skill-evolution

Capture reusable learnings and codify them into validated skill updates via pull requests.

3|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/OktayCopurlu/ai-shared --skill skill-evolution-oktaycopurlu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-evolution
Source: https://github.com/OktayCopurlu/ai-shared/tree/main/.github/workflows/skills/skill-evolution
Command: npx skills add https://github.com/OktayCopurlu/ai-shared --skill skill-evolution-oktaycopurlu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Hard-won insights from complex tasks are usually lost when a session ends, and ad-hoc edits to shared skill files risk drift, broken symlinks, and inconsistent behavior across AI tools. This Skill provides a disciplined funnel for turning repeated patterns into reviewed, validated skill changes. ## Core Features & Use Cases - Capture-Validate-Codify funnel: Stage learnings as memory notes first, then promote only patterns that recur, were requested, or fix a real failure. - Two codification paths: Update an existing skill (Path A) or create a new one (Path B), each with branching, diff review, eval gates, and repo validation steps. - Tool drift detection: Identify when MCP tool-adapter skills document stale tool names or examples and route the fix through a PR. - Use Case: After noticing a GitHub MCP tool was renamed mid-task, finish the work, then open a [skill-evolution] PR updating the affected skill with the new tool name and passing validate.sh and agnix checks. ## Quick Start Ask the agent to save what was learned in this session as a reusable skill update in the ai-shared repo.

Frequently Asked Questions about skill-evolution

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

FAQPage Schema
How do I turn a session learning into a reusable AI skill?▼

First capture the insight as a memory note, then validate that the pattern recurred or filled a real gap. Codify it by branching the skills repo, updating or creating the SKILL.md, running validation, and opening a pull request for review.

How to update a skill when an MCP tool name changes?▼

Finish the current task first, then capture the drift as a skill-evolution candidate. Open a branch like skill-evolution/<name>-tool-drift, update the documented tool names and examples, run validate.sh and agnix, and submit a PR describing the mismatch.

When should a learning not become a skill?▼

Skip codification when the solution is trivial, project-specific, or a one-off fix. Project-specific guidance belongs in the project's own copilot-instructions.md, and most learnings should remain as memory notes rather than new skills.

Why does a renamed skill stop loading in other repos?▼

The folder name must exactly match the name field in SKILL.md frontmatter, and other repos reference skills by name. After renaming, run setup.sh to refresh symlinks and grep the repo for the old name to update all cross-references.

What validation is required before merging a skill change?▼

Run three checks from the repo root in order: zsh validate.sh for repo-local rules, npx agnix for the Agent Skills spec, and setup.sh if folders were added or renamed. Changes to activation text also require updated eval TSV rows.