CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rampwise-analyze

Activity analysis and injury-risk watch for the Rampwise coaching team. Use for "analyse my last run/ride/swim/brick/strength session", "how did this week compare with last week" (works whether or not there was an activity today), week-over-week or month-over-month change, pace/speed/efficiency trend, "am I at risk of getting injured", "is something off", overuse warning signs, pain check-ins, and before adding load. Compares the latest session with the last similar one, compares the last 7 days with the 7 days before (and the calendar week so far), and raises evidence-labelled injury-risk flags from load, recovery and the user's own pain reports. Flags are prompts to look, never a diagnosis. Works with rampwise-recovery, rampwise-load-injury, rampwise-aerobic-base, rampwise-adapt and rampwise-report. Handles swims (pace per 100 m) and brick sessions: the run after a bike is shown against your last normal run.

Quality

90%

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

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 well-built operational skill body: exact runnable commands, a handoff template, explicit thresholds, evidence-labelled flags, and honest limits. The main improvement areas are trimming inline citation detail that duplicates evidence-map.md and tightening reference hygiene (dangling references/papers/ path, unlinked library.md).

Suggestions

Trim the citation parentheticals in the flags table to bare evidence labels (e.g. "research (Frandsen 2025)") since references/evidence-map.md already carries the study details, saving table tokens.

Fix reference hygiene: either add the missing references/papers/ directory (with INDEX.md) the body points to, or link references/library.md from the Papers section so the paper inventory is reachable in one level from SKILL.md.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — no explanations of concepts Claude already knows — but the flags table carries inline citation parentheticals (e.g. "a 10 % rule did not prevent injuries in an RCT, Buist 2008") whose details already live in references/evidence-map.md and could be trimmed to just the evidence label.

4 / 5

Actionability

Fully executable: copy-paste commands with exact paths and all flags (--json, --today YYYY-MM-DD, --id N, --no-readiness), concrete check-in syntax (athlete.py check-in --area .. --pain N [--gait-change]), a handoff block template, and explicit thresholds with their file location (scripts/analysis.py).

5 / 5

Workflow Clarity

The sequence is present across sections (run scripts → lead with the comparison → flags → one action per flag → ask and record → handoff block) with real checkpoints (gait-change pain means stop and recommend a clinician; verify a paper before quoting effects). It falls short of a 5 because no single explicit end-to-end order ties the sections together.

4 / 5

Progressive Disclosure

Good structure: references/evidence-map.md and scripts/analysis.py are clearly signaled and exist, and content is appropriately split. Minor gaps: the body points to references/papers/ which is absent from the bundle, and references/library.md is never linked from SKILL.md (reachable only as a second level via evidence-map.md).

4 / 5

Total

17

/

20

Passed

Description

96%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 third-person capabilities, an explicit 'Use for' clause with natural quoted trigger phrases, and clear coordination with sibling skills. The only weakness is potential trigger overlap on injury-risk phrasing with the sibling rampwise-load-injury skill.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Compares the latest session with the last similar one, compares the last 7 days with the 7 days before (and the calendar week so far), and raises evidence-labelled injury-risk flags" — plus per-sport handling (swim pace per 100 m, brick sessions), comprehensively covering the skill's scope in third person.

5 / 5

Completeness

Both what and when are explicit: an explicit "Use for" clause with concrete trigger phrases, followed by a clear multi-part statement of what the skill does (session-vs-similar, 7-day-vs-7-day, calendar week, evidence-labelled flags).

5 / 5

Trigger Term Quality

It quotes natural user phrasings ("analyse my last run/ride/swim/brick/strength session", "how did this week compare with last week", "am I at risk of getting injured", "is something off") and covers synonyms and variations: week-over-week, month-over-month, pace/speed/efficiency trend, overuse warning signs, pain check-ins, before adding load.

5 / 5

Distinctiveness Conflict Risk

It is scoped to the Rampwise coaching team and explicitly coordinates with named sibling skills ("Works with rampwise-recovery, rampwise-load-injury, rampwise-aerobic-base, rampwise-adapt and rampwise-report"), but injury-risk triggers like "am I at risk of getting injured" and "overuse warning signs" plausibly overlap with the closely related rampwise-load-injury skill.

4 / 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-analyze/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.