Back to skill
Skillv0.1.2
ClawScan security
WHOOP (Official API) · ClawHub's context-aware review of the artifact, metadata, and declared behavior.
Scanner verdict
SuspiciousMar 13, 2026, 6:04 AM
- Verdict
- suspicious
- Confidence
- medium
- Model
- gpt-5-mini
- Summary
- The skill appears to implement a legitimate WHOOP OAuth + fetch workflow, but the package metadata (no required envs / no primary credential) is inconsistent with the scripts and SKILL.md which require WHOOP_CLIENT_ID, WHOOP_CLIENT_SECRET, and WHOOP_REDIRECT_URI; review before installing.
- Guidance
- This package looks like a reasonable WHOOP OAuth client: it talks only to WHOOP endpoints, stores tokens locally (default ~/.config/openclaw/whoop/token.json), and renders user-facing summaries. Before installing: 1) Confirm the source/owner is trusted — the registry metadata and the SKILL.md disagree about required environment variables; the scripts DO require WHOOP_CLIENT_ID, WHOOP_CLIENT_SECRET, and WHOOP_REDIRECT_URI. 2) Provide only a WHOOP app/client with minimal scopes (e.g., read:recovery, read:sleep, read:cycles). 3) Consider setting WHOOP_TOKEN_PATH to a secure location and verify the token file permissions after creation; revoke the app/client from your WHOOP developer dashboard if you later remove the skill. 4) Understand loopback mode opens a local HTTP listener to capture the OAuth code — only use that if you trust the environment and the redirect URI. 5) Ask the publisher to correct the registry metadata to declare the required env vars and primary credential so automated permission reviews work correctly.
Review Dimensions
- Purpose & Capability
- noteThe name, description, SKILL.md, and included scripts all match: this is an OAuth-based WHOOP client that fetches and renders WHOOP v2 metrics. The requested capabilities (fetching recovery/sleep/cycle/workout/profile data, storing tokens) are coherent with the stated purpose. However the registry metadata declares no required env vars or primary credential while the runtime instructions and code clearly require WHOOP_CLIENT_ID, WHOOP_CLIENT_SECRET, and WHOOP_REDIRECT_URI — that metadata mismatch is suspicious and should be corrected.
- Instruction Scope
- okSKILL.md instructs the agent to perform OAuth login, fetch WHOOP endpoints, normalize and render results, and optionally send via OpenClaw message tool or cron. The included scripts only access the WHOOP API, read/write the designated token file, and operate on input/output JSON files; they do not attempt to read unrelated system files or other credentials. Loopback mode starts a local HTTP listener to capture the OAuth code (standard for authorization code flow).
- Install Mechanism
- okNo install spec (instruction-only + bundled scripts). There are no downloads, package installs, or external installers in the manifest — the risk from installation is limited to running the included Python scripts. All code is present in the bundle for review.
- Credentials
- concernThe scripts legitimately require WHOOP_CLIENT_ID, WHOOP_CLIENT_SECRET, and WHOOP_REDIRECT_URI (and optionally WHOOP_TOKEN_PATH / WHOOP_TZ). Those credentials are proportionate for OAuth. The concern is that the registry metadata lists no required env vars and no primary credential — this mismatch could cause users or automated systems to grant insufficient or excessive permissions unknowingly. Token storage to ~/.config/openclaw/whoop/token.json is expected; the code attempts to set file permissions to 0600.
- Persistence & Privilege
- okThe skill does not request special platform privileges or set always:true. It writes a token file under the user's home config directory and creates that directory if needed — this is normal for an OAuth client. It does not modify other skills or system-wide agent settings.