Skill Evolution Engine

Skill Evolution Engine

When to Use

• User says evolve skills or task matches this capability
• User says version skills or task matches this capability
• User says skill maintenance or task matches this capability

Workflow

1. Snapshot the current SKILL.md to a local versioned backup and run the hyper-skill-tester baseline.
2. Prepare the proposed evolution as a reviewable diff with expected benefits, risks, and rollback path.
3. Obtain explicit user approval before applying, committing, publishing, or otherwise persisting the proposed change.
4. After approval, apply the change and compare scores. Present any regression and its rollback option for approval rather than rolling back automatically.

Integrations

• skill-evolver
• evolution
• evolver
• hyper-skill-tester

Error Handling

Gotchas

• Keep version backups locally; do not publish, delete, or restore them without explicit user approval.

Example

Input: User request matching triggers above. Output: Structured result per workflow with integrations invoked as needed.