a-evolve
Apply A-Evolve's agentic evolution methodology to improve AI agent performance across runs. Use when the user wants to diagnose agent failures, generate targeted skills from error patterns, evolve system prompts, or accumulate episodic knowledge. Works standalone or inside AutoResearchClaw pipelines
Оригинален текст · няма потвърден превод на българскиПърво прочетете инструкцията.
Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.
GitHub хранилище- Звезди на репото
- 14 488
- Лиценз
- MIT
- Последна проверка на записа
- 20.09.2026 г.
Добавете в своя инструмент.
Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.
npx skills add aiming-lab/AutoResearchClawСтраницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.
Откъс от SKILL.md
Началото на файла на автора, без превод.
A-Evolve: Agentic Evolution Skill
Apply the Solve → Observe → Evolve → Gate → Reload methodology from A-Evolve to iteratively improve agent performance. This skill is prompt-based — no external dependencies, no harness changes. You analyze failures, propose workspace mutations, and generate durable artifacts (skills, prompt patches, knowledge entries) that the agent can load in future runs.
Core Loop
When asked to evolve or improve agent performance, follow this 5-step loop:
1. Solve (Collect Evidence)
Gather the agent's execution artifacts. Ask the user for or locate:
- Run logs, error traces, or experiment outputs
- Pass/fail results per task
- Metric values (accuracy, reward, success rate)
- Any existing session files from previous runs
If inside AutoResearchClaw, look at:
artifacts/rc-*/— experiment outputs, charts, reviewsevolve.logor stage-specific logsreviews.md— peer review feedback- Sentinel watchdog reports
2. Observe (Diagnose)
Analyze the collected evidence to produce structured observations:
For each failed or underperforming task, identify:
- Error category: code bug, timeout, wrong approach, missing knowledge, API misuse, hallucinated reference, prompt ambiguity, etc.
- Root cause: What specifically went wrong and why
- Frequency: Is this a one-off or a recurring pattern across tasks?
- Severity: blocking (pipeline crash) / degrading (wrong result) / cosmetic (formatting issue)
Write observations as a structured list:
## Observations (Batch N)
### OBS-1: [Category] Short description
- Tasks affected: task_001, task_005, task_012
- Root cause: ...
- Frequency: 3/50 tasks (6%)
- Severity: degrading
### OBS-2: ...
3. Evolve (Propose Mutations)
Based on observations, propose one or more of these mutation types:
A. Generate a Skill (for recurring patterns, frequency ≥ 3)
Write a new SKILL.md file that teaches the agent how to handle this
pattern. A good evolved skill:
- Targets a specific failure category, not generic advice
- Contains concrete steps the agent should follow
- Includes a "when to apply" trigger condition
- Is short (under 100 lines) and self-contained
Example — if the agent keeps failing at API pagination: