whoop
WHOOP Central - OAuth + scripts to fetch WHOOP data (sleep, recovery, strain, workouts). Use when user asks about their sleep, recovery score, HRV, strain, or workout data.
86
Quality
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that hits all the key criteria. It clearly identifies the specific platform (WHOOP), lists concrete data types it handles, and provides explicit trigger terms that users would naturally say. The 'Use when...' clause effectively guides skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'OAuth + scripts to fetch WHOOP data' with explicit data types '(sleep, recovery, strain, workouts)'. Uses third person voice appropriately. | 3 / 3 |
Completeness | Clearly answers both what ('OAuth + scripts to fetch WHOOP data') AND when ('Use when user asks about their sleep, recovery score, HRV, strain, or workout data') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would actually say: 'sleep', 'recovery score', 'HRV', 'strain', 'workout data'. These are terms WHOOP users commonly use when discussing their health metrics. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche - specifically targets WHOOP device data with brand-specific terminology. Unlikely to conflict with generic fitness or sleep tracking skills due to explicit WHOOP branding and specific metrics like HRV and strain. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, highly actionable skill with excellent concrete commands and clear workflows for WHOOP API integration. The main weakness is verbosity - the troubleshooting section is extensive and the multiple authentication paths add length. The content would benefit from splitting detailed troubleshooting and Postman setup into separate reference files.
Suggestions
Move the detailed Postman authentication instructions to a separate POSTMAN_AUTH.md file and reference it from the main skill
Move the troubleshooting section to a TROUBLESHOOTING.md file, keeping only the most common issues inline
Condense the 'If your WHOOP Redirect URL is...' section - it repeats information already covered in the auth.js section
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some verbose sections, particularly the extensive troubleshooting and multiple authentication paths. The Postman setup instructions are detailed but could be more condensed given Claude's ability to follow OAuth flows. | 2 / 3 |
Actionability | Excellent actionability with copy-paste ready commands throughout, specific bash commands, exact URLs, and concrete examples for every operation including JSON output flags and time filters. | 3 / 3 |
Workflow Clarity | Clear numbered sequences for setup (0-4 steps), explicit verification checkpoints ('node src/verify.js'), and good error recovery guidance in troubleshooting. The Postman checklist explicitly warns about common pitfalls. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is monolithic - the extensive troubleshooting section and detailed Postman instructions could be split into separate reference files. No external file references for advanced content. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- Repository
- Demerzels-lab/elsamultiskillagent
- Commit
45f9fac
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.