anycap-worldcup-predict

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

AnyCap World Cup Predict

Read this entire file before starting. It defines a reliable workflow for turning a player name (or a whole squad) into structured, verifiable World Cup pre-match intel using AnyCap, then optionally calling a winner and scoreline for fun.

World Cup match prediction and pre-match intel for serious football fans. Turn player names and lineups into structured, verifiable profiles, stats, and matchup briefings so you can read a World Cup matchup before kickoff -- then, if you want, finish with a for-fun prediction (likely winner + scoreline + confidence). Built for World Cup squads and national-team lineups, and works for any footballer.

This skill is about how to retrieve and verify player data. For CLI command reference (flags, output, jq), read the

anycap-cli

skill and its

references/search.md

references/crawl.md

This skill surfaces public information (profiles, form, historical stats) and can finish with an optional for-fun prediction (likely winner + a playful scoreline) derived from that data. It does not set betting odds, output win probabilities as if they were facts, or place wagers. Every prediction must ship with the disclaimer in predict.md. Treat everything as informational and form your own judgment.

开始前请通读整个文档。 本文档定义了一套可靠的工作流程，可通过AnyCap将球员姓名（或整支球队阵容）转化为结构化、可验证的世界杯赛前情报，还可选择性地给出娱乐性质的胜负及比分预测。

为资深足球爱好者提供世界杯比赛预测与赛前情报。将球员姓名及阵容转化为结构化、可验证的档案、数据及对决简报，让你在世界杯开赛前就能了解对决双方的情况——如果需要，还可以得出一个娱乐性质的预测结果（潜在胜者+比分+置信度）。该工具专为世界杯阵容及国家队首发名单设计，也适用于所有足球运动员。

本技能聚焦于如何检索与验证球员数据。如需CLI命令参考（参数、输出、jq用法），请查阅

anycap-cli

技能及其

references/search.md

references/crawl.md

文档。

本技能展示的是公开信息（档案、状态、历史数据），并可基于这些数据得出可选的娱乐性质预测（潜在胜者+趣味比分）。它不提供博彩赔率、不将获胜概率视为事实输出，也不进行投注。所有预测都必须附带predict.md中的免责声明。所有内容仅供参考，请自行判断。

Prerequisites

前提条件

```
anycap
```
CLI installed and authenticated (
```
anycap status
```
to verify). Read the
```
anycap-cli
```
skill if setup is needed.
```
jq
```
for parsing JSON output.

已安装并认证
```
anycap
```
CLI（可通过
```
anycap status
```
验证）。如需设置，请查阅
```
anycap-cli
```
技能。
已安装
```
jq
```
用于解析JSON输出。

Core Principle: Search Less, Not Faster

核心原则：少搜索，而非快搜索

Do not crawl the whole web for every player. Narrow the search space first, then retrieve only what matters:

Grounding first -- ask for a structured profile in one shot (
```
anycap search --prompt
```
). This is the fastest path to clean data.
Disambiguate -- when a name is shared by several players, add context (nationality, position, birth year, club) to lock onto the right one.
Verify only when accuracy matters -- cross-check against an authoritative, crawlable source (Wikipedia) instead of trusting a single answer.
Prune, don't dump -- in batch mode, fetch one structured profile per player; never crawl every search result.

不要为每位球员爬取整个网络。先缩小搜索范围，再仅获取关键信息：

先锚定信息——一次性获取结构化档案（
```
anycap search --prompt
```
）。这是获取干净数据的最快途径。
消歧义——当多个球员同名时，添加上下文信息（国籍、位置、出生年份、俱乐部）以锁定目标球员。
仅在需要精准性时验证——对照权威、可爬取的来源（维基百科）交叉核对，而非轻信单一答案。
精简而非堆砌——在批量模式下，为每位球员获取一份结构化档案；绝不爬取所有搜索结果。

Workflow

工作流程

Goal	Route	Reference
One player's basic info	Grounding structured JSON	lookup.md
Right player when name is shared	Add context / pre-scan with `--query`	lookup.md
High-accuracy, sourced profile	Cross-check vs Wikipedia	verify.md
A whole squad / roster	Loop grounding, aggregate to table	batch.md
Career + current World Cup stats	Grounding stats JSON (with caveats)	stats.md
Size up a matchup (Team A vs Team B)	Build both squads via batch, compare side by side	batch.md
Add past World Cup context	Format, group + knockout results, key players, team history, head-to-head	history.md
Call a winner + scoreline (for fun)	Weigh the gathered layers (plus any user-defined dimensions), then predict with a mandatory disclaimer	predict.md

