CtrlK
BlogDocsLog inGet started
Tessl Logo

fitness-analyzer

分析运动数据、识别运动模式、评估健身进展,并提供个性化训练建议。支持与慢性病数据的关联分析。

38

Quality

38%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/fitness-analyzer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

17%Scale 1-5

Reviews 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.

DimensionReasoningScore

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

Description

58%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description provides a solid set of concrete capabilities in the fitness/exercise data analysis domain and includes a distinctive feature (chronic disease correlation). Its main weaknesses are the absence of an explicit 'Use when...' trigger clause and limited natural keyword coverage that users might employ when requesting this skill.

Suggestions

Add an explicit 'Use when...' clause with trigger phrases, e.g., '当用户提到运动数据分析、健身计划、锻炼记录、体能评估或运动与慢性病关联时使用'

Include more natural synonyms and variations users might say, such as '锻炼', '体能', '步数', '心率', '卡路里', '运动记录' to improve trigger term coverage

DimensionReasoningScore

Specificity

Lists several specific actions: analyzing exercise data, identifying movement patterns, evaluating fitness progress, and providing personalized training recommendations. Also mentions chronic disease data correlation analysis. Minor gaps in coverage (e.g., no mention of specific data formats or metrics).

4 / 5

Completeness

The 'what' is clearly stated with multiple concrete actions. However, there is no explicit 'when' clause (e.g., 'Use when...' or equivalent trigger guidance), which caps this dimension at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Contains relevant domain keywords like '运动数据' (exercise data), '健身进展' (fitness progress), '训练建议' (training recommendations), '慢性病' (chronic disease). However, it lacks common synonyms and variations users might naturally say, such as '锻炼' (workout), '体能' (physical fitness), '步数' (step count), '心率' (heart rate), or file format mentions.

3 / 5

Distinctiveness Conflict Risk

The combination of exercise/fitness analysis with chronic disease correlation creates a fairly distinct niche. There is minor overlap risk with general health data analysis or generic fitness skills, but the specific combination of fitness progress evaluation and chronic disease linkage is distinctive.

4 / 5

Total

14

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

9

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.