// readme

worldcup-betting-analyst

世界杯竞彩足球 · 诚实分析助手。这个 skill 可用于 Claude Code 和 Codex，帮助用户在世界杯及赛前热身赛期间分析中国竞彩足球玩法。

它的目标不是“保证命中”，而是：

  1. 把实时赔率、单关/过关状态、伤停、首发、战意和市场概率查清楚。
  2. 用比赛原型分析强弱对位、破密集防守、小组赛算分、同级缠斗等关键问题。
  3. 明确区分“看好赛果”“相对可买”和“赔率是否真的有价值”。
  4. 用主推、可选、博取、跳过做分层推荐，而不是非黑即白。
  5. 识别低赔热门、乱串关、追注、借钱下注等高风险行为。

能做什么

  • 从体彩官网 API 抓取竞彩赔率和单关/过关状态。
  • 结合实时搜索分析近况、伤停、首发、战意、世界杯/大赛履历。
  • 用低抽水市场概率做校准，避免纯靠主观判断。
  • 输出单场分析卡片、分层推荐、串关建议和总结表。
  • 在信息不足或赔率无价值时降级推荐强度；没有清晰方向时才建议跳过。

文件结构

worldcup-betting-analyst/
├── SKILL.md
├── agents/
│   └── openai.yaml
├── scripts/
│   ├── fetch_sporttery.py
│   └── odds_math.py
└── examples/
    └── sample-output.md

安装到 Codex

个人级别：

mkdir -p ~/.agents/skills/worldcup-betting-analyst
cp -R SKILL.md agents scripts examples ~/.agents/skills/worldcup-betting-analyst/

项目级别：

mkdir -p .agents/skills/worldcup-betting-analyst
cp -R SKILL.md agents scripts examples .agents/skills/worldcup-betting-analyst/

在 Codex 中可以显式输入：

$worldcup-betting-analyst 帮我看看今晚世界杯竞彩怎么买

也可以直接提到世界杯、竞彩、足彩、买球、串关等关键词，让 Codex 自动判断是否触发。

安装到 Claude Code

个人级别：

mkdir -p ~/.claude/skills/worldcup-betting-analyst
cp -R SKILL.md scripts examples…
↑ The Undervalued Score +

How much a project earns versus how much attention it actually gets. Above 50 means the work is outrunning its audience. Recomputed nightly from commit velocity, contributor effort, issue resolution, fork utility, release cadence, and project maturity — divided by a logarithmic reach factor.

score  = signal / reach

signal = 0.25·commit_velocity   // commits in last 90 days (cap 30)
       + 0.20·contributor_work  // unique authors × velocity (cap 100)
       + 0.20·issue_resolution  // closed ÷ total issues
       + 0.20·fork_ratio        // forks ÷ stars (proxy for real usage)
       + 0.10·release_cadence   // releases in 90 days (cap 3)
       + age_bonus              // +0 to +0.30 after 6 months
       + homepage_bonus         // +0.05 if homepage is set

reach  = log₁₀(stars + watchers + 10)█
♥ The Health Score +

Is the project alive and maintained right now? A 0–100 pulse recomputed nightly from commit recency, rhythm, how fast issues close, and how quickly PRs get merged.

health = 0.35·recency       // days since last commit (90d decay)
       + 0.25·cadence       // commit rhythm consistency
       + 0.20·issue_health  // closed ÷ total issues
       + 0.20·pr_health     // merged ÷ total PRs█
◷ Health bands +

The colour and label on every card come straight from the health score.

Healthy   80 – 100   active, responsive, regular releases
Stable    60 – 79    maintained, steady, no alarms
Quiet     40 – 59    slowing down — watch this one
At Risk    0 – 39    going dark · candidate for rescue█
// Tags — what each label means +

Tags are independent behavioral signals computed nightly. A project can hold multiple at once. They drive the home page sections.

solo_builder      one person holds > 80% of commits (last 180d)
needs_contributors has open "help wanted" or "good first issue" labels
hidden_gem        < 100 stars · active in last 3 months · documented
legacy_hero       repo > 5 years old · committed this year
fork_magnet       forks/stars > 0.5 · used as template or dependency
release_machine   5+ releases in the last 90 days
under_pressure    > 10 open issues · ≤ 2 contributors · health ≥ 60
community_watch   watchers > stars · devs tracking before the public
community_hub     GitHub Discussions enabled · > 20 discussions
funded            maintainer has active funding channel█
★ Why rank against stars at all? +

Stars are an outcome, not effort. A project with 8 stars and daily commits is doing more interesting work than one coasting on 8k. We measure the building, then divide by the attention already received — so the genuinely undervalued rise to the top.

// stars   = lagging indicator
// commits = leading indicator
// we rank by the leading one█