evolve

Run a preflight-gated evolution loop with evaluator scoring and experiment databases.

835|211|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/GAIR-NLP/ASI-Evolve --skill evolve-gair-nlp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evolve
Source: https://github.com/GAIR-NLP/ASI-Evolve/tree/main/skills/evolve
Command: npx skills add https://github.com/GAIR-NLP/ASI-Evolve --skill evolve-gair-nlp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires sentence-transformers, numpy, faiss, pyyaml, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill automates a disciplined, evaluator-driven evolution loop so agents can iteratively improve code, prompts, algorithms, or pipelines while preserving safety gates and durable memory. It removes ad-hoc trial-and-error by enforcing a preflight confirmation, explicit evaluator timeouts, and a recorded experiment database so each round is traceable and reproducible.

Core Features & Use Cases

  • Preflight gating that collects objective, core score, evaluator command/script, explicit timeout, mutation scope, sampling algorithm, and approval before any mutation or evaluation runs.
  • Four-stage loop (learn → design → experiment → analyze) with two durable memory systems: a cognition store for reusable external insights and an experiment database for node lineage, scores, and analyses.
  • Deterministic CLI toolset (brief, cognition, db, eval, files, summary) to normalize specs, seed and query cognition, sample and record nodes, run evaluators with enforced timeouts, and manage writable file scopes.
  • Pluggable samplers and safety including ucb1/greedy/random/island and custom sampler hooks, serialized database access, best-snapshot persistence, and path guards to prevent unauthorized file writes.
  • Use Case: Run reproducible architecture or prompt search where each candidate is evaluated by an automated metric, and lessons are carried forward to avoid wasted retries.

Quick Start

Normalize the run brief, set an explicit evaluator command and timeout, confirm preflight with the user, and then execute iterative rounds anchored on sampled parents using the provided CLI wrappers.

Frequently Asked Questions about evolve

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

FAQPage Schema
How do I automate prompt or algorithm optimization using an evaluator-driven evolution loop?

Automated evaluator-driven evolution uses a preflight-gated, four-stage loop of learn, design, experiment, and analyze to iteratively improve prompts or algorithms while recording node lineages and scores in a durable database for reproducible results.

What is preflight gating in an automated code or pipeline evolution workflow?

Preflight gating in automated evolution workflows is a safety mechanism that collects the run specification, evaluator command, explicit timeout, and mutation scope to confirm approval before any file mutations or evaluations are executed.

How do I run reproducible architecture search with automated scoring and bounded file writes?

Reproducible architecture search requires running iterative evolution rounds anchored on sampled parents, using deterministic CLI wrappers to enforce path guards, manage writable file scopes, and serialize database actions for traceable scoring.

Can I use custom sampling algorithms like ucb1 or greedy for evolutionary search?

Custom sampling algorithms like ucb1, greedy, random, and island are supported as pluggable samplers in the evolutionary search loop, allowing you to sample parent candidates and carry forward lessons to avoid wasted retries.

What dependencies do I need to set up an evolutionary search pipeline for code optimization?

Setting up an evolutionary search pipeline requires installing sentence-transformers, numpy, faiss, and pyyaml to support the cognition store for reusable insights and the serialized experiment database for recording node lineages.

Why does my automated evaluator timeout during the experiment phase of the evolution loop?

Automated evaluator timeouts occur when the evaluator command or script exceeds the explicit timeout limit defined during the preflight gating stage, ensuring disciplined and bounded evaluation within the experiment phase.