CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rampwise-recovery

Recovery and readiness specialist for the Rampwise coaching team. Use for "should I train hard today", HRV, resting heart rate, sleep, sleep debt, fatigue, overreaching, "am I recovered", or a morning readiness check. Runs a script that pulls HRV, sleep and resting HR from the user's own Garmin and returns GREEN / AMBER / RED against the user's personal baseline. Works with rampwise-load-injury (training stress), rampwise-strength (what the evening session should be) and rampwise (final verdict).

Quality

94%

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

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

An exemplar instructional skill body: executable commands with real backing scripts, precise decision thresholds, a concrete handoff contract, explicit edge-case and safety rules, and disciplined evidence-strength labeling — all in about 50 lines with no filler. The only defect is a broken bundle reference: `references/papers/` (and its `INDEX.md`) is cited in the Papers section but absent from the shipped bundle.

Suggestions

Fix the Papers section's broken reference: either ship `references/papers/` with the promised `INDEX.md` (listing read depth per paper, as library.md's status column already does) or point the section at the existing `references/library.md`.

Add a one-line link from the body to `references/library.md` (e.g. in the Papers section) so the citation index is discoverable from the top level instead of only via evidence-map.md.

DimensionReasoningScore

Conciseness

The ~50-line body is dense with content Claude cannot be assumed to know — exact flag thresholds, the baseline band definition, the verdict rule, the handoff block, and evidence-strength limits — with zero padding and no explanation of basic concepts (it never explains what HRV or sleep debt are). Re-checked against anchor 4: the only candidate for trimming is the triple-restated `<skills>` path note, but that ambiguity across harnesses justifies it.

5 / 5

Actionability

Four copy-paste command variants (`--brief`, `--json`, `--stress 4`) plus `--date/--days/--trend` options, all pointing at a script that exists in `scripts/readiness_check.py`; the handoff block is a concrete fill-in template with enumerated flag codes and confidence conditions. This matches the fully-executable anchor covering the common cases; no pseudocode or vague direction remains.

5 / 5

Workflow Clarity

Single-task skill (run the readiness check, emit the handoff) with an unambiguous action, and the edge cases that matter are explicitly handled: "Missing data for today (watch not synced) = say so; use the latest day and label it", confidence-downgrade conditions, the AMBER-one-flag escalation prompt, and the stop-and-refer medical rule. The operation is read-only, so the destructive/batch validation cap does not apply.

5 / 5

Progressive Disclosure

Good structure overall: the body is a lean overview, evidence detail is correctly pushed to `references/evidence-map.md` (which exists and is clearly signaled), and the bulk paper data stays out of SKILL.md. Not 5 because the "Papers" section points to `references/papers/` with an `INDEX.md` that does not exist in the bundle, and `references/library.md` is only discoverable via evidence-map.md rather than from the body — minor organization/navigation gaps per the anchor-4 description.

4 / 5

Total

19

/

20

Passed

Description

91%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 its specialist role, its concrete mechanism (Garmin data → GREEN/AMBER/RED against personal baseline), an explicit 'Use for' clause with natural quoted trigger phrases, and its position in the multi-skill team. The only weakness is mild trigger overlap (fatigue, overreaching) with the sibling training-stress skill.

DimensionReasoningScore

Specificity

"Runs a script that pulls HRV, sleep and resting HR from the user's own Garmin and returns GREEN / AMBER / RED against the user's personal baseline" names several concrete actions (pull three biometrics, compare against personal baseline, return a tri-state verdict) plus its team role and handoff targets. Not 5 because the action list is narrow for its niche (one script, one verdict) rather than comprehensively covering capabilities; not 3 because it goes well beyond 1-2 generic actions.

4 / 5

Completeness

Both halves are explicit: what ("Recovery and readiness specialist... Runs a script that pulls HRV, sleep and resting HR from the user's own Garmin and returns GREEN / AMBER / RED") and when ("Use for..." followed by concrete trigger phrases). This matches the anchor-5 example structure exactly; anchor 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

The "Use for" list combines quoted natural user phrases ("should I train hard today", "am I recovered", "a morning readiness check") with domain synonyms (HRV, resting heart rate, sleep, sleep debt, fatigue, overreaching), matching the comprehensive-synonyms anchor. Re-checked against anchor 4: only trivial variants like the spelled-out "heart rate variability" are absent, and HRV is the standard term users say.

5 / 5

Distinctiveness Conflict Risk

The niche is clearly partitioned against siblings ("Works with rampwise-load-injury (training stress), rampwise-strength (what the evening session should be) and rampwise (final verdict)"), and Garmin-baseline triggers are largely distinct. Not 5 because "fatigue" and "overreaching" are shared concepts with the rampwise-load-injury (training stress) skill, leaving minor overlap risk with a closely related skill — the anchor-4 condition.

4 / 5

Total

18

/

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