For a matchup, run the squad workflow for both teams, then layer in historical context (tournament track record + head-to-head from history.md). Present three layers side by side -- squad quality, current form, historical context -- and highlight differences in key positions and availability. Then, if a prediction is wanted, finish with an optional for-fun call (likely winner + playful scoreline + confidence) per predict.md. Always keep the factual layers clearly separated from the prediction, and always attach the disclaimer.

目标	实现路径	参考文档
单名球员的基本信息	锚定结构化JSON	lookup.md
同名球员中定位正确目标	添加上下文 / 使用 `--query` 预扫描	lookup.md
高精准度、有来源的球员档案	与维基百科交叉核对	verify.md
整支球队阵容 / 名单	循环锚定信息，汇总为表格	batch.md
职业生涯 + 当前世界杯数据	锚定数据JSON（注意局限性）	stats.md
分析对决双方（A队 vs B队）	通过批量流程构建两队阵容，并列对比	batch.md
添加过往世界杯背景	整理、分组 + 淘汰赛结果、关键球员、球队历史、交手记录	history.md
给出胜负+比分预测（娱乐性质）	综合已收集的信息（及用户自定义维度），并附带强制免责声明进行预测	predict.md

对于对决分析，先为两队执行球队阵容流程，再加入历史背景（赛事记录+history.md中的交手记录）。将三个层面的信息并列展示——阵容实力、近期状态、历史背景——并突出关键位置的差异及球员可用性。如果需要预测结果，最后可添加可选的娱乐性质预测（潜在胜者+趣味比分+置信度），需遵循predict.md的要求。务必将事实信息层与预测结果明确区分，并始终附带免责声明。

Fast path (single player)

快速路径（单名球员）

bash

anycap search --prompt 'Give the basic profile of footballer Jude Bellingham as JSON with fields: full_name, date_of_birth, nationality, height, position, current_club, shirt_number, national_team. Only the JSON.' \
  | jq -r '.data.content'

Returns (verified):

json

{
  "full_name": "Jude Victor William Bellingham",
  "date_of_birth": "2003-06-29",
  "nationality": "English",
  "height": "1.86 m",
  "position": "Midfielder",
  "current_club": "Real Madrid",
  "shirt_number": 5,
  "national_team": "England"
}

Grounding search costs 5 credits per call. General search (

--query

) and crawl cost 1 credit each.

bash

anycap search --prompt 'Give the basic profile of footballer Jude Bellingham as JSON with fields: full_name, date_of_birth, nationality, height, position, current_club, shirt_number, national_team. Only the JSON.' \
  | jq -r '.data.content'

返回结果（已验证）：

json

{
  "full_name": "Jude Victor William Bellingham",
  "date_of_birth": "2003-06-29",
  "nationality": "English",
  "height": "1.86 m",
  "position": "Midfielder",
  "current_club": "Real Madrid",
  "shirt_number": 5,
  "national_team": "England"
}

锚定搜索每次调用消耗5个积分。常规搜索（

--query

）和爬取每次消耗1个积分。

Output Schema

输出 Schema

Normalize every profile to this schema so single-player and batch results are consistent:

Field	Type	Notes
`full_name`	string	Legal/full name
`date_of_birth`	string	`YYYY-MM-DD` ; use `null` if unknown
`nationality`	string	Primary nationality
`height`	string	e.g. `1.86 m` ; `null` if unknown
`position`	string	e.g. `Midfielder` , `Goalkeeper`
`current_club`	string	Club as of retrieval date
`shirt_number`	int/null	Club or national-team number
`national_team`	string	National team

Rules:

Use
```
null
```
for missing fields. Never invent values.
```
current_club
```
and
```
shirt_number
```
change frequently -- treat them as point-in-time and note the retrieval date.
When a field cannot be confirmed, mark it and (if accuracy matters) verify via verify.md.

将所有档案标准化为以下Schema，确保单球员和批量结果的一致性：

字段	类型	说明
`full_name`	string	法定全名
`date_of_birth`	string	`YYYY-MM-DD` 格式；未知则设为 `null`
`nationality`	string	主要国籍
`height`	string	示例： `1.86 m` ；未知则设为 `null`
`position`	string	示例： `Midfielder` （中场）、 `Goalkeeper` （门将）
`current_club`	string	检索日期时的所属俱乐部
`shirt_number`	int/null	俱乐部或国家队球衣号码
`national_team`	string	所属国家队

