Agent Prompt Evolution

Track agent set and meta-agent evolution to assess specialization and reusability.

21|2|Updated Oct 8, 2025
One-click install
npx skills add https://github.com/yaleh/meta-cc --skill agent-prompt-evolution
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Agent Prompt Evolution
Source: https://github.com/yaleh/meta-cc/tree/main/.claude/skills/agent-prompt-evolution
Command: npx skills add https://github.com/yaleh/meta-cc --skill agent-prompt-evolution

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill tracks how Claude Code agents specialize during methodology development, enabling data-driven decisions about specialization and reuse.

Core Features & Use Cases

  • Agent set evolution: Track additions/removals across iterations.
  • Meta-agent evolution: Monitor capability changes to the coordinating agent.
  • Specialization decisions: When and why to introduce specialized agents.
  • Reusability assessment: Distinguish universal vs domain-specific components.

Quick Start

Record a new specialization decision and evaluate its ROI across the next iterations.

Frequently Asked Questions about Agent Prompt Evolution

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

FAQPage Schema
How do I track agent specialization across experiments?

Track agent specialization by recording when generic agents show performance gaps (>5x), documenting additions and removals in your agent set across iterations, and monitoring capability changes to your coordinating meta-agent. This identifies which specialized agents deliver ROI versus which remain universal components.

When should I introduce specialized agents in methodology development?

Introduce specialized agents when comparing multi-experiment results reveals performance disparities that generic agents cannot resolve, or when analyzing methodology transferability shows domain-specific logic emerging. Use this Skill to decide which specializations justify the 2–3 hour overhead per experiment.

How do I distinguish universal from domain-specific agent components?

Reusability assessment compares agent behavior and performance across experiments to isolate universal logic (applicable across domains) from domain-specific reasoning. This evaluation informs which components to maintain as core versus which to retire or specialize.

Can I reuse agent designs across different methodologies?

Reusability depends on tracking meta-agent evolution and specialization decisions alongside agent set changes. This Skill provides ROI-focused reporting to show whether agents designed for one methodology transfer to others or require domain-specific adaptation.

What overhead should I expect when tracking agent evolution?

Expect 2–3 hours per experiment to record specialization decisions, track agent set and meta-agent changes, and generate templates and quick-start guidance. This overhead is amortized across iterations when comparing multiple experiments.

How do I measure the impact of adding a specialized agent?

Document the specialization decision, measure performance before and after across subsequent iterations, and use ROI-focused reporting to compare results. This shows whether the specialized agent's performance gain justifies maintaining it versus reverting to generic design.