Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Use whoop-cli to fetch WHOOP data, generate day briefs/health flags, and export trend data for automation workflows.
Use whoop-cli to fetch WHOOP data, generate day briefs/health flags, and export trend data for automation workflows.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Use the installed whoop command.
Never ask users to paste client secrets/tokens into chat. For first-time auth, the user should run login locally on their own shell. Prefer read-only operational commands in agent flows (summary, day-brief, health, trend, sync pull). Do not run whoop auth login unless the user explicitly asks for login help. Tokens are stored locally at ~/.whoop-cli/profiles/<profile>.json by the CLI.
If whoop is missing: npm install -g @andreasnlarsen/whoop-cli@0.3.1 Optional OpenClaw skill install from package bundle: whoop openclaw install-skill --force
whoop auth status --json If unauthenticated, ask the user to run local login: whoop auth login --client-id ... --client-secret ... --redirect-uri ... Validate: whoop day-brief --json --pretty
Daily: whoop summary --json --pretty whoop day-brief --json --pretty whoop strain-plan --json --pretty whoop health flags --days 7 --json --pretty Activity analysis: whoop activity list --days 30 --json --pretty whoop activity trend --days 30 --json --pretty whoop activity types --days 30 --json --pretty training-only: whoop activity trend --days 30 --labeled-only --json --pretty
WHOOP generic activity rows (often sport_id=-1) are auto-detected and may be unlabeled movement (housework/incidental activity), not intentional training. Do not treat generic activity as confirmed training volume by default. For coaching/training recommendations, default to --labeled-only and report both total vs filtered counts.
Canonical source: whoop activity list --json Prefer built-in filters first (--labeled-only, --generic-only, --sport-id, --sport-name). If custom slicing is needed and jq is available, filter shell-side from raw JSON (example): whoop activity list --days 30 --json | jq '.data.records | map(select(.sport_id != -1))' Export: whoop sync pull --start YYYY-MM-DD --end YYYY-MM-DD --out ./whoop.jsonl --json --pretty
Canonical state: ~/.whoop-cli/experiments.json only. Plan experiments with context at creation time: whoop experiment plan --name ... --behavior ... --start-date YYYY-MM-DD [--end-date YYYY-MM-DD] --description ... --why ... --hypothesis ... --success-criteria ... --protocol ... --json --pretty Update context without creating duplicate state: whoop experiment context --id ... [--description ... --why ... --hypothesis ... --success-criteria ... --protocol ...] --json --pretty Check lifecycle/status with: whoop experiment status [--status planned|running|completed] [--id ...] --json --pretty Evaluate outcomes with: whoop experiment report --id ... --json --pretty Profile scope is strict by default (active --profile only). Use --all-profiles only when cross-profile visibility is explicitly needed. Prefer output field sourceOfTruth (path to canonical state file); experimentsFile is kept as compatibility alias. Avoid duplicating experiment state into other files unless the user explicitly asks for separate notes.
Never print client secrets or raw tokens. Keep API errors concise and actionable. Treat this integration as unofficial/non-affiliated.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.