skill-evolve

Apply governance-approved mutations to skills with audit logging.

1.9k|124|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/yologdev/yoyo-evolve --skill skill-evolve-yologdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-evolve
Source: https://github.com/yologdev/yoyo-evolve/tree/main/skills/skill-evolve
Command: npx skills add https://github.com/yologdev/yoyo-evolve --skill skill-evolve-yologdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables safe, auditable evolution of your skill library by allowing you to refine, deprecate, or retire other skills based on recurring patterns observed across past sessions.

Core Features & Use Cases

  • Guarded mutation: enforces origin-based allow-list and core-safety checks before any change.
  • Audit-first workflow: logs every decision to skills/_journal.md and ties it to explicit outcomes.
  • Lifecycle management: supports refine, create, retire, or NO-OP actions to manage the skill catalog over time.

Quick Start

Run the skill_evolve cycle via scripts/skill_evolve.sh to begin an evolution pass.

Frequently Asked Questions about skill-evolve

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate skill lifecycle management and safely retire deprecated skills?

Automating skill lifecycle management involves applying governance-approved mutations—refine, create, retire, or NO-OP—based on recurring session patterns. Strict gating ensures mutations are justified, reversible, and recorded in an audit log.

What is a guarded mutation workflow for evolving skills with version control?

Guarded mutation workflows enforce origin-based allow-lists and core-safety checks before modifying skills. This prevents changes to core-enabled skills and requires eligible targets to declare a specific frontmatter origin for safe, auditable evolution.

How do I log skill mutations to an audit journal with expected outcomes?

Skill mutations are logged by recording every decision in a markdown audit journal file. Each entry ties the mutation to an explicit expected outcome, ensuring the evolution pass remains fully auditable and reversible.

Can I use YAML frontmatter to control which skills are eligible for automated refinement?

YAML frontmatter controls skill refinement eligibility by requiring an explicit origin tag. Skills lacking this designated origin are skipped, and core-enabled skills are actively avoided to prevent unsafe automated mutations.

When should I avoid using automated skill evolution passes on my workflow?

Avoid automated skill evolution passes when targeting skills lacking the required frontmatter origin or those that are core-enabled. Strict gating blocks these mutations to prevent unsafe or unjustified modifications to your workflow.