规则：

缺失字段使用
```
null
```
。绝不编造数据。
```
current_club
```
和
```
shirt_number
```
会频繁变动——将其视为即时数据，并标注检索日期。
当某字段无法确认时，标记该字段；若需要精准性，可通过verify.md进行验证。

Important: Source Reliability (verified)

重要提示：来源可靠性（已验证）

Wikipedia is reliably crawlable (
```
anycap crawl https://en.wikipedia.org/wiki/<Player>
```
returns full Markdown). Use it as the primary verification source.
Transfermarkt blocks crawling --
```
anycap crawl
```
returns a short
```
Human Verification
```
page, not data. Do not rely on crawling it; use grounding search or Wikipedia instead.
Other stats sites may also bot-block. Always check the crawled
```
title
```
/length before trusting content.

维基百科可稳定爬取（
```
anycap crawl https://en.wikipedia.org/wiki/<Player>
```
返回完整Markdown内容）。将其作为主要验证来源。
Transfermarkt会阻止爬取——
```
anycap crawl
```
返回简短的
```
Human Verification
```
页面，而非数据。不要依赖爬取该网站；使用锚定搜索或维基百科替代。
其他数据网站也可能阻止爬虫。在信任内容前，务必检查爬取结果的
```
title
```
和长度。

Prediction (for fun)

预测（娱乐性质）

After the factual layers, you may add an optional, clearly-labeled prediction so the briefing is fun to read. See predict.md for the method and the required disclaimer. Non-negotiable rules:

Facts first, prediction last. Never blend the guess into the data tables; put it in its own clearly-marked block.
Always attach the disclaimer from predict.md. A prediction without the disclaimer is incomplete output.
Entertainment, not betting. Do not present win probabilities or odds as facts, do not give wagering advice, and do not tell anyone to bet.
Show the reasoning. Base the call on the gathered signals (ranking, form, head-to-head, key players), not a coin flip.
Let the user steer. Users can add, drop, or re-weight prediction dimensions (e.g. home advantage, injuries, rest, weather, "vibes"). Honor their weights, retrieve any missing data first, and list the final dimension set used. See predict.md.

在事实信息层之后，你可以添加一个可选的、明确标记的预测结果，让简报更具趣味性。请查看predict.md了解方法及必填的免责声明。不可协商的规则：

先事实，后预测。绝不要将猜测混入数据表格；将预测放在单独的、明确标记的区块中。
始终附带免责声明，即predict.md中的内容。没有免责声明的预测是不完整的输出。
仅供娱乐，非博彩建议。不要将获胜概率或赔率视为事实，不要提供投注建议，也不要引导任何人投注。
展示推理过程。基于已收集的信号（排名、状态、交手记录、关键球员）做出判断，而非随机猜测。
遵循用户导向。用户可以添加、删除或重新加权预测维度（如主场优势、伤病、休息、天气、“氛围”）。尊重他们的权重，先检索所有缺失数据，并列出最终使用的维度集合。详情请见predict.md。

Limitations

局限性

Live data (current club, shirt number, latest stats) reflects whatever the web returns at call time and can lag real events.
Grounding stats numbers are best-effort and can be approximate; verify critical figures against Wikipedia.
Generic player names need disambiguation context or the wrong person may be returned.
This skill retrieves data on demand; it is not a stored database of all players.

实时数据（当前俱乐部、球衣号码、最新数据）反映调用时网络返回的内容，可能滞后于实际事件。
锚定数据的数值为最佳估算值，可能存在近似；关键数据请对照维基百科验证。
通用球员姓名需要消歧义上下文，否则可能返回错误的球员信息。
本技能按需检索数据；并非存储所有球员信息的数据库。

Quick Reference

快速参考

Tool	Purpose
`anycap search --prompt "...JSON..."`	Structured profile / stats in one shot (5 cr)
`anycap search --query "..." --no-crawl`	Find/disambiguate the right player page (1 cr)
`anycap crawl https://en.wikipedia.org/wiki/<Player>`	Authoritative verification source (1 cr)
`anycap status`	Check auth before a batch run

工具	用途
`anycap search --prompt "...JSON..."`	一次性获取结构化档案/数据（5积分）
`anycap search --query "..." --no-crawl`	查找/消歧义目标球员页面（1积分）
`anycap crawl https://en.wikipedia.org/wiki/<Player>`	权威验证来源（1积分）
`anycap status`	批量运行前检查认证状态