Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
orchestra-research avatar

Evolving Ai Agents

  • 336 installs
  • 11.2k repo stars
  • Updated June 16, 2026
  • orchestra-research/ai-research-skills

evolving-ai-agents is an agent skill that documents the A-Evolve `Evolver` API for benchmark-driven agent evolution.

About

evolving-ai-agents is a reference skill for Orchestra’s A-Evolve stack: import `agent_evolve as ae`, construct an `Evolver` with an agent seed or custom workspace, attach a named or custom benchmark, and iterate evolution cycles until benchmarks improve. Solo builders shipping autonomous coding agents use it when ad-hoc prompt tweaks stop scaling and they need a structured loop—tasks, scoring, and evolvable layers—grounded in public harnesses like SWE-verified or MCP-Atlas. The doc spells resolution rules for string agent names, working-directory copies, and manifest validation so you do not start evolution on a broken workspace. You can override `workspace_dir`, inject a custom engine, and thread `EvolveConfig` without re-reading the whole Python package. Complexity is advanced because you are orchestrating benchmarks, seeds, and evolution state—not invoking a single API call. Treat this as Build-phase agent infrastructure; pair it with your own eval harness and version control before Ship.

  • `ae.Evolver` entry point with `run(cycles)` returning `EvolutionResult`
  • Built-in agent seeds: swe, terminal, mcp—or custom `BaseAgent` / workspace paths
  • Built-in benchmarks: swe-verified, mcp-atlas, terminal2, skill-bench, arc-agi-3 via `BenchmarkAdapter`
  • Seed workspaces copied to a working directory with manifest checks for `entrypoint` and `evolvable_layers`
  • Custom `EvolutionEngine` hook (default `AEvolveEngine`) and `EvolveConfig` tuning

Evolving Ai Agents by the numbers

  • 336 all-time installs (skills.sh)
  • +37 installs in the week ending Jul 26, 2026 (Skillselion tracking)
  • Ranked #2,131 of 16,659 AI & Agent Building skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/orchestra-research/ai-research-skills --skill evolving-ai-agents

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs336
repo stars11.2k
Security audit1 / 3 scanners passed
Last updatedJune 16, 2026
Repositoryorchestra-research/ai-research-skills

What it does

Run benchmark-driven evolution cycles on coding or terminal agents with the A-Evolve `agent_evolve` API and built-in seeds like swe, terminal, and mcp.

Who is it for?

Best when you're experimenting with self-improving agents and already run Python and want named benchmarks plus manifest-validated seed workspaces.

Skip if: Beginners who only need a one-shot Claude skill without local Python evolution infrastructure or benchmark maintenance.

When should I use this skill?

User is implementing or debugging A-Evolve / agent_evolve Evolver setup, seeds, benchmarks, or evolution cycles.

What you get

You can configure `ae.Evolver` with seeds, benchmarks, and cycles so evolved workspace state reflects measurable benchmark gains instead of guesswork.

  • Configured Evolver run
  • EvolutionResult after benchmark cycles
  • Validated agent workspace with entrypoint and evolvable_layers

By the numbers

  • 5 built-in benchmark names documented
  • 3 built-in agent seed names: swe, terminal, mcp

Files

SKILL.mdMarkdownGitHub ↗

Evolving AI Agents with A-Evolve

Overview

A-Evolve is universal infrastructure for evolving any AI agent across any domain using any evolution algorithm with zero manual engineering. It represents all evolvable agent state as files (prompts, skills, memory, tools), runs iterative solve-observe-evolve cycles against benchmarks, and uses LLM-driven mutation to improve agent performance automatically.

