CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rampwise-adapt

Adaptive next-day session for the Rampwise coaching team. Use for "what should I do tomorrow", "adjust tomorrow's session", "I slept badly, change my plan", "keep my calendar in sync with how I feel", "progress my training", daily or morning re-planning, and after a missed or hard session. Looks at the saved plan, today's readiness, the injury-risk watch (rampwise-analyze) and how much of the last two weeks' plan was done, then decides per planned session: keep, small progression, easy swap, shorter, recovery spin or rest. Builds the changed workout (and optional .fit file) and prepares the calendar update for the main session to apply after approval. Conservative by default; progression only when everything is green. Works with rampwise-planner, rampwise-recovery, rampwise-analyze and rampwise-report. Adapts event plans (all sports) and Garmin-history plans: swims shortened or easy, brick runs dropped on amber or red, race day never changed.

Quality

93%

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

90%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 lean, highly actionable skill body: exact thresholds, runnable commands, and a well-guarded calendar procedure with approval and fallback checkpoints. The two weaker spots are the absence of a single ordered end-to-end flow and a Papers section that references a nonexistent directory, plus an orphaned library.md.

Suggestions

Fix the Papers section: `references/papers/` and `INDEX.md` do not exist in this bundle — point instead to the 'Full-text reading notes' section of `references/evidence-map.md` and to `references/library.md`, which already explain that this skill reuses the other skills' papers.

Reference `references/library.md` somewhere in the body (e.g. from the Papers section) so the paper library is discoverable instead of orphaned.

Add one short ordered flow at the top (run `next_session.py` → apply the decision table → ask/apply the calendar update → `--record` after an accepted progression → emit the handoff block) so the end-to-end sequence does not have to be assembled from separate sections.

DimensionReasoningScore

Conciseness

The body is dense and operational throughout — a decision table with exact multipliers ("shorter (x0.7, or x0.85 for long sessions)"), run commands, a numbered calendar procedure, and a handoff template. It explains nothing Claude already knows and contains no padded sections, matching the 'every token earns its place' anchor.

5 / 5

Actionability

Fully executable guidance: copy-paste commands with all flags ("--days 3", "--write-fit", "--record"), exact numeric thresholds ("at least 85 % of the last 14 days of plan done, this week up 10 % or less, at least 7 days since the last progression"), concrete payload fields ("notificationLevel: NONE"), and a filled-in handoff block format. It is not a 4 because the commands and thresholds leave no gaps for the common cases.

5 / 5

Workflow Clarity

The calendar sub-workflow is numbered with real checkpoints ("ask first" on approval, "check the user's own events for clashes", "If the connector is not authorised, give the change as text", re-run with --record after acceptance). It falls short of 5 because the end-to-end sequence (run script → decide → apply calendar → record → handoff) is distributed across topic sections rather than given as one ordered flow, and there is no re-validation step after an update is applied.

4 / 5

Progressive Disclosure

Good structure with a clearly signaled, one-level-deep reference ("rules and evidence: `references/evidence-map.md`", which exists and holds the bulk detail). Not a 5 because the Papers section points to `references/papers/` and `INDEX.md`, which do not exist in the bundle, and `references/library.md` is never referenced from the body — minor organization gaps rather than buried or inline-bloated content, so above anchor 3.

4 / 5

Total

18

/

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: third-person voice, concrete capabilities, and natural user-quoted trigger phrases that clearly answer both what the skill does and when to use it. The only weakness is mild overlap risk with the sibling rampwise-planner skill on the broadest trigger phrases.

DimensionReasoningScore

Specificity

It lists multiple concrete actions with comprehensive coverage: "Looks at the saved plan, today's readiness, the injury-risk watch", "decides per planned session: keep, small progression, easy swap, shorter, recovery spin or rest", "Builds the changed workout (and optional .fit file) and prepares the calendar update". Not a 4 because inputs, decision set, outputs, and per-sport adaptations are all explicitly named with no meaningful coverage gap.

5 / 5

Completeness

Both halves are explicit: an explicit trigger clause ("Use for 'what should I do tomorrow'... after a missed or hard session") and a concrete what (per-session decisions, built workout/.fit file, calendar update prepared for approval). Not a 4 because the 'when' is specific and concrete rather than merely present.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases in the user's own voice: "what should I do tomorrow", "adjust tomorrow's session", "I slept badly, change my plan", "keep my calendar in sync with how I feel", plus variations like "daily or morning re-planning" and "after a missed or hard session". Not a 4 because both direct quotes and situational synonyms are covered.

5 / 5

Distinctiveness Conflict Risk

Clear niche — next-day adaptation of an existing plan — with explicit sibling delineation ("Works with rampwise-planner, rampwise-recovery, rampwise-analyze and rampwise-report"). Not a 5 because broad triggers like "what should I do tomorrow" and "progress my training" could plausibly also match rampwise-planner; not a 3 because the niche and boundaries are explicitly stated.

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