CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rampwise-planner

One training planner for every goal: a race (17 events: running, triathlon, duathlon, cycling, open-water swim) or NO target (build endurance and aerobic base for any mix of run, ride and swim), from the athlete's own Garmin data (--from-garmin) or answers, with persistent goals (athlete.json). Use to build or adjust a multi-week plan, check the run gate (a tracked goal, optional lock), set pace targets after a time trial, view a plan, or export it (.ics, .csv, Zwift, MRC, Garmin .fit workouts when heart-rate data are known). Starts from aerobic base; quality sessions are on by default and locked per athlete only when their own data says so (active injury, a RED reset week, their settings). Respects recovery, load and injuries. Every rule is labelled research or practice in references/evidence-map.md.

Quality

81%

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

63%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 exceptionally concrete — real commands, flags, exit codes and validation loops — and the workflow is well sequenced with error recovery. It is dragged down by wall-of-text paragraphs, rules and options repeated across sections, study details inlined that already live in evidence-map.md, and several referenced files that do not exist in the bundle.

Suggestions

Break the 'Garmin workouts and the session menu' and heart-rate-rule sections into tables or lists, and strip the inlined study statistics (Lu 2025, Heiber 2024, Eur J Appl Physiol 2025) down to pointers into references/evidence-map.md, where they are already documented.

State the quality-session lock rules and the plan.py/build_plan.py --legacy relationship once each instead of three and two times respectively, and add the missing referenced files (references/papers/INDEX.md, docs/EVIDENCE-DEPTH.md) or remove the references.

Give the calendar connector operations and `athlete.py injury-add` the same explicit syntax treatment as build_plan.py so every instruction is copy-paste ready.

DimensionReasoningScore

Conciseness

Almost every token is skill-specific (settings paths, scripts, rules) with no explanation of concepts Claude already knows, but it is far from tight: the session-menu paragraph is a ~450-word run-on, the quality-lock rules are stated in three places, `--legacy` and the export formats each appear twice, and specific dates ("set by the athlete 2026-11-16") are inlined rather than isolated, so it sits at 'mostly efficient but could be tightened' rather than the minor-trim level of 4.

3 / 5

Actionability

Concrete, mostly copy-paste-ready commands throughout: `python -X utf8 "<skills>/rampwise/scripts/athlete.py" show`, `build_plan.py --start YYYY-MM-DD --weeks 4 --readiness green|amber|red --out ...`, `athlete.py set hr.easy_band '{"run":[lo,hi],"bike":[lo,hi]}'`, `plan.py --list-events`; minor gaps keep it from 5 — the calendar connector operations (`list_events`, `delete_event`, `create_event`) and `athlete.py injury-add ...` are described in prose without their syntax.

4 / 5

Workflow Clarity

A clear numbered sequence (State → Build → Explain → Calendar → Weekly re-sync) with explicit validation checkpoints (exit code 2 with the questions to ask, "every file is decoded again as a check", the event planner "stops and lists" missing inputs, list-before-delete-before-create on the calendar) and error-recovery loops; it falls short of 5 because the plan.py/build_plan.py legacy-forwarding relationship is explained late and confusingly, and cross-skill inputs (readiness, head-coach handoffs) are assumed rather than sequenced.

4 / 5

Progressive Disclosure

References are one level deep and clearly signaled (`references/evidence-map.md` "full table", `library.md` "rows 20-24"), but the body inlines content that belongs in those references (Lu 2025 / Heiber 2024 sample sizes and bpm errors duplicated from evidence-map.md) and points to paths absent from the bundle (`references/papers/` with `INDEX.md`, `docs/EVIDENCE-DEPTH.md`), which is more than the 'minor organization gaps' of the 4 anchor.

3 / 5

Total

14

/

20

Passed

Description

92%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 dense, highly specific description that explicitly covers what the skill does and when to use it, with concrete export formats and data sources. Its only weakness is that race types are given as categories rather than the natural event names (marathon, 5k, Ironman) a user would actually type.

DimensionReasoningScore

Specificity

Lists multiple concrete actions with named artifacts: "build or adjust a multi-week plan", "check the run gate", "set pace targets after a time trial", "view a plan, or export it (.ics, .csv, Zwift, MRC, Garmin .fit workouts...)" — coverage is comprehensive across build, adjust, measure, view and export, so it matches the top anchor rather than the 'minor gaps' anchor at 4.

5 / 5

Completeness

Explicitly answers both: the 'what' ("One training planner for every goal: a race ... or NO target ... from the athlete's own Garmin data ... or answers") and the 'when' ("Use to build or adjust a multi-week plan, check the run gate ..., set pace targets after a time trial, view a plan, or export it"), matching the anchor that requires a clear what AND an explicit when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural-term coverage ("training planner", "race", "triathlon", "Garmin", "endurance and aerobic base", "time trial", "pace targets") but the 17 race types are only named as categories, missing the concrete distances users actually say ("marathon", "5k", "half marathon", "Ironman"), which keeps it below the comprehensive-synonyms anchor at 5.

4 / 5

Distinctiveness Conflict Risk

A clear niche (Garmin-data-driven multi-week training plans with named export formats, run gate, athlete.json persistence) with triggers unlikely to fire for unrelated skills; the '4' anchor's 'minor overlap risk' does not apply because nothing generic remains.

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-planner/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.