allanyiin-skill-evolution

Convert agent failure traces into skill patches, evals, and lifecycle decisions.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/JustinChangTW/ai-skills-core --skill allanyiin-skill-evolution-justinchangtw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: allanyiin-skill-evolution
Source: https://github.com/JustinChangTW/ai-skills-core/tree/main/skills/01-skill-management/allanyiin-skill-evolution
Command: npx skills add https://github.com/JustinChangTW/ai-skills-core --skill allanyiin-skill-evolution-justinchangtw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? When an AI agent skill fails, gets corrected by users, regresses, or drifts out of alignment with neighboring skills, teams often lack a structured way to turn that failure evidence into concrete skill updates, regression tests, or retirement decisions. This Skill closes that failure-to-evolution loop with a repeatable, evidence-driven process. ## Core Features & Use Cases - Failure normalization and root-cause classification: Converts tool traces, user corrections, and regression reports into structured failure records classified by a nine-category taxonomy (trigger, workflow, tool contract, environment drift, safety, output contract, library drift, eval gap, stale knowledge). - Minimal compatible patch decisions: Produces an evolution decision record choosing among NO-CHANGE, PATCH, EVAL-ONLY, ROLLBACK, MERGE-SPLIT, RETIRE, or BLOCKED, with patch surface, compatibility risk, and rollback path. - Eval and regression gate generation: Drafts trigger evals (direct, indirect, negative) and functional evals (happy path, edge case, failure mode) plus regression gate thresholds. - Use Case: A PPTX skill ships slides that break after SVG-to-PowerPoint conversion. Feed the failure trace to this Skill and receive a PATCH decision adding a render QA gate, a reference rule, and a failure-mode eval fixture. ## Quick Start Ask the agent to analyze this failed agent run and turn it into a skill evolution decision with a regression eval draft.

Frequently Asked Questions about allanyiin-skill-evolution

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

FAQPage Schema
How do I turn a failed agent run into a skill update?▼

Provide the failure trace, expected behavior, actual behavior, and the affected skill path. The Skill normalizes the failure record, classifies the root cause, and outputs a decision record with a minimal patch surface, eval additions, and verification steps.

How do I convert a regression into an eval test?▼

Supply the failing case, the correctness criteria, and any should-trigger or should-not-trigger conditions. The Skill drafts trigger evals (direct, indirect, negative) or functional evals (happy path, edge case, failure mode) with coverage tags ready for evals.json.

When should I use skill evolution versus creating a new skill?▼

Use skill evolution only when failure evidence exists, such as traces, corrections, or regressions. Creating a brand-new skill without failure evidence belongs to a skill creator workflow, and benchmark-driven optimization with held-out splits belongs to a skill optimizer.

Can it decide to merge, split, or retire skills?▼

Yes. When routing logs show repeated query stealing or overlapping primary jobs, it produces MERGE-SPLIT or RETIRE decisions with migration notes, rollback conditions, and eval redistribution plans. These lifecycle actions require explicit user approval before execution.

What happens if the failure record contains secrets or credentials?▼

The Skill returns BLOCKED and stops processing until the input is redacted. It never analyzes or repeats raw secrets, and it will not apply patches based on unsafe input containing unmasked credentials or personal data.