← Back to Skills Marketplace
WHOOP CLI for Agents
by
andreasnlarsen
· GitHub ↗
· v0.3.1
693
Downloads
0
Stars
1
Active Installs
8
Versions
Install in OpenClaw
/install whoop-cli
Description
Use whoop-cli to fetch WHOOP data, generate day briefs/health flags, and export trend data for automation workflows.
Usage Guidance
Do not install or enable this skill until you verify its origin. Steps to consider: 1) Confirm the npm package and GitHub repo referenced in SKILL.md (@andreasnlarsen/whoop-cli) are legitimate and match the maintainer listed in the registry. 2) Be wary that the registry metadata omits the env vars and install instructions that SKILL.md requires — ask the publisher to fix the manifest or provide a signed/verified source. 3) If you proceed, install the whoop CLI yourself (npm install -g @andreasnlarsen/[email protected]) and perform OAuth login locally; never paste client secrets into chat. 4) Inspect ~/.whoop-cli profiles after login to confirm tokens are local and as expected. 5) Prefer read-only commands (summary, day-brief, health, trend, sync pull) and avoid granting the agent permissions to perform auth/login on your behalf. If the skill's origin cannot be confirmed or the manifest corrected, avoid enabling it.
Capability Analysis
Type: OpenClaw Skill
Name: whoop-cli
Version: 0.3.1
The skill bundle appears benign. It provides instructions for an AI agent to interact with the `whoop-cli` for health data access. The `SKILL.md` explicitly includes strong security guardrails, instructing the agent to never ask for or print client secrets/tokens, to prefer local login, and to use read-only commands. While it includes commands to export data to local files (`whoop sync pull --out ./whoop.jsonl`) and manage local experiment state (`~/.whoop-cli/experiments.json`), these are legitimate functions of the stated purpose and lack any indication of malicious intent such as exfiltration, unauthorized execution, or persistence mechanisms. All commands are standard uses of the `whoop` CLI and `npm` for installation.
Capability Assessment
Purpose & Capability
The skill's stated purpose (agent-friendly whoop-cli access for briefs, health flags, and exports) matches the commands and workflows in SKILL.md. Requesting WHOOP OAuth credentials and a whoop binary is coherent with that purpose. However, the registry metadata lists no required binaries, no env vars, and no install spec while SKILL.md clearly documents both required env vars and an npm install — this inconsistency is unexpected and should be resolved before trusting the skill.
Instruction Scope
SKILL.md instructs the agent to run whoop CLI commands that read/write local files (e.g., ~/.whoop-cli/profiles/*.json, experiments.json) and to prefer read-only operations; it explicitly warns not to request secrets in chat and to let the user perform login locally. Those runtime instructions are generally scoped to the stated purpose, but they also allow or suggest commands that could surface local token files or request client secrets for login; the guidance relies on human enforcement. Given the mismatch between declared and actual requirements, it's unclear whether the agent will be constrained to the safe behaviors described.
Install Mechanism
SKILL.md provides an npm global install (package @andreasnlarsen/[email protected]), which is a reasonable distribution mechanism for a Node CLI, but the registry's top-level metadata contained no install spec. The presence of install instructions only in SKILL.md (not in the registry) is an inconsistency. Installing an npm package globally requires runtime privileges and should be done from a trusted source; SKILL.md points to a GitHub repo, but the skill listing has no homepage and an unknown source, increasing risk.
Credentials
SKILL.md requires WHOOP_CLIENT_ID, WHOOP_CLIENT_SECRET, and WHOOP_REDIRECT_URI (with WHOOP_CLIENT_SECRET declared as primaryEnv) which are appropriate for OAuth-based CLI access. The registry metadata, however, declared no required env vars or primary credential — this mismatch is a red flag. Otherwise, the skill does not request additional unrelated credentials and restricts operations to local token files and read-only commands where possible.
Persistence & Privilege
The skill does not request always:true, does not claim persistent system-wide configuration changes, and is instruction-only (no code written to disk by the registry). SKILL.md mentions the CLI will store tokens under ~/.whoop-cli and offers an optional local install command, which is normal for a CLI integration and within scope for this purpose.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install whoop-cli - After installation, invoke the skill by name or use
/whoop-cli - Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.3.1
Adds structured experiment context fields (description/why/hypothesis/success criteria/protocol) and experiment context update command; pins installer to @andreasnlarsen/[email protected]
v0.3.0
Align installer to @andreasnlarsen/[email protected] and include profile-scoped experiment plan/status/report protocol with single-source state guidance
v0.2.0
Activity-first command surface; remove workout commands; add agent-safe activity filtering guidance and pin installer to @andreasnlarsen/[email protected]
v0.1.6
Sync skill installer to npm package @andreasnlarsen/[email protected] (auth ENOENT fix release).
v0.1.5
Set clearer listing title emphasizing agent-first WHOOP CLI workflow.
v0.1.4
Update listing description to highlight agent-friendly CLI workflow and reduced raw-API plumbing.
v0.1.3
Add explicit required binary/env metadata and stronger credential-handling guidance (local login, no secrets in chat).
v0.1.2
Initial public release of the WHOOP CLI OpenClaw skill.
Metadata
Frequently Asked Questions
What is WHOOP CLI for Agents?
Use whoop-cli to fetch WHOOP data, generate day briefs/health flags, and export trend data for automation workflows. It is an AI Agent Skill for Claude Code / OpenClaw, with 693 downloads so far.
How do I install WHOOP CLI for Agents?
Run "/install whoop-cli" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is WHOOP CLI for Agents free?
Yes, WHOOP CLI for Agents is completely free (open-source). You can download, install and use it at no cost.
Which platforms does WHOOP CLI for Agents support?
WHOOP CLI for Agents is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created WHOOP CLI for Agents?
It is built and maintained by andreasnlarsen (@andreasnlarsen); the current version is v0.3.1.
More Skills