Skip to content
Development
Skill

/cm-skill-evolution

Repair or extend CodyMaster skills with a three-mode loop: FIX, DERIVED, and CAPTURED, grounded in current repo tooling.

From plugin
cm
5362 skills8 agents11 commands3 hooks
+1
Install
$ npx -y skills add tody-agent/codymaster --skill cm-skill-evolution --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/cm-skill-evolution

Context preview

The summary Claude sees to decide when to auto-load this skill.

Repair or extend CodyMaster skills with a three-mode loop: FIX, DERIVED, and CAPTURED, grounded in current repo tooling.

SKILL.md

cm-skill-evolution.SKILL.md
name: cm-skill-evolution
description: "Repair or extend CodyMaster skills with a three-mode loop: FIX, DERIVED, and CAPTURED, grounded in current repo tooling."

cm-skill-evolution

Use this skill after `cm-skill-health` identifies a degraded or broken skill, or when `cm advisory handoff --for cm-skill-evolution` produces a structured recovery note.

Modes

FIX

Use when the skill should exist already but is inaccurate, broken, or partially missing.

Checklist:

  • repair broken references
  • restore missing support files
  • align docs and profiles
  • re-run skill validation and test gate

DERIVED

Use when the original promise was too ambitious, but the repo has enough primitives to ship a truthful MVP.

Checklist:

  • keep the same user problem
  • reduce claims to what the code can support today
  • reuse existing repo building blocks instead of inventing a new subsystem

CAPTURED

Use when the main value is operational learning rather than a new code path.

Checklist:

  • append the lesson with `cm retro --project . --tool skill --note "..."`
  • record durable context in `.cm/CONTINUITY.md`
  • update the relevant skill so future sessions do not repeat the same failure

Evolution Loop

1. Start from the health note.

  • Preferred source: `cm advisory handoff --for cm-skill-evolution`

2. Pick one mode only. 3. Define the smallest truthful recovery. 4. Patch the skill and its discovery surfaces. 5. Verify:

  • `npm run validate:skills`
  • `npm run check:skills`
  • repo test gate if code or docs wiring changed materially

6. Capture the lesson in retro and continuity.

Decision guide

  • The feature existed and drifted: `FIX`
  • The changelog promised more than the repo ever shipped: `DERIVED`
  • The issue is mainly process and should inform future work: `CAPTURED`

Output

## Skill Evolution
- Skill: cm-...
- Mode: FIX | DERIVED | CAPTURED
- Change: ...
- Verification: ...
- Learning captured: yes | no

Preferred advisory input:

## Advisory Handoff
- Consumer: cm-skill-evolution
- Skill: cm-...
- Recovery path: FIX | DERIVED | CAPTURED | NONE
- Confidence: 0.xx
- Source analysis: EA-...
- Task: ...
- Status: completed | partial | failed
- Evidence: ...
- Selected skills: ...
- Target skills: ...
- Quality weight: 0.xx
- Next step: ...
Read more
Ships withcm

"I can't write code. But in 6 months, I shipped 12 real products using AI. CodyMaster is everything I learned — so you don't have to repeat my mistakes." — Tody Le, Head of Product, Creator of CodyMaster 50+ skills. One install.

Get the whole plugin

Other skills on cm.