Section 11: Endurance Training Coach (Intervals.icu)
PassAudited by ClawScan on May 1, 2026.
Overview
This instruction-only coaching skill is coherent and disclosed, but it handles private training data and can optionally use external GitHub files and scheduled checks.
Before installing, review the referenced Section 11 GitHub materials, keep your training-data repository or folder private, limit connector permissions, avoid public URLs for personal data, and only enable the heartbeat/scheduled checks if you intentionally want background coaching.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent may be able to read private training files through a connected GitHub account.
The skill can use delegated access to a private GitHub data repository. This is expected for the training-data workflow, but users should ensure the connector is limited to the intended repo and permissions.
GitHub connector: If the platform has a GitHub connector ... the athlete connects their private data repo directly. The AI reads files through the connector
Use a dedicated private training-data repository and grant the narrowest connector permissions available, preferably read-only.
Coaching instructions may change if the external GitHub protocol changes.
The core protocol can be loaded from a mutable GitHub 'main' branch. This is disclosed and purpose-aligned, but changes to that external file could change coaching behavior.
If not found, fetch from: https://raw.githubusercontent.com/CrankAddict/section-11/main/SECTION_11.md
Review the referenced repository and prefer a local or commit-pinned copy of the protocol if you need stable behavior.
Private training, route, and schedule information may be read and reused as context for coaching answers.
The skill relies on persistent and retrieved athlete files as authoritative context. This is central to the coaching purpose, but those files may contain sensitive health, location, goals, and schedule data and can influence future advice.
Data files (`latest.json`, `history.json`, `intervals.json`, `ftp_history.json`, `routes.json`, `DOSSIER.md`, `section11/`) live in the athlete's data directory ... Ask the athlete to fill in their data (zones, goals, schedule, etc.)
Keep the data directory or repository private, avoid public raw URLs for personal data, and periodically review dossier and JSON contents for accuracy.
If enabled, the agent may periodically read training data and create summaries or plans without a fresh prompt each time.
The template supports scheduled background analysis. It is clearly disclosed and opt-in, but enabling it means the agent may act on a schedule rather than only in direct chat.
The heartbeat is fully opt-in and disabled by default. It must be explicitly configured by the user. When active, it only performs scheduled analysis (read training data → run protocol checks → write summaries/plans to your chosen location).
Enable heartbeat only if you want scheduled coaching, set notification hours carefully, and disable it when no longer needed.