CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rampwise-strength

Strength-for-endurance specialist for the Rampwise coaching team. Use for evening or any strength session planning for a runner, cyclist, swimmer or triathlete, "how should I place strength with cardio", concurrent training and interference, heavy vs light strength, strength frequency, injury-prevention strength, "should I lift before a long ride", and reviewing how strength fits in the week. Runs a script on the user's real Garmin data to check timing and frequency. Works with rampwise-recovery (can I lift heavy tonight), rampwise-load-injury (what else is on the plate) and rampwise (final verdict). Swims and multisport sessions count as cardio for the 3-hour gap; goal profiles include triathlon.

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

A well-built instruction-plus-scripts skill: runnable commands, explicit constraints handling, labelled research-vs-practice rules, and a clean overview-to-reference split. The main gaps are a broken reference to a missing references/papers/ directory, missing invocation examples for the planner and history scripts, and inline statistics that duplicate the evidence map despite the skill's own instruction to verify numbers in the paper files.

Suggestions

Fix or remove the 'references/papers/' pointer (and its INDEX.md mention) — the directory is absent from the bundle, so navigation dead-ends; either ship it or point paper verification at references/library.md and evidence-map.md.

Add a complete example invocation for strength_plan.py (e.g. the full command with --goal and athlete.json inputs) and one for strength_history.py, mirroring the copy-paste quality of the strength_check.py examples.

Trim the inline effect sizes and confidence intervals from the evidence section to direction-level statements, deferring exact numbers to references/evidence-map.md — this aligns with the skill's own 'open the file before quoting a sample size or effect' rule and cuts duplicated tokens.

DimensionReasoningScore

Conciseness

Dense and domain-specific with no general-knowledge padding, but the evidence section quotes full statistical detail (CIs, participant counts, SMDs) that duplicates references/evidence-map.md — and the Papers section itself instructs 'Before you quote a sample size, effect or limit, open the file', so the inline numbers could be trimmed to directions.

4 / 5

Actionability

strength_check.py is copy-paste ready with flags, and planner inputs, user-choice keys, and the exit-2 stop-and-ask behavior are concretely specified. However there is no full invocation example for strength_plan.py's generation case or strength_history.py, and 'athlete.py show' is given without a path.

4 / 5

Workflow Clarity

Explicit ordering ('Run athlete.py show first'), recovery-gated rules (RED/AMBER), a defined handoff output block, and stop-and-ask validation give most checkpoints. The end-to-end sequence across sibling skills must be assembled from the frontmatter description and scattered sections rather than one ordered workflow.

4 / 5

Progressive Disclosure

Good one-level-deep structure: the ~60-exercise library and goal profiles live in JSON references, the evidence map in its own file, and the body is a genuine overview. But the body points to 'references/papers/' and its INDEX.md, which do not exist in the bundle — a broken navigation pointer.

4 / 5

Total

16

/

20

Passed

Description

95%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.

A strong description: it states concrete capabilities, gives an explicit 'Use for' clause rich with both colloquial and technical trigger phrases, and cleanly delineates its niche against sibling skills. The only weakness is that it under-sells the skill's concrete outputs (session generation and the handoff block), which keeps specificity just short of the top anchor.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'strength session planning for a runner, cyclist, swimmer or triathlete', 'Runs a script on the user's real Garmin data to check timing and frequency', plus explicit sibling-skill coordination — but omits concrete outputs the skill produces (session generation, handoff block), so it falls short of the comprehensive anchor.

4 / 5

Completeness

Explicitly answers both what ('Strength-for-endurance specialist... Runs a script on the user's real Garmin data to check timing and frequency') and when ('Use for evening or any strength session planning...') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Comprehensive natural-language coverage including quoted colloquial phrases users would actually say ('how should I place strength with cardio', 'should I lift before a long ride') alongside technical synonyms ('concurrent training and interference', 'heavy vs light strength', 'injury-prevention strength', 'strength frequency').

5 / 5

Distinctiveness Conflict Risk

Clear niche (strength-for-endurance within the Rampwise team) with explicit boundaries against sibling skills — 'Works with rampwise-recovery (can I lift heavy tonight), rampwise-load-injury (what else is on the plate) and rampwise (final verdict)' — minimizing wrong-skill triggering.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 possibly missing (references/papers/)

Warning

Total

15

/

16

Passed

Repository

Azahir21/rampwise

Path

skills/rampwise-strength/SKILL.md

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.