CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rampwise-load-injury

Training-load and injury-risk specialist for the Rampwise coaching team. Use for "am I doing too much", weekly volume, ramp rate, longest run/ride/swim, load spikes, rest days, training streaks, hard-day spacing, injury risk, "can I add a long run/ride", build-up pacing for a long event, and before adding volume. Runs a script on the user's real Garmin activity history. Works with rampwise-recovery (can the body absorb it), rampwise-strength (what else is on the plate) and rampwise (final verdict). Counts swimming, multisport activities and brick sessions (bike then run) as load; the spike rule is research for running only (swim and ride are not studied).

Quality

90%

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

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.

A high-quality specialist skill body: executable commands, a precise evidence hierarchy with firmness labels, a concrete output contract, and honest limits. The main gaps are minor — some evidence detail duplicated between the body and the reference file, and a papers/ navigation target referenced but missing from the bundle.

Suggestions

Trim the inline hazard-ratio and sample-size detail in rules 1-2 to one-line summaries and defer the numbers to references/evidence-map.md, which already carries them.

Ship references/papers/ (or its INDEX.md) referenced by the "Papers" section, or state explicitly that papers are fetched on demand via paper_fetch.py so the navigation target is not dangling.

Add a brief fallback step for the Run section (what to do if load_check.py errors or returns no activities) to make the workflow's error path explicit.

DimensionReasoningScore

Conciseness

Every section carries domain-specific evidence content Claude would not know (hazard ratios, cohort sizes, study limits) with no padding of basic concepts. Not 5 because the citation detail in rules 1-2 (e.g. "hazard ratios 1.64 for 10-30 %, 1.52 for 30-100 %, 2.28 for over 100 %") duplicates what is expanded in references/evidence-map.md, and the opening "Paths" blockquote is long for what it conveys.

4 / 5

Actionability

Copy-paste-ready commands with the <skills> placeholder defined up front ("python -X utf8 \"<skills>/rampwise-load-injury/scripts/load_check.py\" --weeks 8" plus a --json variant), a literal handoff block template with exact fields, and a concrete fallback command ("run paper_fetch.py \"<author year>\""). Covers the common cases fully.

5 / 5

Workflow Clarity

Sections follow the natural sequence (run script, interpret flags against the rules, check the evidence before quoting, communicate, emit handoff block) and include checkpoints such as "Before you quote a sample size, effect or limit, open the file" and WARN triage guidance. Not 5 because the sequence is implicit in section order rather than explicit, and there is no recovery step if the script itself fails.

4 / 5

Progressive Disclosure

A well-sectioned ~55-line overview with one-level-deep references, and the referenced references/evidence-map.md and scripts/load_check.py are real bundle files. Not 5 because the body points to "references/papers/" with an "INDEX.md" that is absent from the bundle, and the rules section inlines study detail that also lives in evidence-map.md rather than fully deferring to it.

4 / 5

Total

17

/

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: concrete actions, an explicit 'Use for' clause with natural trigger phrases, and explicit delineation from sibling skills. The only weakness is that the capability list is slightly thinner than the (excellent) trigger list, leaving the core analytical output partially implied.

DimensionReasoningScore

Specificity

Names several concrete actions — "Runs a script on the user's real Garmin activity history", "Counts swimming, multisport activities and brick sessions (bike then run) as load" — with minor coverage gaps (the core flag/assessment action is implied via triggers rather than stated as an action). Not 3 because more than 1-2 specific actions are named; not 5 because the action list is thinner than the extensive trigger enumeration.

4 / 5

Completeness

Explicitly answers both: what ("Training-load and injury-risk specialist... Runs a script on the user's real Garmin activity history") and when ("Use for 'am I doing too much'... and before adding volume") with concrete trigger phrases. Matches the anchor-5 example structure exactly.

5 / 5

Trigger Term Quality

Comprehensive natural phrasing users would actually say: "am I doing too much", "can I add a long run/ride", weekly volume, ramp rate, load spikes, rest days, training streaks, hard-day spacing, build-up pacing for a long event. Anchor 5 fits directly; no common synonym or variation is obviously missing.

5 / 5

Distinctiveness Conflict Risk

Clear niche within the Rampwise suite with distinct triggers, and it explicitly delineates sibling boundaries ("Works with rampwise-recovery (can the body absorb it), rampwise-strength (what else is on the plate) and rampwise (final verdict)"). Minimal conflict risk; the running-only scope of the spike rule is even stated.

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-load-injury/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.