meta-skill-evolution

Decides whether to update, propose, or discard skill knowledge after each task.

2|1|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/frederico-kluser/newsletter-crawler --skill meta-skill-evolution-frederico-kluser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meta-skill-evolution
Source: https://github.com/frederico-kluser/newsletter-crawler/tree/main/.agents/skills/meta-skill-evolution
Command: npx skills add https://github.com/frederico-kluser/newsletter-crawler --skill meta-skill-evolution-frederico-kluser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents accumulate knowledge during tasks, but persisting every observation bloats or corrupts skill files. This Skill provides a disciplined end-of-task pipeline that decides whether new knowledge is important enough to persist, verifies it against external evidence, and safely integrates it into SKILL.md without regressions. ## Core Features & Use Cases - Five-step memory pipeline: importance gating, external verification, conflict detection, gated lean updates, and a separate git commit for auditability. - Verification-first persistence: knowledge is only written when confirmed by a green test/build/lint/eval, entailment against a cited file, or explicit user confirmation. - Promote-or-discard gating: changes are staged in SKILL.md.next and promoted only if validate-skill.mjs passes with no correct-to-wrong regressions. - Use Case: After fixing a subtle bug in a crawler, run this pipeline to check whether the lesson is non-obvious and verified, then replace the outdated passage in the relevant SKILL.md and commit it separately. ## Quick Start At the end of your task, ask the agent to run the meta-skill-evolution pipeline for each skill involved and persist only verified important learnings.

Frequently Asked Questions about meta-skill-evolution

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

FAQPage Schema
How do I persist new knowledge into an AI agent skill safely?

Run the five-step pipeline: gate on importance, verify with an external signal like a passing test or eval, detect conflicts with existing content, stage the change in SKILL.md.next, and promote only if validate-skill.mjs passes without regressions.

When should I update an existing skill versus propose a new one?

Update an existing skill when the knowledge fits its current scope. Propose a new skill as a human-reviewed draft with name, description, and evals when the knowledge falls outside every existing skill's scope, and never auto-publish it.

What counts as external verification before writing to SKILL.md?

Accepted signals are a green test, build, lint, type-check, or eval that produced the knowledge, entailment against the cited source file, or explicit user confirmation. Without one of these signals, the candidate learning is discarded.

How does the pipeline prevent memory poisoning in skills?

The conflict detection step blocks content that reads like an injected instruction or originates from an untrusted source. Contradicting content replaces the old passage rather than appending a competing rule, and high-impact changes remain a human-reviewed diff.

What happens if a skill update causes an eval regression?

The update is discarded under the promote-or-discard rule. Changes are staged in SKILL.md.next and only integrated into SKILL.md when validate-skill.mjs shows no correct-to-wrong flips, keeping the skill lean and stable.