CD whoopskill
WHOOP CLI with health insights, trends analysis, and data fetching (sleep, recovery, HRV, strain).
As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
The files contain someone else's key or token. If it is live, your agent will call third-party services under a stranger's identity; if it was revoked, the skill's scripts simply fail. Such a key often arrives with the author's whole workspace, personal data included.
The key is visible to everyone who downloaded the skill and has likely been copied by catalog-scanning bots already. Revoke it now, check bills and access logs, then reissue.
How to improve
- Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 6
-
high Secrets in code
meta-credential-files.env.txtCredential / dotenv files bundled with the skill (1).env.txt
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:31High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha512-GZMB+a0mO…4cw+w1WV…UED+1X8a…sJi+8mgpw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:201High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…HK5+NE/tvnRLbIqUWa+0E9N4WNMjmp/kXXP…R8w==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:422High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…78O/B3Kkh+nKABUF++bvJv…56W+C8F9…X6m+IktJnIb1Jjg==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:507High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…CEn+F6ft…izg==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:662High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…eDC+zVo0…NXH+tu0NalHolcJ/QAGq…IMw==",
detector
Files scanned: 19. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 46/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (web, node) that frontmatter does not declare
- 100Steps. 28 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1386 tokens
- 100Running it twice. No mutating operations
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 98: 120–800 characters recommended
- +4Structure: 1 headings, hard to scan
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Step-by-step instructions: 28 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.