ava-self-evolution

Mines real agent run traces to detect skill and plugin regressions and propose fixes.

1|Updated Aug 14, 2026
One-click install
npx skills add https://github.com/zhiyuan-zhang0206/Ava --skill ava-self-evolution-zhiyuan-zhang0206
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ava-self-evolution
Source: https://github.com/zhiyuan-zhang0206/Ava/tree/main/ava_builtins/skills/ava-self-evolution
Command: npx skills add https://github.com/zhiyuan-zhang0206/Ava --skill ava-self-evolution-zhiyuan-zhang0206

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires httpx, psycopg, and includes references (resource) components.

What problem does it solve? AI agent skills and plugins change constantly, but there is no systematic way to know whether a recent edit degraded real-world behavior. This Skill closes that loop by collecting actual agent run traces, labeling failures, attributing regressions to recently changed skills or plugins, and proposing concrete fixes. ## Core Features & Use Cases - Trace Dataset Collection: Harvests real agent runs from Loki events and Postgres into a durable JSONL dataset with transcripts, tool calls, and ok/fumbled/failed labels. - Regression Mining & Attribution: Clusters failed and fumbled runs by skill and plugin contribution, then confirms root causes via agent self-reflection (debrief) and deep-dive workers. - Evaluation Loop: Re-runs replay-safe tasks with fresh agents, scores them with a completion/efficiency rubric, and keeps skill text edits only when measured scores improve. - Use Case: After a daily batch of ~100 runs, detect that a recently edited skill correlates with five fumbled runs, identify the exact instruction causing failures, apply a fix, verify the rubric score improves, and open a PR for human review. ## Quick Start Run the self-evolution batch flow to collect yesterday's agent runs and report any regressions tied to recently changed skills.

Frequently Asked Questions about ava-self-evolution

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

FAQPage Schema
How do I detect regressions in AI agent skills after editing them?▼

Collect real run traces into a JSONL dataset, label each run ok, fumbled, or failed using objective signals like user corrections and exec failures, then cluster bad runs by the skills they touched. Overlap those clusters with skills changed in the same git window to identify suspects.

How to evaluate a skill prompt change without ground truth?▼

Use comparative measurement: re-run the same replay-safe tasks with fresh agents before and after the edit, score each run with a completion and efficiency rubric, and keep the edit only if the mean overall score rises. Absolute quality cannot be measured without an answer key.

What tasks are safe to replay for agent evaluation?▼

Only pure read/compute tasks are replay-safe. The is_replay_safe gate skips any run whose tool calls include shell commands, file writes, message sending, scheduling, or external API calls, since replaying those would cause real side effects.

Why does the daily scan alert on an empty dataset?▼

An empty dataset means the data source is broken, not that nothing happened, so the scan exits with an alert code. The only exception is a window where every run was a TEST- prefixed benchmark spawn excluded by design, which exits cleanly.

How are agent evaluation runs protected against cheating?▼

A layered audit checks three leak surfaces: shared cluster memory, web search, and access to the original run's transcripts or results. Eval agents run with restricted SDK and gateway access, and any run that touches a leak surface is invalidated and excluded from the mean score.