evolve-skill

Transform user feedback into updated or new SKILL.md files with approval.

23|3|Updated May 17, 2024
One-click install
npx skills add https://github.com/johnend/dots --skill evolve-skill-johnend
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evolve-skill
Source: https://github.com/johnend/dots/tree/main/common/.ai/skills/evolve-skill
Command: npx skills add https://github.com/johnend/dots --skill evolve-skill-johnend

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review and distill user feedback or session patterns to identify when to update or create a Skill unit, ensuring changes are captured in the correct SKILL.md with proposal-first approval.

Core Features & Use Cases

  • Evolve existing skills when behavior should be updated to reflect new patterns.
  • Create new skills only when a distinct workflow or trigger requires separate handling.
  • Ensure changes include clear triggers, validation checks, and documented rationale for approvals.

Quick Start

Review recent feedback, identify whether to update an existing skill or create a new one, and draft the revised SKILL.md content for review.

Frequently Asked Questions about evolve-skill

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

FAQPage Schema
How do I update agent skills from user feedback?

To update agent skills from user feedback, the evolution process reviews session patterns and applies changes to SKILL.md files, drafting proposed updates for approval before applying edits.

When should I create a new skill versus updating an existing one?

Create a new skill only when a distinct workflow or trigger requires separate handling; otherwise, update existing skills in the SKILL.md files to reflect new behavior patterns.

Does the skill evolution process require approval before applying changes?

Yes, the skill evolution process requires approval before applying changes, presenting a proposed update with documented rationale, clear trigger language, and validation checks for review.

What should be included when evolving agent workflows into skills?

Evolving agent workflows into skills requires including clear trigger language, validation checks, and documented rationale within the SKILL.md files to ensure proper guardrails and approvals.

How do I add guardrails to recurring workflows in skill documentation?

To add guardrails to recurring workflows in skill documentation, the evolution process transforms session patterns into updated SKILL.md files with validation checks and clear trigger language before approval.

Can I automatically apply feedback updates to skill documentation?

No, you cannot automatically apply feedback updates; the process distills user feedback into a proposed change for the SKILL.md files and requires explicit approval before applying any edits.