跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
搜索与研究

anycap-worldcup-predict

World Cup match prediction and pre-match intel for football (soccer) fans: predict who will win and a likely scoreline, backed by structured, verifiable evidence -- player profiles, squad dossiers, current form, head-to-head records, and past-tournament history -- using AnyCap web search and crawl. Weighs FIFA ranking, recent form, head-to-head, and key players, plus any user-defined dimensions (home advantage, injuries, rest, weather, vibes), then makes a clearly-labeled for-fun call with a confidence level and a mandatory disclaimer. Built on the 'search less, not faster' strategy: narrow the search space first, retrieve only what matters, then verify against authoritative sources. Use when a fan wants a World Cup match prediction, predicted score, or who-will-win call; wants a player's profile, bio, form, or stats; wants a full World Cup squad or national-team lineup table; wants to size up two teams before a match; or wants head-to-head and past World Cup context. Trigger on: World

anycap-ai · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add anycap-ai/anycap --skill anycap-worldcup-predict

技能说明


name: anycap-worldcup-predict description: "World Cup match prediction and pre-match intel for football (soccer) fans: predict who will win and a likely scoreline, backed by structured, verifiable evidence -- player profiles, squad dossiers, current form, head-to-head records, and past-tournament history -- using AnyCap web search and crawl. Weighs FIFA ranking, recent form, head-to-head, and key players, plus any user-defined dimensions (home advantage, injuries, rest, weather, vibes), then makes a clearly-labeled for-fun call with a confidence level and a mandatory disclaimer. Built on the 'search less, not faster' strategy: narrow the search space first, retrieve only what matters, then verify against authoritative sources. Use when a fan wants a World Cup match prediction, predicted score, or who-will-win call; wants a player's profile, bio, form, or stats; wants a full World Cup squad or national-team lineup table; wants to size up two teams before a match; or wants head-to-head and past World Cup context. Trigger on: World Cup prediction, predict the score, who will win, match prediction, predicted scoreline, World Cup, World Cup squad, national team lineup, pre-match analysis, matchup, player form, footballer stats, player profile, head-to-head, or scout a team." metadata: version: 0.6.2 website: https://anycap.ai license: MIT compatibility: Requires anycap CLI (authenticated). Works with any agent that supports shell commands.

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.

Prerequisites

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

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:

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

Workflow

GoalRouteReference
One player's basic infoGrounding structured JSONlookup.md
Right player when name is sharedAdd context / pre-scan with --querylookup.md
High-accuracy, sourced profileCross-check vs Wikipediaverify.md
A whole squad / rosterLoop grounding, aggregate to tablebatch.md
Career + current World Cup statsGrounding stats JSON (with caveats)stats.md
Size up a matchup (Team A vs Team B)Build both squads via batch, compare side by sidebatch.md
Add past World Cup contextFormat, group + knockout results, key players, team history, head-to-headhistory.md
Call a winner + scoreline (for fun)Weigh the gathered layers (plus any user-defined dimensions), then predict with a mandatory disclaimerpredict.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.

Fast path (single player)

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):

{
  "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.

Output Schema

Normalize ev

阅读完整来源 ↗