Endurance Coach
ReviewAudited by ClawScan on May 1, 2026.
Overview
The skill is coherent for endurance coaching, but users should notice that it can use Strava data, run an external npm CLI, and keep persistent local athlete context.
This skill appears purpose-aligned and not malicious from the provided artifacts. Before using Strava sync, review the external endurance-coach npm CLI and the permissions it requests. Expect local files under ~/.endurance-coach to store training history and coaching context, and periodically review or delete them if you do not want that information retained.
Findings (3)
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.
A future or compromised version of the external CLI could behave differently from what the skill documentation describes.
The skill relies on an external npm package executed with npx and @latest, so the reviewed artifacts do not pin or include the CLI code that performs data analysis and sync operations.
npx -y endurance-coach@latest stats --weeks 8 --longest-weeks 12
Use the CLI only when expected, consider pinning a known version instead of @latest, and review the npm package before authorizing account access.
Authorizing Strava may expose activity history and athlete profile data to the local coaching workflow.
The skill can initiate Strava authorization and synchronize training history, which is expected for the stated coaching purpose but involves delegated access to a user fitness account.
For Strava auth and sync, use the CLI commands `auth` then `sync`.
Authorize only the intended Strava account, review the permissions requested by the CLI, and revoke access if you stop using the skill.
Sensitive personal fitness and life-context information may persist locally and affect later training plans.
The skill stores and reuses persistent athlete context, including life constraints, goals, training patterns, and coaching guidance, so stale or edited context can influence future recommendations.
`~/.endurance-coach/Athlete_Context.md` ... `Use this context to inform all coaching decisions.`
Periodically review the Athlete_Context.md file, remove details you do not want retained, and verify important assumptions before following a plan.