Benchmark results (Claude Opus 4.6):

  • MCP-Atlas: 79.4% (#1)
  • SWE-bench Verified: 76.8% (~#5)
  • Terminal-Bench 2.0: 76.5% (~#7)
  • SkillsBench: 34.9% (#2)

When to Use A-Evolve

Use A-Evolve when:

  • Optimizing agent prompts, skills, or memory against a measurable benchmark
  • Building self-improving agents with automated gating and rollback
  • Evolving domain-specific tool usage and procedures through LLM-driven mutation
  • Running iterative solve-observe-evolve loops to maximize agent performance
  • Needing reproducible, git-versioned evolution history for every change

Key differentiator: Other frameworks _build_ agents; A-Evolve _optimizes_ them. It sits on top of any agent framework and makes it better through automated evolution.

Do NOT use A-Evolve for:

  • Building multi-agent orchestration from scratch (use CrewAI, LangGraph)
  • One-shot agent tasks with no iteration needed (use LangChain, LlamaIndex)
  • RAG pipeline optimization (use LlamaIndex, Chroma)
  • Prompt-only optimization without skill/memory evolution (use DSPy)

Quick Start

Installation

pip install a-evolve                    # Core
pip install a-evolve[anthropic]         # With Claude support
pip install a-evolve[all]               # All providers

Three-Line Evolution

import agent_evolve as ae

evolver = ae.Evolver(agent="swe", benchmark="swe-verified")
results = evolver.run(cycles=10)
print(f"Final score: {results.final_score}")

This copies the built-in SWE seed workspace, runs 10 evolution cycles against SWE-bench Verified, and returns the optimized agent.

Core Concepts

The Agent Workspace

All evolvable state lives as files in a workspace directory:

my-agent/
├── manifest.yaml          # Metadata + entrypoint
├── prompts/
│   ├── system.md          # Main system prompt (evolved)
│   └── fragments/         # Modular prompt pieces
├── skills/
│   └── skill-name/
│       └── SKILL.md       # Reusable procedure with frontmatter
├── memory/
│   ├── episodic.jsonl     # Lessons from failures
│   └── semantic.jsonl     # General knowledge
├── tools/
│   ├── registry.yaml      # Tool manifest
│   └── tool_name.py       # Tool implementations
└── evolution/             # Managed by engine (metrics, history)

The Evolution Loop

Each cycle follows five phases:

1. Solve — Agent processes a batch of tasks from the benchmark 2. Observe — Benchmark evaluates trajectories, producing (task, trajectory, feedback) triples 3. Evolve — Evolution engine mutates workspace files based on observations 4. Gate — Validate mutations (git snapshot before/after for rollback) 5. Reload — Agent reinitializes from evolved filesystem state

Three Pluggable Interfaces

# 1. Agent — implements solve()
class MyAgent(ae.BaseAgent):
    def solve(self, task: ae.Task) -> ae.Trajectory:
        # Domain-specific solving logic
        return ae.Trajectory(task_id=task.id, output=result, steps=steps)

# 2. Benchmark — implements get_tasks() and evaluate()
class MyBenchmark(ae.BenchmarkAdapter):
    def get_tasks(self, split="train", limit=None) -> list[ae.Task]:
        return [ae.Task(id="1", input="...")]

    def evaluate(self, task: ae.Task, trajectory: ae.Trajectory) -> ae.Feedback:
        return ae.Feedback(success=True, score=0.95, detail="Passed")

# 3. Engine — implements step()
class MyEngine(ae.EvolutionEngine):
    def step(self, workspace, observations, history, trial):
        # Mutate workspace based on observations
        return ae.StepResult(mutated=True, summary="Updated prompts")

Workflow 1: Evolve an Existing Agent

Use when: You have a working agent and want to optimize it against a benchmark.

Critical Requirements:

  • [ ] Agent implements BaseAgent.solve() returning Trajectory
  • [ ] Benchmark implements BenchmarkAdapter with get_tasks() and evaluate()
  • [ ] Seed workspace has manifest.yaml with entrypoint and evolvable layers
  • [ ] System prompt exists at prompts/system.md
  • [ ] Workspace is a git repo (run git init && git add -A && git commit -m "init")

Steps

import agent_evolve as ae

# Configure evolution parameters
config = ae.EvolveConfig(
    batch_size=10,           # Tasks per solve round
    max_cycles=20,           # Maximum evolution iterations
    evolve_prompts=True,     # Mutate system prompt
    evolve_skills=True,      # Discover and refine skills
    evolve_memory=True,      # Build episodic memory
    evolver_model="us.anthropic.claude-opus-4-6-v1",
)

# Point to your agent workspace and benchmark
evolver = ae.Evolver(
    agent="./my-agent-workspace",
    benchmark="swe-verified",     # Or custom BenchmarkAdapter instance
    config=config,
)

# Run evolution
results = evolver.run(cycles=10)

# Inspect results
print(f"Cycles completed: {results.cycles_completed}")
print(f"Final score: {results.final_score}")
print(f"Converged: {results.converged}")
for cycle_num, score in enumerate(results.score_history):
    print(f"  Cycle {cycle_num + 1}: {score:.3f}")

Post-Evolution

The workspace is now optimized. Inspect what changed:

cd my-agent-workspace
git log --oneline              # See evo-1, evo-2, ... tags
git diff evo-1 evo-10          # Compare first and last evolution
cat prompts/system.md          # Read evolved prompt
ls skills/                     # See discovered skills

Workflow 2: Add a Custom Benchmark

Use when: You want to evolve agents on your own domain-specific tasks.

Critical Requirements:

  • [ ] Define task format (inputs, expected outputs)
  • [ ] Implement scoring logic (0.0–1.0 scale)
  • [ ] Prepare task dataset (train + holdout split)

Steps

import agent_evolve as ae

class CodeReviewBenchmark(ae.BenchmarkAdapter):
    """Evaluate agents on code review quality."""

    def get_tasks(self, split="train", limit=None):
        tasks = load_review_dataset(split)
        if limit:
            tasks = tasks[:limit]
        return [
            ae.Task(id=t["id"], input=t["diff"], metadata={"expected": t["comments"]})
            for t in tasks
        ]

    def evaluate(self, task, trajectory):
        expected = task.metadata["expected"]
        actual = trajectory.output
        precision, recall = compute_review_metrics(expected, actual)
        f1 = 2 * precision * recall / (precision + recall + 1e-9)
        return ae.Feedback(
            success=f1 > 0.7,
            score=f1,
            detail=f"P={precision:.2f} R={recall:.2f} F1={f1:.2f}",
        )

# Use with any agent
evolver = ae.Evolver(agent="./my-agent", benchmark=CodeReviewBenchmark())
results = evolver.run(cycles=5)

Workflow 3: Create a Custom Evolution Engine

Use when: The default LLM-driven mutation doesn't suit your domain.

Steps

import agent_evolve as ae

class RuleBasedEngine(ae.EvolutionEngine):
    def step(self, workspace, observations, history, trial):
        failures = [o for o in observations if not o.feedback.success]
        if not failures:
            return ae.StepResult(mutated=False, summary="No failures to address")

        # Analyze failure patterns
        error_types = categorize_errors(failures)
        prompt = workspace.read_prompt()

        # Append learned rules to prompt
        new_rules = generate_rules(error_types)
        workspace.write_prompt(prompt + "\n" + new_rules)

        return ae.StepResult(
            mutated=True,
            summary=f"Added {len(new_rules)} rules from {len(failures)} failures",
        )

evolver = ae.Evolver(
    agent="./my-agent",
    benchmark="my-benchmark",
    engine=RuleBasedEngine(),
)

Built-in Components

Seed Agents

AgentDomainModelKey Feature
sweSWE-benchClaude Opus 4.6Verify-fix loop, skill proposals
terminalTerminal-BenchClaude Sonnet 4Concurrent timeout, env discovery
mcpMCP-AtlasClaude Opus 4.6MCP server integration

Benchmarks

NameDomainMetric
swe-verifiedCode patchingPass rate
mcp-atlasTool callingAccuracy
terminal2Shell tasksPass rate
skill-benchMulti-step proceduresAccuracy
arc-agi-3Interactive gamesRHAE score

Evolution Algorithms

AlgorithmStrategyBest For
A-Evolve/SkillForgeLLM-driven workspace mutationGeneral-purpose
Guided SynthesisMemory-first, curated skillsSkill discovery
Adaptive EvolutionReward tracking, filtered observationsFine-grained control
Adaptive SkillSkill-centric refinementSkill-heavy domains

Configuration Reference

ae.EvolveConfig(
    batch_size=10,              # Tasks per solve round
    max_cycles=20,              # Max evolution iterations
    holdout_ratio=0.2,          # Test set split for gating
    evolve_prompts=True,        # Mutate system prompts
    evolve_skills=True,         # Discover/refine skills
    evolve_memory=True,         # Build episodic memory
    evolve_tools=False,         # Mutate tool implementations
    trajectory_only=False,      # Hide scores from evolver
    evolver_model="us.anthropic.claude-opus-4-6-v1",
    evolver_max_tokens=16384,
    egl_threshold=0.05,         # Convergence epsilon
    egl_window=3,               # Cycles for plateau detection
)

Convergence: Evolution stops early when score improvement is less than egl_threshold over the last egl_window cycles.

Skill Format

Skills are reusable procedures discovered and refined during evolution:

---
name: verify-edge-cases
description: "TRIGGER when: checking boundary conditions. DO NOT TRIGGER: for happy-path tests."
---

## Pattern
Test all falsy-but-valid values: 0, False, "", [], {}

## Process
1. List all input boundaries
2. Run each against the implementation
3. Check both output AND side effects

Skills accumulate in the workspace skills/ directory. The evolver curates them: ACCEPT new skills, MERGE overlapping ones, SKIP redundant proposals. Target: 5–10 broad skills, not 30 narrow ones.

Common Issues

Evolution score plateaus early

Cause: Batch size too small or evolver doesn't see enough failure diversity. Fix: Increase batch_size (try 15–20) and ensure benchmark tasks cover diverse failure modes. Set trajectory_only=False so the evolver sees scores.

Agent workspace grows too large

Cause: Skill library bloat from accepting every proposal. Fix: The default SkillForge engine curates skills automatically. If using a custom engine, implement merging logic to consolidate overlapping skills.

Git conflicts during evolution

Cause: Multiple evolution runs on the same workspace. Fix: Each evolver.run() should operate on its own workspace copy. Use Evolver(agent="seed-name") to auto-copy the seed each time.

LLM provider errors during evolution

Cause: Rate limits or authentication issues with the evolver model. Fix: Check evolver_model config. For Bedrock, ensure AWS credentials are configured. For Anthropic, set ANTHROPIC_API_KEY.

Custom agent not picking up evolved state

Cause: Agent doesn't implement reload_from_fs(). Fix: Override reload_from_fs() in your BaseAgent subclass to re-read prompts, skills, and memory from the workspace after each evolution cycle.

Usage Instructions for Agents

When this skill is loaded:

1. Read this entire file before implementing any evolution workflow 2. Start with the Quick Start — get a minimal evolution running before customizing 3. Use built-in seeds when possible"swe", "terminal", "mcp" have battle-tested configurations 4. Always initialize git in custom workspaces before running evolution 5. Check convergence settings — default egl_threshold=0.05 with egl_window=3 may be too aggressive for your domain 6. Inspect evolved state after each run — read prompts/system.md and skills/ to understand what the evolver learned

Pro Tips:

  • Set trajectory_only=False (default) so the evolver sees scores — this accelerates learning
  • Start with batch_size=10 and adjust based on task diversity
  • Use holdout_ratio=0.2 to prevent overfitting to training tasks
  • After evolution, git diff evo-1 evo-N shows the cumulative effect of all mutations
  • If the evolver isn't finding skills, enrich feedback.detail strings with specific failure reasons

Warning Signs:

  • Score oscillating between cycles → benchmark evaluation may be non-deterministic
  • Skills directory growing past 15+ skills → engine isn't merging/curating properly
  • Prompt growing past 10K chars → evolution is appending without refactoring
  • converged=True after 2-3 cycles → increase egl_window and decrease egl_threshold

References

  • Architecture deep dive: See references/architecture.md
  • API reference: See references/api.md
  • Step-by-step tutorials: See references/tutorials.md
  • Real-world examples: See references/examples.md
  • GitHub issues & solutions: See references/issues.md
  • Design patterns: See references/design-patterns.md
  • Release history: See references/releases.md

Related skills

How it compares

API reference for an evolution engine—not a single-turn codegen skill or an MCP data connector.

FAQ

Who is evolving-ai-agents for?

Developers building or tuning autonomous agents who need the `agent_evolve` Evolver API, built-in seeds, and benchmark adapters spelled out in one place.

When should I use evolving-ai-agents?

In Build when wiring evolution into your agent repo; in Ship when regression-testing evolved layers against swe-verified or mcp-atlas; in Operate when iterating cycles after production failures.

Is evolving-ai-agents safe to install?

Evolution runs local workspaces and benchmarks that may execute agent code; review the Security Audits panel on this page and sandbox runs before trusting evolved entrypoints.

AI & Agent Buildingagentsautomation

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.