World Cup 2026 Intelligence (Premium)
A hosted, read-only intelligence layer for the FIFA World Cup 2026. It joins
three things that are normally separate — official match truth, live
prediction-market state, and AI-grounded context — under one canonical id
space, so an agent can go from a market to the fixture to the teams in a single
hop and reason about why a price is moving.
This skill itself runs no code. Like the machina
gateway it builds on, it shells out to machina-cli, selects the hosted World
Cup Intelligence project, and the agent harness talks to that project's MCP
server. Tenant routing, provider keys, rate limits, and caching all live
server-side. You never call a raw HTTP API or hold a provider key.
Read-only intelligence — not advice. Every output is informational sports
market intelligence. Not betting, trading, financial, or investment advice.
This layer has no order-placement, trading, or portfolio endpoints. If the
user wants to act on a signal, that execution happens in their own agent, on
their own account and keys — never here.
Premium / billing
This is a paid, metered layer (Machina Credits — see your project's credit-cost
classes). Free public data does not flow through here. Where your agent
harness supports agent-native pay-per-call (x402), the MCP server advertises price
per tool; otherwise calls draw from the project's credit balance. If a call
returns a 402 / "payment required" / "insufficient credits" error, surface it to
the user and stop — do not retry-loop.
Quick Start
# 1. Install the Machina CLI (one-time) — shared with the `machina` skill
pipx install machina-cli
# or: uv tool install machina-cli
# or: python -m pip install --user machina-cli
# 2. Authenticate
machina login # interactive (browser)
# machina login --api-key <project-api-key> # non-interactive (CI/CD)
# 3. Select the World Cup Intelligence project (REQUIRED)
machina project list
machina project use <world-cup-project-id>
# 4. Connect the MCP server
# `machina project use` (or `machina template install`) returns the MCP URL +
# headers. Point your harness's MCP config at it (e.g. .claude/mcp.json for
# Claude Code), then reload the harness so it re-reads the config.
Inspect-before-run fallback
If a shell installer is required by the user's environment, download and inspect it before execution instead of piping remote content directly into a shell:
curl -fsSL https://raw.githubusercontent.com/machina-sports/machina-cli/main/install.sh -o /tmp/machina-install.sh
less /tmp/machina-install.sh
bash /tmp/machina-install.sh
CRITICAL: Before Any Premium Call
Verify, in order — fix the specific failing step, never loop on the same call:
machina-cli is installed — which machina / machina version.
- Authenticated —
machina auth whoami returns a user.
- The World Cup Intelligence project is selected —
machina project use <id>.
- The harness is connected to that project's MCP server (tools are visible).
What you get
All tools are read-only. Group by job:
Identity & fixtures (official match truth)
| Tool |
Returns |
worldcup-resolve |
Any provider id or canonical URN → entity + all cross-provider ids |
worldcup-get-schedule |
Fixtures, filter by date / team / status |
worldcup-get-event-context |
Enriched match context (event + grounded prematch research) |
worldcup-get-standings |
Group tables |
worldcup-get-squads |
Both teams' squads |
worldcup-get-injuries |
Injuries / suspensions |
worldcup-get-player-performance-context |
Player performance signals (official + provisional, kept separate) |
Market intelligence (Kalshi + Polymarket, URN-linked)
| Tool |
Returns |
worldcup-search-markets |
Market search across venues, linked to fixtures/teams |
worldcup-get-market-state |
Live price + order-book depth + price history + trades |
worldcup-market-movers |
Biggest price moves over a lookback window |
worldcup-compare-market-sources |
Cross-venue price comparison |
worldcup-find-market-edges |
Informational edge / arb candidates, with caveats (AI) |
worldcup-explain-market-move |
Why a price moved, grounded + cited (AI) |
worldcup-generate-market-brief |
Grounded market-intelligence brief for a fixture (AI) |
worldcup-fan-sentiment-context |
Social / news pulse from live X + web (AI) |
Conversational
world-cup-intelligence-agent — full read + market context.
world-cup-market-analyst-agent — market-focused analyst.
The intelligence loop
A typical agent flow — research only, no execution:
- Find the market —
worldcup-search-markets {"query":"Brazil","status":"open"}.
- Anchor it to truth — each market carries
event_urn + related_team_urns;
worldcup-resolve (or worldcup-get-event-context) expands the fixture, squads,
standings, injuries.
- Read live state —
worldcup-get-market-state for price, order-book depth,
history, trades; worldcup-market-movers / worldcup-compare-market-sources for
movement and cross-venue gaps.
- Explain & brief —
worldcup-explain-market-move, worldcup-find-market-edges
(informational only), worldcup-generate-market-brief, worldcup-fan-sentiment-context.
- Hand off — return the signal + sources + freshness/liquidity/resolution
caveats to the user. Stop there. Any trade is the user's own action elsewhere.
Identifiers
Every entity has a canonical machina URN, stable across providers:
- event —
urn:machina:sport:soccer:event:{home}-vs-{away}:{YYYYMMDD}:wor
- team —
urn:machina:sport:soccer:team:{slug}:{iso3}
- player —
urn:machina:sport:soccer:player:{slug}:{YYYYMMDD-dob}:{iso3}
- competition —
urn:machina:sport:soccer:competition:fifa-world-cup-2026:wor
iso3 is the lowercased ISO-3166 alpha-3 (UK home nations use FIFA codes eng/sco/wal).
Every doc also carries a uniform provider_ids map (one id per provider).
Alternate key: reads accept the canonical event_urn or provider_event_id
(the api-football fixture id, e.g. 1489417) — the latter is the simplest client
handle. Markets are keyed {source}:{source_market_id} (e.g. kalshi:KXWCGAME-…,
polymarket:2415458).
Freshness
- Identity / fixtures — synced; teams/events stable, players refresh daily.
worldcup-search-markets — cached, refreshed every ~30 min; responses warn past 15 min.
worldcup-get-market-state — live from the source.
worldcup-market-movers — hourly snapshot series; needs ≥2 buckets to show movement.
Common Errors & Recovery
| Error |
Cause |
Recovery |
command not found: machina |
CLI not installed |
pip install machina-cli |
Not authenticated… |
No session |
machina login |
No project selected… |
Project not chosen |
machina project list → machina project use <world-cup-id> |
402 / payment required / insufficient credits |
Metered call, no balance |
Tell the user; top up credits or enable x402. Do not retry-loop. |
Tools not visible after project use |
Harness hasn't reloaded MCP config |
Restart / reload the harness so it re-reads the MCP config |
Commands that DO NOT exist — never call these
any place, order, trade, buy, sell, bet tool — this layer is
read-only; no such tool exists. Execution is the user's own, elsewhere.
raw requests / direct provider HTTP — go through the MCP server; keys and
the correct searchLimit/nested filters live server-side.
machina mcp start / machina mcp connect — the MCP server runs on Machina
infra; the harness connects via its own MCP config.
Guardrails
- Never present an output as betting/trading/financial advice.
- Never use "guaranteed edge", "guaranteed profit", or "bet this" language —
edges/movers are informational candidates, not recommendations.
- Always return source, freshness, and resolution/liquidity caveats with any
market output.
1---2name: world-cup3description: |4 Premium FIFA World Cup 2026 market & match intelligence — a hosted, read-only5 layer that fuses official match truth (fixtures, standings, squads, injuries,6 player performance) with live prediction markets (Kalshi + Polymarket: prices,7 order books, price history, movers, cross-venue edges) and AI-grounded context8 (prematch briefs, move explanations, fan/social pulse). Every entity carries a9 canonical machina URN cross-walked across api-football, sportradar, opta, entain10 and ESPN, so a market resolves to a fixture resolves to two teams.1112 This skill is prompt-only and premium: it routes the agent to the hosted World Cup13 Intelligence project (a per-project Machina MCP server) via `machina-cli`. It runs14 no code locally and ships no API keys.1516 Use when: the user wants World Cup 2026 odds + match context together, asks "what17 moved and why", wants a grounded market brief or fan-sentiment read on a fixture,18 or needs one stable id that joins markets ↔ fixtures ↔ teams across providers.19 Don't use when: the user wants free snapshot data from public APIs (use the20 `football-data`, `kalshi`, `polymarket`, or `markets` skills), or wants to place a21 bet/trade — this layer is read-only intelligence and never executes orders.22license: MIT23metadata:24 source: https://skillmd.com/skills/machina-sports/world-cup25 author: machina-sports26 version: "0.1.0"27 premium: true28 billing: metered29 risk:30 mode: premium_mcp_read_only31 money_movement: false32 secrets_required: true33 external_mcp: true34 metered_billing: true35 untrusted_content: true36 requires_explicit_confirmation: true37---3839# World Cup 2026 Intelligence (Premium)4041A hosted, **read-only** intelligence layer for the FIFA World Cup 2026. It joins42three things that are normally separate — **official match truth**, **live43prediction-market state**, and **AI-grounded context** — under one canonical id44space, so an agent can go from a market to the fixture to the teams in a single45hop and reason about *why* a price is moving.4647This skill itself runs no code. Like the [`machina`](https://skills.sh/machina-sports/sports-skills/machina)48gateway it builds on, it shells out to `machina-cli`, selects the hosted **World49Cup Intelligence** project, and the agent harness talks to that project's **MCP50server**. Tenant routing, provider keys, rate limits, and caching all live51server-side. You never call a raw HTTP API or hold a provider key.5253> **Read-only intelligence — not advice.** Every output is informational sports54> market intelligence. **Not betting, trading, financial, or investment advice.**55> This layer has **no** order-placement, trading, or portfolio endpoints. If the56> user wants to act on a signal, that execution happens in *their own* agent, on57> *their own* account and keys — never here.5859## Premium / billing6061This is a paid, metered layer (Machina Credits — see your project's credit-cost62classes). Free public data does **not** flow through here. Where your agent63harness supports agent-native pay-per-call (x402), the MCP server advertises price64per tool; otherwise calls draw from the project's credit balance. If a call65returns a `402` / "payment required" / "insufficient credits" error, surface it to66the user and stop — do not retry-loop.6768## Quick Start6970```bash71# 1. Install the Machina CLI (one-time) — shared with the `machina` skill72pipx install machina-cli73# or: uv tool install machina-cli74# or: python -m pip install --user machina-cli7576# 2. Authenticate77machina login # interactive (browser)78# machina login --api-key <project-api-key> # non-interactive (CI/CD)7980# 3. Select the World Cup Intelligence project (REQUIRED)81machina project list82machina project use <world-cup-project-id>8384# 4. Connect the MCP server85# `machina project use` (or `machina template install`) returns the MCP URL +86# headers. Point your harness's MCP config at it (e.g. .claude/mcp.json for87# Claude Code), then reload the harness so it re-reads the config.88```8990### Inspect-before-run fallback9192If a shell installer is required by the user's environment, download and inspect it before execution instead of piping remote content directly into a shell:9394```bash95curl -fsSL https://raw.githubusercontent.com/machina-sports/machina-cli/main/install.sh -o /tmp/machina-install.sh96less /tmp/machina-install.sh97bash /tmp/machina-install.sh98```99100## CRITICAL: Before Any Premium Call101102Verify, in order — fix the *specific* failing step, never loop on the same call:103104- `machina-cli` is installed — `which machina` / `machina version`.105- Authenticated — `machina auth whoami` returns a user.106- The **World Cup Intelligence** project is selected — `machina project use <id>`.107- The harness is connected to that project's MCP server (tools are visible).108109## What you get110111All tools are **read-only**. Group by job:112113### Identity & fixtures (official match truth)114115| Tool | Returns |116|------|---------|117| `worldcup-resolve` | Any provider id **or** canonical URN → entity + all cross-provider ids |118| `worldcup-get-schedule` | Fixtures, filter by date / team / status |119| `worldcup-get-event-context` | Enriched match context (event + grounded prematch research) |120| `worldcup-get-standings` | Group tables |121| `worldcup-get-squads` | Both teams' squads |122| `worldcup-get-injuries` | Injuries / suspensions |123| `worldcup-get-player-performance-context` | Player performance signals (official + provisional, kept separate) |124125### Market intelligence (Kalshi + Polymarket, URN-linked)126127| Tool | Returns |128|------|---------|129| `worldcup-search-markets` | Market search across venues, linked to fixtures/teams |130| `worldcup-get-market-state` | Live price + order-book depth + price history + trades |131| `worldcup-market-movers` | Biggest price moves over a lookback window |132| `worldcup-compare-market-sources` | Cross-venue price comparison |133| `worldcup-find-market-edges` | Informational edge / arb candidates, with caveats (AI) |134| `worldcup-explain-market-move` | Why a price moved, grounded + cited (AI) |135| `worldcup-generate-market-brief` | Grounded market-intelligence brief for a fixture (AI) |136| `worldcup-fan-sentiment-context` | Social / news pulse from live X + web (AI) |137138### Conversational139140- `world-cup-intelligence-agent` — full read + market context.141- `world-cup-market-analyst-agent` — market-focused analyst.142143## The intelligence loop144145A typical agent flow — research only, no execution:1461471. **Find** the market — `worldcup-search-markets {"query":"Brazil","status":"open"}`.1482. **Anchor** it to truth — each market carries `event_urn` + `related_team_urns`;149 `worldcup-resolve` (or `worldcup-get-event-context`) expands the fixture, squads,150 standings, injuries.1513. **Read live state** — `worldcup-get-market-state` for price, order-book depth,152 history, trades; `worldcup-market-movers` / `worldcup-compare-market-sources` for153 movement and cross-venue gaps.1544. **Explain & brief** — `worldcup-explain-market-move`, `worldcup-find-market-edges`155 (informational only), `worldcup-generate-market-brief`, `worldcup-fan-sentiment-context`.1565. **Hand off** — return the signal + sources + freshness/liquidity/resolution157 caveats to the user. **Stop there.** Any trade is the user's own action elsewhere.158159## Identifiers160161Every entity has a **canonical machina URN**, stable across providers:162163- event — `urn:machina:sport:soccer:event:{home}-vs-{away}:{YYYYMMDD}:wor`164- team — `urn:machina:sport:soccer:team:{slug}:{iso3}`165- player — `urn:machina:sport:soccer:player:{slug}:{YYYYMMDD-dob}:{iso3}`166- competition — `urn:machina:sport:soccer:competition:fifa-world-cup-2026:wor`167168`iso3` is the lowercased ISO-3166 alpha-3 (UK home nations use FIFA codes `eng`/`sco`/`wal`).169Every doc also carries a uniform `provider_ids` map (one id per provider).170171**Alternate key:** reads accept the canonical `event_urn` **or** `provider_event_id`172(the api-football fixture id, e.g. `1489417`) — the latter is the simplest client173handle. Markets are keyed `{source}:{source_market_id}` (e.g. `kalshi:KXWCGAME-…`,174`polymarket:2415458`).175176## Freshness177178- Identity / fixtures — synced; teams/events stable, players refresh daily.179- `worldcup-search-markets` — cached, refreshed every ~30 min; responses warn past 15 min.180- `worldcup-get-market-state` — live from the source.181- `worldcup-market-movers` — hourly snapshot series; needs ≥2 buckets to show movement.182183## Common Errors & Recovery184185| Error | Cause | Recovery |186|---|---|---|187| `command not found: machina` | CLI not installed | `pip install machina-cli` |188| `Not authenticated…` | No session | `machina login` |189| `No project selected…` | Project not chosen | `machina project list` → `machina project use <world-cup-id>` |190| `402` / `payment required` / `insufficient credits` | Metered call, no balance | Tell the user; top up credits or enable x402. **Do not retry-loop.** |191| Tools not visible after `project use` | Harness hasn't reloaded MCP config | Restart / reload the harness so it re-reads the MCP config |192193## Commands that DO NOT exist — never call these194195- ~~any `place`, `order`, `trade`, `buy`, `sell`, `bet` tool~~ — this layer is196 read-only; no such tool exists. Execution is the user's own, elsewhere.197- ~~raw `requests` / direct provider HTTP~~ — go through the MCP server; keys and198 the correct `searchLimit`/nested `filters` live server-side.199- ~~`machina mcp start` / `machina mcp connect`~~ — the MCP server runs on Machina200 infra; the harness connects via its own MCP config.201202## Guardrails203204- Never present an output as betting/trading/financial advice.205- Never use "guaranteed edge", "guaranteed profit", or "bet this" language —206 edges/movers are **informational candidates**, not recommendations.207- Always return **source, freshness, and resolution/liquidity caveats** with any208 market output.