--- name: pp-catapult-openfield-connect description: "Every Catapult GPS metric — ACWR, velocity benchmarks, load reports — from one command, with a local SQLite mirror for offline analysis. Trigger phrases: `check ACWR for the squad`, `what is the player load from today's session`, `compare the last two matches`, `who is at injury risk`, `generate a weekly load report`, `sync Catapult data`, `use catapult-openfield-connect`, `run catapult CLI`." author: "erash11" license: "Apache-2.0" argument-hint: " [args] | install cli|mcp" allowed-tools: "Read Bash" metadata: openclaw: requires: bins: - catapult-openfield-connect-pp-cli install: - kind: go bins: [catapult-openfield-connect-pp-cli] module: github.com/mvanhorn/printing-press-library/library/health/catapult-openfield-connect/cmd/catapult-openfield-connect-pp-cli --- # Catapult OpenField — Printing Press CLI ## Prerequisites: Install the CLI This skill drives the `catapult-openfield-connect-pp-cli` binary. **You must verify the CLI is installed before invoking any command from this skill.** If it is missing, install it first: 1. Install via the Printing Press installer. It defaults binaries to `$HOME/.local/bin` on macOS/Linux and `%LOCALAPPDATA%\Programs\PrintingPress\bin` on Windows: ```bash npx -y @mvanhorn/printing-press-library install catapult-openfield-connect --cli-only ``` 2. Verify: `catapult-openfield-connect-pp-cli --version` 3. Ensure the reported install directory is on `$PATH` for the agent/runtime that will invoke this skill. If the `npx` install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.5 or newer). This installs into `$GOPATH/bin` (default `$HOME/go/bin`), so add that directory to `$PATH` instead: ```bash go install github.com/mvanhorn/printing-press-library/library/health/catapult-openfield-connect/cmd/catapult-openfield-connect-pp-cli@latest ``` If `--version` reports "command not found" after install, the runtime cannot see the binary directory on `$PATH`. Do not proceed with skill commands until verification succeeds. catapult-openfield-connect-pp-cli syncs your OpenField data into a local SQLite store and unlocks computations the API cannot do alone: 28-day ACWR dashboards, personal velocity bests, session diffs, and positional benchmarks — all scriptable, pipeable, and agent-native. What used to require a custom R script now takes one command. ## When to Use This CLI Use this CLI for any Catapult OpenField data task: pulling session stats, checking squad ACWR, comparing matches, generating load reports, or giving an agent access to athlete GPS data without manual OpenField exports. It is the only CLI surface for OpenField; the alternative is the catapultR R package or the web UI. ## Anti-triggers Do not use this CLI for: - Do not use this CLI to create, update, or delete anything in OpenField — it is read-only by design - Do not use it for live in-session streaming telemetry; it reads completed activity data - Do not use it for video or tactical analysis — OpenField carries GPS/accelerometer data only ## Unique Capabilities These capabilities aren't available in any other tool for this API. ### Load intelligence that compounds - **`acwr`** — Instant acute:chronic workload ratios for any athlete or the full squad, color-coded into safe (0.8-1.3), caution, and danger (>1.5) zones. _Reach for this when asked who is at injury risk or for the morning workload check._ ```bash catapult-openfield-connect-pp-cli acwr --squad --metric total_player_load --flag-risk --agent ``` - **`report`** — One-command weekly summary — total Player Load, session count, ACWR, max velocity vs PB, monotony, strain, and risk flags — exportable as markdown or CSV. _Reach for this when a coach briefing or weekly load summary is requested._ ```bash catapult-openfield-connect-pp-cli report --week --squad --format markdown --export ./week_load.md ``` - **`pb`** — Compares recent session values against each athlete's all-time or rolling personal best, with readiness % and 3-session trend arrows. _Use before deciding who trains at full intensity today._ ```bash catapult-openfield-connect-pp-cli pb --metric max_vel --vs-peak --agent ``` - **`benchmark`** — Ranks any athlete against positional peers for a metric: percentile rank, squad median, and position median with outlier flags. _Use after match debriefs to answer how an athlete compares to peers._ ```bash catapult-openfield-connect-pp-cli benchmark --metric total_distance --percentile --agent ``` ### Session analysis - **`diff`** — Side-by-side comparison of two sessions (by ID, date, or last/prev) showing absolute and percentage change per metric and per athlete. _Use to diagnose travel fatigue and fixture congestion between consecutive matches._ ```bash catapult-openfield-connect-pp-cli diff last prev --squad --metrics total_player_load,max_vel --agent ``` - **`rtp`** — Tracks an injured athlete's load progression session-by-session as a percentage of squad average or a pre-injury baseline window. _Use when managing return-to-play decisions to give medical staff quantitative progression data._ ```bash catapult-openfield-connect-pp-cli rtp --athlete top --target-metric total_player_load --vs-squad --threshold 85 --agent ``` - **`heatmap`** — Renders an athlete-by-period intensity matrix for a session — ANSI heatmap on a terminal, JSON matrix for agents — surfacing where fatigue compounded. _Use after matches to diagnose second-half performance drops._ ```bash catapult-openfield-connect-pp-cli heatmap --activity last --metric total_player_load --json ``` ## Command Reference **activities** — Training sessions and matches - `catapult-openfield-connect-pp-cli activities annotations` — Annotations on an activity - `catapult-openfield-connect-pp-cli activities athletes` — Athletes who participated in an activity - `catapult-openfield-connect-pp-cli activities devices` — Devices used in an activity - `catapult-openfield-connect-pp-cli activities get` — Get one activity; use --embed all for tag/athlete detail - `catapult-openfield-connect-pp-cli activities list` — List activities (sessions and matches) with venue and timing - `catapult-openfield-connect-pp-cli activities periods` — Periods (halves, quarters, drills) within an activity **annotations** — Annotation metadata - `catapult-openfield-connect-pp-cli annotations` — List annotation categories **athletes** — Athletes registered in the OpenField account - `catapult-openfield-connect-pp-cli athletes annotations` — Annotations recorded against an athlete - `catapult-openfield-connect-pp-cli athletes bands` — Velocity/acceleration band thresholds configured for an athlete - `catapult-openfield-connect-pp-cli athletes list` — List all athletes with physical attributes, jersey numbers, and positions **customer** — Account info and settings - `catapult-openfield-connect-pp-cli customer get` — Customer account info - `catapult-openfield-connect-pp-cli customer settings` — User settings including velocity and distance units **parameters** — The 200+ metric catalog (Player Load, banded velocity, heart rate...) - `catapult-openfield-connect-pp-cli parameters` — List every parameter (metric) available in OpenField, with slugs used by stats queries **periods** — Periods across activities - `catapult-openfield-connect-pp-cli periods annotations` — Annotations on a period - `catapult-openfield-connect-pp-cli periods athletes` — Athletes in a period **sensor** — Raw 10Hz sensor data, IMA events, and velocity/acceleration efforts - `catapult-openfield-connect-pp-cli sensor data` — 10Hz sensor stream for one athlete in one activity (large; requires sensor-read-only scope) - `catapult-openfield-connect-pp-cli sensor efforts` — Generation-2 velocity or acceleration efforts for one athlete in one activity - `catapult-openfield-connect-pp-cli sensor events` — IMA events (jumps, dives, sport-specific movements) for one athlete in one activity **stats** — The stats query engine — computed metrics with grouping and filters - `catapult-openfield-connect-pp-cli stats` — Query computed statistics. **teams** — Teams in the account - `catapult-openfield-connect-pp-cli teams` — List teams **venues** — Venues - `catapult-openfield-connect-pp-cli venues get` — Get one venue - `catapult-openfield-connect-pp-cli venues list` — List venues ## Freshness Contract This printed CLI owns bounded freshness only for registered store-backed read command paths. In `--data-source auto` mode, those paths check `sync_state` and may run a bounded refresh before reading local data. `--data-source local` never refreshes. `--data-source live` reads the API and does not mutate the local store. Set `CATAPULT_OPENFIELD_CONNECT_NO_AUTO_REFRESH=1` to skip the freshness hook without changing source selection. Covered paths: - `catapult-openfield-connect-pp-cli activities` - `catapult-openfield-connect-pp-cli activities list` - `catapult-openfield-connect-pp-cli annotations` - `catapult-openfield-connect-pp-cli athletes` - `catapult-openfield-connect-pp-cli athletes list` - `catapult-openfield-connect-pp-cli parameters` - `catapult-openfield-connect-pp-cli sensor` - `catapult-openfield-connect-pp-cli teams` - `catapult-openfield-connect-pp-cli venues` - `catapult-openfield-connect-pp-cli venues list` - `catapult-openfield-connect-pp-cli customer` - `catapult-openfield-connect-pp-cli customer get` - `catapult-openfield-connect-pp-cli customer settings` When JSON output uses the generated provenance envelope, freshness metadata appears at `meta.freshness`. Treat it as current-cache freshness for the covered command path, not a guarantee of complete historical backfill or API-specific enrichment. ### Finding the right command When you know what you want to do but not which command does it, ask the CLI directly: ```bash catapult-openfield-connect-pp-cli which "" ``` `which` resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code `0` means at least one match; exit code `2` means no confident match — fall back to `--help` or use a narrower query. ## Recipes ### Morning ACWR check for the full squad ```bash catapult-openfield-connect-pp-cli acwr --squad --flag-risk --agent --select athlete_name,acwr,risk_zone ``` Run before every training session to see who is in the caution or danger zone. ### Post-session stats grouped by athlete ```bash catapult-openfield-connect-pp-cli stats --parameters total_player_load,total_distance,max_vel --group-by athlete --json ``` The primary data pull after every session. ### Compare the last two matches ```bash catapult-openfield-connect-pp-cli diff last prev --squad --metrics total_player_load,max_vel --agent --select athlete_name,metric,delta_pct ``` Percentage change per athlete per metric between matches; --select keeps agent context tight. ### Find velocity metric slugs ```bash catapult-openfield-connect-pp-cli search "velocity" --type parameters --limit 10 ``` Discover exact slugs before building a stats query. ### Weekly report to markdown ```bash catapult-openfield-connect-pp-cli report --week --squad --format markdown --export ./week12_load.md ``` Paste directly into the coach briefing doc. ## Auth Setup OpenField Connect accepts a long-lived API token (create one in OpenField under API Tokens) sent as a Bearer header. Set CATAPULT_TOKEN in your environment or run auth set-token. Regional hosts differ: this CLI defaults to the Americas host (us.catapultsports.com); override base_url in config for APAC/EMEA tenants. Run `catapult-openfield-connect-pp-cli doctor` to verify setup. ## Agent Mode Add `--agent` to any command. Expands to: `--json --compact --no-input --no-color --yes`. - **Pipeable** — JSON on stdout, errors on stderr - **Filterable** — `--select` keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs: ```bash catapult-openfield-connect-pp-cli activities list --agent --select id,name,status ``` - **Previewable** — `--dry-run` shows the request without sending - **Offline-friendly** — sync/search commands can use the local SQLite store when available - **Non-interactive** — never prompts, every input is a flag - **Read-only** — do not use this CLI for create, update, delete, publish, comment, upvote, invite, order, send, or other mutating requests ### Response envelope Commands that read from the local store or the API wrap output in a provenance envelope: ```json { "meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."}, "results": } ``` Parse `.results` for data and `.meta.source` to know whether it's live or local. A human-readable `N results (live)` summary is printed to stderr only when stdout is a terminal AND no machine-format flag (`--json`, `--csv`, `--compact`, `--quiet`, `--plain`, `--select`) is set — piped/agent consumers and explicit-format runs get pure JSON on stdout. ## Paths and state Agents should treat the CLI's path resolver as part of the runtime contract: - Use `--home ` for one invocation, or set `CATAPULT_OPENFIELD_CONNECT_HOME=` to relocate all four path kinds under one root. - Use per-kind env vars only when a specific kind must diverge: `CATAPULT_OPENFIELD_CONNECT_CONFIG_DIR`, `CATAPULT_OPENFIELD_CONNECT_DATA_DIR`, `CATAPULT_OPENFIELD_CONNECT_STATE_DIR`, `CATAPULT_OPENFIELD_CONNECT_CACHE_DIR`. - Resolution order is per-kind env var, `--home`, `CATAPULT_OPENFIELD_CONNECT_HOME`, XDG (`XDG_CONFIG_HOME`, `XDG_DATA_HOME`, `XDG_STATE_HOME`, `XDG_CACHE_HOME`), then platform defaults. - `config` contains settings like `config.toml` and profiles. `data` contains `credentials.toml`, `data.db`, cookies, and auth sidecars. `state` contains persisted queries, jobs, and `teach.log`. `cache` contains regenerable HTTP/cache files. - Stored secrets live in `credentials.toml` under the data dir. Existing legacy `config.toml` secrets are read for compatibility and leave `config.toml` on the first auth write. - Run `catapult-openfield-connect-pp-cli doctor --fail-on warn` to surface path and credential-location warnings. `agent-context` exposes a schema v4 `paths` block for agents that need the resolved dirs. - For MCP, pass relocation through the MCP host config. The MCP binary does not inherit CLI flags: ```json { "mcpServers": { "catapult-openfield-connect": { "command": "catapult-openfield-connect-pp-mcp", "env": { "CATAPULT_OPENFIELD_CONNECT_HOME": "/srv/catapult-openfield-connect" } } } } ``` Fleet precedence: an inherited per-kind env var overrides an explicit `--home` for that kind. Use `CATAPULT_OPENFIELD_CONNECT_HOME` or per-kind vars as durable fleet levers, and use `--home` only for a single invocation. Relocation is not reversible by unsetting env vars; move files manually before clearing `CATAPULT_OPENFIELD_CONNECT_HOME`, or `doctor` will not find credentials left under the former root. ## Automatic learning This CLI ships a self-capturing learning loop. The CLI does its own bookkeeping: every invocation is journaled locally, a failed flag followed by a corrected retry auto-derives a `flag_alias` candidate, and a `teach` on a query family without a playbook auto-synthesizes a `playbook_candidate` from the session's journal. Your job is judgment only: `recall` first, act on surfaced candidates, `teach` the final answer, `playbook amend` when you observe a correction. You never record failures by hand. ### Step 1: `recall` before any discovery Before list/search/drill commands on a new user question, run: ```bash catapult-openfield-connect-pp-cli recall "" --agent ``` The response envelope: ```json { "query": "...", "normalized": "", "query_entities": ["..."], "found": true | false, "match_score": 0.0, "results": [ { "resource_id": "...", "resource_type": "...", "venue": "...", "confidence": 2, "entity_match": "exact|partial|unknown", "source": "taught|preseed|pattern", "warnings": ["..."] } ], "mismatches": [ /* only when --debug-mismatches */ ], "warnings": [ /* top-level */ ], "candidates": [ { "id": 12, "class": "flag_alias | playbook_candidate", "summary": "...", "sightings": 3, "last_seen": "...", "rationale": "...", "next_action": ["", "catapult-openfield-connect-pp-cli learnings confirm 12"] } ], "playbook": { "query_family": "...", "playbook": { "steps": [ { "cmd": "", "purpose": "..." } ], "entity_slots": ["$ENTITY"], "expected_tool_calls": 3 }, "slots_resolved": { "$ENTITY": { "token": "", "canonical": "" } }, "notes": "" }, "notes": "" } ``` Empty-store short-circuit: if the store has no learnings, playbooks, or candidates yet (recall finds nothing and `learnings list` and `learnings candidates` are both empty), skip recall for the rest of this session instead of taxing every query; resume recall-first once something has been taught. ### Step 2: decision tree Read `candidates`, `playbook`, `notes`, `results[0]`, and warnings in that order: ``` if Candidates present (warnings include "candidates_present"): -> candidates are try-then-confirm, never facts. Follow each candidate's two-step next_action verbatim: run the trial command first, then run `learnings confirm ` only after the trial verified the behavior. Reject a wrong candidate with `learnings reject `. -> NEVER re-teach something recall surfaced as a candidate; confirm or reject that candidate instead of teaching a duplicate. -> candidates ride alongside playbooks and resource hits, not instead of them; continue with the branches below after acting on them. if Playbook present: -> READ Playbook.notes verbatim FIRST (workarounds + gotchas the CLI surface doesn't expose) -> replay Playbook.steps in order, substituting Playbook.slots_resolved entries for the entity slot tokens. If a step's slot is unresolved, fall back to discovery for that step only. -> the Playbook's expected_tool_calls is a budget; if you find yourself running materially more, record the divergence via `catapult-openfield-connect-pp-cli playbook amend` at end-of-session. elif Notes present (no Playbook): -> read Notes verbatim before any discovery step; they carry known gotchas for this query family even when no structured choreography exists yet. elif Found AND Results[0].EntityMatch == "exact" AND Results[0].Confidence >= 2: -> skip discovery; fetch live data for Results[*].ResourceID in parallel elif Found AND Results[0].EntityMatch == "partial": -> candidate hint, NOT a hit; read the resource title to validate before trusting elif (any row in Mismatches[] when --debug-mismatches was passed): -> treat as cold start; the stored learning is for a different entity (different canonical resolved from query_entities) else: // Found == false, no playbook, no notes -> cold start; run discovery normally; teach the answer afterward (Step 4). If the family has no playbook yet, that teach auto-synthesizes a playbook candidate from this session's journal - you do not need to record one by hand. ``` Playbook and Notes are orthogonal to the per-resource path. A recall response can carry both a Playbook AND a `Results[]` hit - use both: the Playbook tells you which choreography to run; the resource hits short-circuit specific steps. Defa