CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rampwise-aerobic-base

Aerobic base and endurance-efficiency specialist for the Rampwise coaching team. Use for "analyze my run/ride", aerobic fitness trend, heart rate vs pace/speed efficiency, efficiency factor, aerobic decoupling, cardiac drift, durability on long sessions, time in heart-rate zones, easy-vs-hard balance, and "is my base improving". Runs scripts on the user's real Garmin FIT data. Works with rampwise-heat-weather (conditions that distort HR), rampwise-recovery (fatigue), rampwise-fueling (long-session drift) and rampwise (verdict). Runs, rides and swims (lap-based pace, rest share and decoupling; wrist heart rate in water can be unreliable) and the legs of multisport activities. Also reads a .fit file from any watch brand (--fit-file) or Strava API data saved as JSON (--strava-json).

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

78%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 strong, dense operational body: copy-paste commands, precise metric semantics, honest reliability gating, confounder checks, and a handoff format make it highly actionable, and it wastes few tokens on things Claude already knows. Weaknesses are navigational and structural: two referenced files are missing from the bundle, caveats are duplicated, and the multi-tool workflow is never given an explicit order.

Suggestions

Fix the dangling references: either add references/papers/INDEX.md and docs/OTHER-WATCHES.md to the bundle or repoint those mentions at files that exist (e.g., fold the papers index into references/library.md, which already tracks read depth per paper).

Deduplicate repeated caveats — state 'coaching conventions, not published cut-offs' and 'compare only with the athlete's own similar sessions' once and cross-reference from the other section — and split the single-paragraph 'Other watch brands and Strava' section into short labeled rules.

Add a brief explicit step order for the workflow (e.g., 1. analyze_activity.py for the session in question, 2. aerobic_trend.py for context if 4+ reliable sessions, 3. hold_check.py when durability is the question, 4. apply confounder checks, 5. emit handoff block) so the tool-selection sequence is stated rather than inferred.

DimensionReasoningScore

Conciseness

Efficient and assumes Claude's competence — no basic-concept explanations, and operational content (thresholds, reliability flags, fallbacks) dominates — but it could be tightened: the caveat 'coaching conventions, not published cut-offs' appears in both the decoupling bullet and the All sports section, 'compare only with the athlete's own similar sessions' is likewise stated twice, and the 'Other watch brands and Strava' paragraph is a single dense wall. Not 5 because of this duplication and overlong compound sentences; not 3 because nothing explains what Claude already knows.

4 / 5

Actionability

Fully executable: copy-paste commands with flags for all three scripts ('python -X utf8 "<skills>/rampwise-aerobic-base/scripts/analyze_activity.py" ACTIVITY_ID --json', '--days 56 --sport all', '--sport bike --days 30 --ceiling 150'), exact metric definitions with thresholds and units, the exact Strava stream field names to save, a literal handoff block template, install instructions, and download-failure fallback. Covers the common cases completely.

5 / 5

Workflow Clarity

The flow (run script → check reliability flags → check confounders via sibling skills → emit handoff block) is discernible with real validation checkpoints ('A flagged number is **not a fitness signal**; say "no valid reading"', 'fewer than 4 comparable, reliable sessions there is **no trend**'), an error-recovery loop ('If a download fails, report it and fall back to the summary only'), and an output checklist. Falls short of 5 because the sequence is never made explicit — no ordered steps or decision guidance for which of the three scripts to run in what situation, leaving the reader to assemble the order from prose.

4 / 5

Progressive Disclosure

Good instinct — computation is delegated to scripts (all three referenced scripts exist) and evidence detail lives in references/evidence-map.md — but scored against the actual bundle, two referenced paths dangle: 'references/papers/ (INDEX.md lists the read depth)' and 'docs/OTHER-WATCHES.md' do not exist in the bundle, and the body never mentions the existing references/library.md while evidence-map.md chains into it (a second reference level). Missing referenced files break navigation, which is more than the 'minor organization gaps' of anchor 4; the clear signaling and appropriate splitting keep it above anchor 3's muddled-structure profile, so it sits at 3.

3 / 5

Total

16

/

20

Passed

Description

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

An exemplary description: concrete third-person capability statements, quoted natural trigger phrases including file extensions and alternate data sources, and explicit boundaries against sibling skills. Its only cost is length, but the density means no clause is wasted, so no anchor below 5 fits any dimension.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'aerobic fitness trend, heart rate vs pace/speed efficiency, efficiency factor, aerobic decoupling, cardiac drift, durability on long sessions, time in heart-rate zones, easy-vs-hard balance' plus 'Runs scripts on the user's real Garmin FIT data' and reading '.fit file from any watch brand (--fit-file) or Strava API data saved as JSON' — comprehensive coverage with no vague filler. The description is long but dense rather than padded; every clause names a capability or boundary.

5 / 5

Completeness

Explicitly answers both: what ('Aerobic base and endurance-efficiency specialist... Runs scripts on the user's real Garmin FIT data' with a full capability list) and when ('Use for "analyze my run/ride"... and "is my base improving"' with concrete trigger phrases). Matches the top anchor exactly.

5 / 5

Trigger Term Quality

Includes natural user phrasing in quotes ('analyze my run/ride', 'is my base improving') alongside synonyms and technical variants (aerobic decoupling, cardiac drift, efficiency factor, easy-vs-hard balance) and concrete file formats (.fit, Strava JSON). Coverage of terms a user would actually say is comprehensive.

5 / 5

Distinctiveness Conflict Risk

Clear niche (aerobic base/endurance efficiency within the Rampwise team) with explicit division of labor against siblings — 'Works with rampwise-heat-weather (conditions that distort HR), rampwise-recovery (fatigue), rampwise-fueling (long-session drift) and rampwise (verdict)'. Minimal conflict risk; triggers are domain-specific.

5 / 5

Total

20

/

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-aerobic-base/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.