CtrlK
BlogDocsLog inGet started
Tessl Logo

fitness-nutrition

Workout planning, macros, and body metrics via wger/USDA.

57

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/health/fitness-nutrition/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a strong, highly actionable skill document with executable code throughout, clear sequencing, and sensible progressive disclosure to real bundle files; its main weaknesses are minor redundancy in the Quick Reference table and verification checkpoints that are post-hoc rather than interactive feedback loops.

DimensionReasoningScore

Conciseness

Mostly lean and efficient with executable code, dense wger ID reference tables, and delegated science to FORMULAS.md; minor over-explanation from the 'Quick Reference' table duplicating endpoints already covered in Procedure.

4 / 5

Actionability

Fully executable, copy-paste-ready curl+python inline scripts for every common case (search, details, filter, food search, food details) plus explicit body_calc.py subcommand invocations covering all calculators.

5 / 5

Workflow Clarity

Clear sequenced steps (identify -> reference IDs -> fetch/present) with a Verification section providing post-run confirmation checkpoints; verification is post-hoc rather than an integrated validate->fix->retry feedback loop, keeping it below 5.

4 / 5

Progressive Disclosure

Well-structured sections with clearly signaled one-level-deep references (references/FORMULAS.md, scripts/body_calc.py) that exist as real files; the inlined wger ID tables and the un-surfaced scripts/nutrition_search.py keep it just below 5.

4 / 5

Total

17

/

20

Passed

Description

53%Weight 40%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 conveys a clear fitness/nutrition niche and named data sources, but it is missing an explicit 'when to use' trigger clause and several natural user keywords, which limit its completeness and trigger-term coverage.

Suggestions

Add a 'Use when ...' clause listing concrete triggers (e.g. 'Use when the user asks about workouts, gym routines, macros, calories, BMI, TDEE, or one-rep max').

Expand natural keywords to include synonyms users actually say: calories, diet, exercise, nutrition, protein, BMI, TDEE.

Enumerate the offline calculators (BMI, TDEE, 1RM, macros, body fat %) in the description to make capabilities more concrete.

DimensionReasoningScore

Specificity

Names the domain and concrete capability areas ('Workout planning, macros, and body metrics') plus the data sources (wger/USDA), but stops at a few actions rather than comprehensively enumerating exercise lookup, nutrition search, TDEE/1RM/body-fat calculations.

3 / 5

Completeness

Has a clear 'what' (workout planning, macros, body metrics via wger/USDA) but no explicit 'Use when...' trigger clause; per the guidelines a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Includes several natural terms users would say ('Workout', 'macros', 'body metrics') but omits common variations like calories, diet, exercise, nutrition, BMI, TDEE, and protein.

3 / 5

Distinctiveness Conflict Risk

A clear fitness/nutrition niche anchored to specific data sources (wger/USDA) makes it largely distinct from other skills, with only minor overlap risk; lacks fully explicit trigger phrases that would push it to 5.

4 / 5

Total

13

/

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.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

13

/

16

Passed

Repository
NousResearch/hermes-agent
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.