How do I install the Fitness skill?

Run npx skillmds@latest add boshu2/fitness in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Fitness safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Fitness?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Fitness free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Fitness?

boshu2 (@boshu2) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Fitness by boshu2 — Agent Skill

Name: Fitness
Rating: 4.2 (5 reviews)
Author: boshu2

File contents

Fitness — read-only goal measurement

Inspect the active goals document and run only the caller-selected measurement, validation, drift, history, export, or meta-goal command.

Renamed from goals (2026-07-29): the semantic skill is fitness; the ao goals CLI command family is a separate product surface and keeps its name. The goals compatibility alias skill was deleted 2026-09-03.

Measurement stays trustworthy only because it cannot mutate what it measures; the moment a fitness report edits a goal, the next report measures the editor, not the project.

Named failure mode — advice creep: a measurement report that ends with "you should…" has silently become work selection.

Anti-pattern: padding the report with recommendations to look helpful. Corrective: return the numbers, the evidence gaps, and checked/not-checked scope, and let the caller decide.

Boundary

Prefer GOALS.md when both Markdown and legacy YAML exist.
Preserve stable directive and gate identities in the report.
Every measured gate must name its executable check and observed outcome.
Do not add, remove, prioritize, recommend, apply, prune, migrate, or otherwise mutate goals.
Do not translate a fitness gap into work selection or a next action.
No subcommand edits the goals source through its own logic. measure, drift, and export persist a best-effort JSON snapshot under the fixed derived path .agents/ao/goals/baselines/. render --out <file> writes a Gherkin spec to whatever path the caller names — the CLI does not constrain it, so never point --out at the goals source or any non-derived file.

Commands

All eight subcommands read the goals source without mutating it. The snapshot write (fixed derived path) and the render --out write (caller-chosen path, caller's responsibility) are the only side effects.

ao goals measure --json
ao goals validate --json
ao goals drift
ao goals history
ao goals export
ao goals meta --json
ao goals scenarios
ao goals render          # append --out <file> to write the spec instead of stdout

Run the requested command once. Return the command, exit code, goal-level results, aggregate measurement, missing evidence, and checked/not-checked scope. Then stop.

---name: fitnessdescription: Measure declared project fitness goals without recommending or applying work. Triggers: "fitness", "check project fitness", "measure goals".---# Fitness — read-only goal measurement Inspect the active goals document and run only the caller-selected measurement, validation, drift, history, export, or meta-goal command. Renamed from `goals` (2026-07-29): the semantic skill is `fitness`; the `ao goals` CLI command family is a separate product surface and keeps its name. The `goals` compatibility alias skill was deleted 2026-09-03. Measurement stays trustworthy only because it cannot mutate what it measures; the moment a fitness report edits a goal, the next report measures the editor, not the project. Named failure mode — **advice creep**: a measurement report that ends with "you should…" has silently become work selection. Anti-pattern: padding the report with recommendations to look helpful. Corrective: return the numbers, the evidence gaps, and checked/not-checked scope, and let the caller decide. ## Boundary - Prefer `GOALS.md` when both Markdown and legacy YAML exist. - Preserve stable directive and gate identities in the report. - Every measured gate must name its executable check and observed outcome. - Do not add, remove, prioritize, recommend, apply, prune, migrate, or otherwise mutate goals. - Do not translate a fitness gap into work selection or a next action. - No subcommand edits the goals source through its own logic. `measure`, `drift`, and `export` persist a best-effort JSON snapshot under the fixed derived path `.agents/ao/goals/baselines/`. `render --out <file>` writes a Gherkin spec to whatever path the caller names — the CLI does not constrain it, so never point `--out` at the goals source or any non-derived file. ## Commands All eight subcommands read the goals source without mutating it. The snapshot write (fixed derived path) and the `render --out` write (caller-chosen path, caller's responsibility) are the only side effects. ```bash ao goals measure --json ao goals validate --json ao goals drift ao goals history ao goals export ao goals meta --json ao goals scenarios ao goals render # append --out <file> to write the spec instead of stdout ``` Run the requested command once. Return the command, exit code, goal-level results, aggregate measurement, missing evidence, and checked/not-checked scope. Then stop.

Frequently asked questions

Fitness