agent-evolver_skill

This skill enables autonomous agent self-improvement by analyzing errors, extracting insights, and optimizing strategies to boost performance.
  • Python

2.5k

GitHub Stars

5

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill agent-evolver

  • _meta.json281 B
  • deploy.sh4.7 KB
  • evolver.sh1.5 KB
  • requirements.txt220 B
  • SKILL.md6.4 KB

Overview

This skill is an AI agent self-evolution engine that enables agents to learn from experience, detect problems, extract insights, and optimize strategies autonomously. It captures execution results, analyzes failures with an LLM-backed pipeline, and persists actionable lessons for semantic search and automated strategy updates. Use it to raise success rates, reduce repeated errors, and implement continuous learning for long-running agents.

How this skill works

The engine ingests task results or error traces, runs automated analysis to extract root causes and solutions, and stores structured experience capsules in a local database. Experiences are vectorized for semantic search and aggregated into evolution statistics. Periodic or event-driven evolution cycles update agent strategies, manage strategy versions, and can automatically apply or roll back changes based on historic success metrics.

When to use it

  • After a task or job fails and you need root-cause analysis and suggested fixes
  • When you want to improve an agent's overall success rate or optimize execution strategies
  • To accumulate institutional knowledge from repeated runs and enable semantic search of past incidents
  • When you need automated, periodic tuning of agent behavior with versioning and rollback
  • To detect recurring error patterns and prioritize remediation across tasks

Best practices

  • Feed complete error traces and task context to improve analysis quality
  • Enable embeddings and provide an API key for the LLM to get richer suggestions
  • Tag task types consistently (e.g., code_generation, data_analysis) for targeted stats
  • Run evolution cycles in staging before applying strategy changes in production
  • Monitor metrics after automated changes and configure rollback thresholds

Example use cases

  • Analyze a recurring ValueError in code generation runs and apply a recommended fix
  • Search historical experiences to find prior solutions for a negative-number calculation bug
  • Periodically compute evolution stats to identify the most common error classes to address
  • Automatically evolve an agent after a failed task to update prompts or prechecks
  • Persist lessons from data-processing pipelines to prevent repeated failures

FAQ

No. It can use fallback local analysis, but enabling an OpenAI API key and a vector store (ChromaDB) yields richer extraction and semantic search.

Where are experiences stored?

Experiences are persisted locally (default ~/.evolver/evolution.db) and vector files (default ~/.evolver/chroma) if embeddings are enabled.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational