Skill

cm-skill-evolution

From cm

Repairs or extends CodyMaster skills via three-mode loop (FIX, DERIVED, CAPTURED) after cm-skill-health identifies issues, grounded in repo tooling.

developer-tools

code-quality

npx claudepluginhub tody-agent/codymaster --plugin cm

Tool Access

This skill uses the workspace's default tool permissions.

Preview

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.

SKILL.md

Similar Skills

evolve-skill

Evolves existing skills by refining content in-place or creating advanced variants. Assesses gaps, applies changes, updates version metadata, syncs registry/cross-references. Use for outdated steps, feedback gaps, complexity upgrades.

1 tool

agent-almanac

skill-forge-evolve

Improves existing Claude Code skills by fixing under/over-triggering, refining instructions, adding sub-skills, and evolving architecture based on feedback.

skill-forge

improving-skills

Optimizes a single existing Claude Code skill through task-based workflow: analyze structure, gather context, research best practices, identify/apply improvements, validate/review. For 'improve skill' or similar.

rcc

Stats

Stars40

Forks25

Last CommitApr 18, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

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

Start from the health note.
- Preferred source: cm advisory handoff --for cm-skill-evolution
Pick one mode only.
Define the smallest truthful recovery.
Patch the skill and its discovery surfaces.
Verify:
- npm run validate:skills
- npm run check:skills
- repo test gate if code or docs wiring changed materially
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: ...