Content
17%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a feature specification document rather than an actionable skill for Claude. It extensively explains well-known concepts (statistics formulas, MET values, pace calculations) that waste tokens, provides no executable code or concrete implementation steps, and presents everything in a single monolithic file. The output format examples are detailed but serve more as wishful templates than actionable instructions.
Suggestions
Remove the algorithm explanation section entirely (linear regression, Pearson correlation, pace calculation, MET values) — Claude already knows all of these. This alone would cut ~30% of tokens.
Add a concrete workflow: 1. Read data from specified paths → 2. Validate data completeness → 3. Perform specific analysis → 4. Format output using template → 5. Check for danger signals → 6. Present results with appropriate caveats.
Move the lengthy output format examples and MET reference tables into separate bundle files (e.g., TEMPLATES.md, REFERENCE.md) and reference them from the main skill.
Replace the fictional slash commands (/fitness trend) with actual instructions for Claude: what tools to use, how to read the JSON files, what calculations to perform, and how to structure the response.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~300+ lines. Extensively explains concepts Claude already knows (linear regression formulas, Pearson correlation, MET calculations, what pace is). The algorithm section, medical disclaimers, and lengthy example reports massively inflate token count without adding actionable value. Much of this is textbook content Claude has memorized. | 1 / 5 |
Actionability | The skill describes what analyses to perform and shows example outputs, but provides no executable code, no concrete implementation steps, and no actual data processing logic. The '/fitness trend 3months' commands appear to be fictional slash commands with no backing implementation. The output templates are illustrative but not actionable instructions for Claude to follow. | 2 / 5 |
Workflow Clarity | There is no clear step-by-step workflow for how to actually perform any analysis. The skill lists features and outputs but never sequences the steps: read data → validate → compute → format → present. No validation checkpoints exist for data quality issues despite mentioning a 'data quality check' section. The dangerous signal detection has no workflow for what to do when signals are detected beyond listing them. | 2 / 5 |
Progressive Disclosure | The content is a monolithic wall of text with no references to external files despite clearly needing them. The algorithm explanations, lengthy output templates, MET reference tables, and medical safety guidelines should be in separate reference files. No bundle files exist to support this. The document tries to be everything at once with no layered structure. | 2 / 5 |
Total | 7 / 20 Passed |