Creator · gaasher
Last updated · Sep 4, 2026
Use when the user wants to evolve an ML model/program through population-based search rather than a single sequential refine loop — a generational evolution where parallel proposers each apply one small SEARCH/REPLACE diff to a parent, scored by a cascade-evaluated training run,
Creator · gaasher
Last updated · Sep 4, 2026
Use when the user wants to evolve an ML model/program through population-based search rather than a single sequential refine loop — a generational evolution where parallel proposers each apply one small SEARCH/REPLACE diff to a parent, scored by a cascade-evaluated training run,
Creator · gaasher
Last updated · Sep 4, 2026
Use when the user wants to evolve an ML model/program through population-based search rather than a single sequential refine loop — a generational evolution where parallel proposers each apply one small SEARCH/REPLACE diff to a parent, scored by a cascade-evaluated training run,
Creator · gaasher
Last updated · Sep 4, 2026
Use when the user wants to evolve an ML model/program through population-based search rather than a single sequential refine loop — a generational evolution where parallel proposers each apply one small SEARCH/REPLACE diff to a parent, scored by a cascade-evaluated training run,
Sandbox only
Install targets
Codex install prompt
Install the "alpha-evolve" agent skill from https://github.com/gaasher/Agent-Loop-Skills/tree/main/loops/alpha-evolve. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Use when the user wants to evolve an ML model/program through population-based search rather than a single sequential refine loop — a generational evolution where parallel proposers each apply one small SEARCH/REPLACE diff to a parent, scored by a cascade-evaluated training run, and children are kept in a MAP-Elites archive across islands (with migration + checkpointing) so diverse high performers survive. A finite, bounded-parallelism re-creation of AlphaEvolve/OpenEvolve, bent for ML autoresearch. Runs to a fixed compute budget or until interrupted. Not for the sequential single-thread autoresearch loops (one change → measure → keep/revert), and not for verifying a known bug or external claim — this is parallel, diversity-preserving search over a program. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"gaasher-alpha-evolve","task":"Install alpha-evolve","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
Research agents
I need my agent to research a topic, compare sources, and produce a concise report.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add gaasher/Agent-Loop-Skills --skill alpha-evolve
Maintenance
active
2mo since push
Risk
Needs review
Permission surface may require sandboxing
GitHub quality
163
63/100 Quality · 77/100 Trust
Coverage tags
Review notes
Permission surface may require sandboxing · Financial research output is not financial advice; require human review before any live investment decision
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
PromisingUseful candidate, but compare it with alternatives before adopting.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
163 GitHub stars
Repo activity
163 stars, 19 forks
Maintenance
2mo since push
License
MIT
Install
npx skills add gaasher/Agent-Loop-Skills --skill alpha-evolve
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add gaasher/Agent-Loop-Skills --skill alpha-evolveDo not use when
Alternative
1.9K Stars
npx skills add yanliudesign/mono-color-skill --skill mono-color
Alternative
61.0K Stars
npx skills add mvanhorn/last30days-skill -g
Alternative
38.4K Stars
npx skills add Imbad0202/academic-research-skills
Alternative
28.0K Stars
npx skills add assafelovic/gpt-researcher
Agent safety v2
Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
Test manually in an isolated workspace and compare against safer alternatives.
high
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
medium
Skill may inspect schemas, query databases, or work with persistent stores.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20alpha-evolve%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20alpha-evolve%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/gaasher-alpha-evolve/install
Agent should check
Copy prompt
Task: Use alpha-evolve in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20alpha-evolve%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/gaasher-alpha-evolve/install
Install command: npx skills add gaasher/Agent-Loop-Skills --skill alpha-evolve
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/gaasher-alpha-evolve/install
LLM text format
/api/skills/gaasher-alpha-evolve/install?format=text
Find alternatives
/api/skills/search?q=alpha-evolve&limit=3
Agent prompt
Use alpha-evolve for this task. Review https://www.openagentskill.com/api/skills/gaasher-alpha-evolve/install, then install with: npx skills add gaasher/Agent-Loop-Skills --skill alpha-evolveRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/gaasher-alpha-evolve
LLM text
/api/registry/manifest/gaasher-alpha-evolve?format=text
Install alias
/api/registry/install/gaasher-alpha-evolve
Recommend
/api/registry/recommend?task=Use%20alpha-evolve%20in%20an%20agent%20workflow&limit=3
Agent fit
Research agents
Use-case tags
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Prototype with this skill first; keep a fallback candidate ready.
Role in stack
Fallback candidate
Primary fit
Research agents
Trust label
Prototype first
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
INFO163 GitHub stars
Stars/forks activity
CHECK163 stars, 19 forks; issue activity unavailable in current metadata
Recent maintenance
PASS2mo since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Useful candidate, but compare it with alternatives before adopting.
Workflow fit
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Work with data stores
I need my agent to inspect database schemas, write SQL, and explain query results.
Automate repeated work
I need my agent to automate a repeated workflow across tools and files.
Workflow fit
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Turn skills into distribution
A workflow for turning newly indexed skills into SEO briefs, social drafts, comparison pages, and reusable publishing workflows.
Inspect, patch, and verify code
A workflow for software agents that inspect repositories, review pull requests, generate tests, and turn findings into shippable patches.
Alternative shortlist
Similar skills that may fit this task.
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for 单色海报、双色印刷、单色调视觉、蓝色/绿色孔版印刷、risograph、网点照片、复古或当代编辑排版、zine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
Academic Research Skills for Claude Code: research → write → review → revise → finalize
Run autonomous deep research over web and local sources
--- name: alpha-evolve description: > Use when the user wants to evolve an ML model/program through population-based search rather than a single sequential refine loop — a generational evolution where parallel proposers each apply one small SEARCH/REPLACE diff to a parent, scored by a cascade-evaluated training run, and children are kept in a MAP-Elites archive across islands (with migration + checkpointing) so diverse high performers survive. A finite, bounded-parallelism re-creation of AlphaEvolve/OpenEvolve, bent for ML autoresearch. Runs to a fixed compute budget or until interrupted. Not for the sequential single-thread autoresearch loops (one change → measure → keep/revert), and not for verifying a known bug or external claim — this is parallel, diversity-preserving search over a program. compatibility: Requires Python 3.9+ metadata: version: "0.1.0" ---
# Alpha-Evolve
> Reference (read if you need the algorithm's details): AlphaEvolve — https://arxiv.org/abs/2506.13131 · > OpenEvolve (open-source impl) — https://github.com/algorithmicsuperintelligence/openevolve
A **population-based evolutionary** loop over a program. The artifact is the editable model code; a **child** is one analysis-informed **SEARCH/REPLACE diff** to a parent, and the feedback signal is a **cascade-evaluated training run** (`<metric>`, smoke→full). Children are placed in a **MAP-Elites archive across islands** (complexity × diversity axes), so a child survives by being either better or more novel, not just better. The discipline this enforces: **diversity is preserved, not collapsed** — diverse high performers co-exist instead of one local optimum winning. You are the controller: sample a parent + inspirations, spawn parallel Mutators to propose and evaluate children, place them, migrate between islands, checkpoint. Loops to a fixed compute budget or until interrupted.
## When to use
Use this for parallel, diversity-preserving search over a model/program where many variants explore at once and the archive keeps the illuminated frontier. Default to broad island coverage; if quality stalls, bias selection toward exploiting top elites; if coverage stalls, bias toward empty cells. Not for the sequential autoresearch loops (one change at a time), and not for fixing a known anomaly.
The cast (both in this folder): `roles/Mutator.md` produces + cascade-evaluates one child (the generation step); `schemas/result.schema.json` is the result a Mutator returns.
## Setup
Resolve bindings interactively. If `loop.run.yaml` exists in the working dir, load it, confirm the values in one line, and skip to the loop. Otherwise: on Claude Code (the `AskUserQuestion` tool is available, `<host>` = `claude-code`) infer a likely value for each binding and present it as the recommended option; on other hosts (`<host>` = `other`) ask each as a quoted plain-text prompt. Then write `loop.run.yaml` (format: `examples/run.example.yaml`) and confirm the values before creating any other files. `<host>` also decides execution: Claude Code spawns real `Agent` Mutators in parallel (capped at `<concurrency>`); other hosts degrade to running a generation's children serially (identical algorithm).
**Probe the box first (mandatory — measure, never assume `<concurrency>`).** Record and report: - **CPU cores** → `<cores>`: `python3 -c "import os; print(os.cpu_count())"`. - **RAM** → `<ram_gb>`: macOS `sysctl -n hw.memsize`; Linux `grep MemTotal /proc/meminfo`. - **Accelerator** → `<accelerator>`/`<vram>`/`<gpu_count>`: `nvidia-smi --query-gpu=name,memory.total,count --format=csv` (NVIDIA); else macOS Apple GPU/MPS; else CPU-only.
| binding | meaning | default | how to infer | |---|---|---|---| | `<metric>` + `<metric_direction>` | scalar to optimize; min/maximize | — | ask; scan eval output for the reported metric | | `<run_cmd>` / `<entrypoint>` | command for one training run (the evaluator) | — | `pyproject.toml`/`.venv`/`uv`/README | | `<editable_files>` | the program being evolved (e.g. `model.py`, `config.yaml`); never the harness or data | — | ask explicitly — this is the code that gets mutated; do not default it (multi-select on Claude Code) | | `<sandbox_root>` | where `lae/` is created | `./sandbox` | — | | `<gate>` + `<budget>` | one full run's size: `time`/`epochs` + amount; the FIXED eval budget applied to every program | — | identify the duration key now (e.g. `train.epochs`) so the controller can override it | | `<total_budget>` | total compute = number of full training runs (or wall-clock minutes); the single cost dial | — | ask | | `<concurrency>` | parallel evaluations `C` | derived from the probe | CPU-only → `max(1, <cores>//4)`; single GPU/MPS → `1` (ask if more fit `<vram>`); multi-GPU → `<gpu_count>` (pin one child/GPU) |
`num_generations` is **derived**: `ceil(<total_budget> / <concurrency>)`. The cascade is **derived** from `<budget>` (not asked): smoke = ~1 epoch / a small subset, full = `<budget>`, gate = child's smoke `<metric>` ≥ parent's smoke. `<budget>`/`<metric>`/eval split are FIXED — never mutation targets (a child may not "train longer" to look better); changing them means re-running the whole loop.
**Advanced (opt-in).** Ask one yes/no: "Use defaults for the evolutionary settings, or customize?" Defaults are faithful to AlphaEvolve/OpenEvolve — use them and ask nothing more. Only on "customize" ask for each (showing the default as recommended): `num_islands` (4), `num_top` (3), `num_diverse` (2), `num_bins` (10), `migration_interval` (5), `diversity_reference_size` (10), `pop_per_island` (40), `seed` (42). Axes are fixed: complexity × diversity. See `examples/run.example.yaml` for the shape.
Print the resolved bindings + the probe + derived `num_generations`, and **do not create files or launch until the user confirms**. Then initialise the sandbox (header rows only; `programs/` is created as children are evaluated): ``` <sandbox_root>/lae/ ├── archive.tsv ← current elites = program database + checkpoint ├── history.tsv ← append-only record of every child ├── leaderboard.md ← rendered UI └── programs/ ← one self-contained dir per program ```
## The controller (loop)
You maintain `num_islands` MAP-Elites maps in `archive.tsv`, the append-only `history.tsv`, running per-axis percentile stats, and `leaderboard.md`. **You are the sole writer of all shared logs** — Mutators only return results, so there are no write races. Copy this checklist and tick items off:
- [ ] Setup done: probe recorded, bindings confirmed, sandbox initialised, `num_generations` derived. - [ ] GEN 0 — in each island, create the baseline program (a copy of `<editable_files>`) + optionally a few stochastic variants; cascade-evaluate; place in the archive. - [ ] Per generation: build EXACTLY `<concurrency>` tasks (round-robin island, seeded-rule parent, top `num_top` + `num_diverse` most-diverse inspirations); make each child dir by **copying** the parent program + harness. - [ ] Run the `C` Mutators (spawn-or-degrade), each with `roles/Mutator.md`, parent code, inspirations, parent artifacts, its child dir, and the smoke/full budgets. - [ ] For each returned child: append a `history.tsv` row; if `evaluated`, compute its niche → cell and place it in the island map iff `<metric>` is better (`kept=y`); record `smoke_dropped`/`crash` without placing. - [ ] Re-render `leaderboard.md`; checkpoint (`archive.tsv` is the checkpoint); print a status line. - [ ] Every `migration_interval` generations: ring-migrate top elites island k → k+1. - [ ] Stop at `<total_budget>` (reserve a little for synthesis), then synthesize the final report.
**Niche computation (you do this, from a child's sandbox):** - **`complexity`** = trainable param count (fallback: total LOC of the editable files **+ any files the child added**), **log10-scaled**. - **`diversity`** = average normalized edit distance of the program's concatenated code (editable + added files) to a random sample of `diversity_reference_size` programs from its island (vs the baseline if the island is near-empty). Higher = more novel. - Normalize each axis with **running ~5th/95th percentiles** (not raw min/max, so one outlier can't collapse the range): `scaled = clamp01((v − p5)/(p95 − p5))`; `bin = min(num_bins−1, int(scaled × num_bins))`; `cell = (complexity_bin, diversity_bin)`. **Re-bin** existing elites when a percentile shifts enough to move an edge (keep the higher `<metric>` on collisions; the archive is small).
**The Mutator's prompt (the sampler):** parent code + inspirations + the parent's rendered artifacts (`<metric>`, per-class accuracy, loss curve, stderr) + the instruction to return one SEARCH/REPLACE diff. Single harness model — no LLM ensemble. The Mutator applies its diff in the child dir, cascade-evaluates at the FIXED `<budget>` (the controller injects/caps the duration key on the run command), and returns a result validated against `schemas/result.schema.json`: ```json {"child_id": "g3-i1-a2", "parent_id": "g1-i1-a0", "approach_summary": "add BatchNorm after conv2", "sandbox_path": "<sandbox_root>/lae/programs/g3-i1-a2", "status": "evaluated", "smoke_metric": 0.61, "metric": 0.71} ``` `status` ∈ {`evaluated`, `smoke_dropped`, `crash`}; `metric` is null unless `evaluated`. Mutators compute nothing about the archive — the controller derives every niche from the sandbox.
**Program sandboxes.** A parallel population doesn't map onto branches, so every program is a self-contained, fully-runnable dir `<sandbox_root>/lae/programs/<child_id>/`; the archive references it by id. Build each child dir by **copying real files** (the parent's `<editable_files>`, then apply the diff, **plus the harness/entrypoint code it imports**) and evaluate from inside it (`cd <child_dir> && <entrypoint>`). **Symlink only large read-only data**, never the entrypoint or any imported `.py`: Python resolves a symlinked script's `__file__` to the link target, so `sys.path[0]` becomes the original dir and the child's `model.py`/`dataset.py` are silently shadowed by the baselines — every architecture/data mutation becomes a no-op (tell-tale: identical loss curves across different "architectures"). **Isolation sanity gate:** the harness logs the param count / a code fingerprint; flag any child whose code changed but whose metric/loss curve is identical to its parent's (shadowed), and fix the sandbox before placing it. The repo working tree is never mutated.
**Final synthesis.** Report the global-best program + its `lae/programs/<id>/` path, the illuminated complexity×diversity map (coverage + who won each region), per-island bests, and 2–3 notably diverse runners-up.
## Ledger
All three logs live under `<sandbox_root>/lae/`, tab-separated, never commas in free text. The controller is the sole writer; resume from `archive.tsv` + `history.tsv` if interrupted.
**`archive.tsv`** — current elites + checkpoint. Header `island cell metric child_id parent_id sandbox_path complexity diversity`: ``` island cell metric child_id parent_id sandbox_path complexity diversity 0 (2,7) 0.7100 g4-i0-a1 g2-i0-a3 lae/programs/g4-i0-a1 2.1M 0.71 ``` **`history.tsv`** — every child, append-only. Header `gen island parent_id child_id smoke_metric full_metric status kept cell`: ``` gen island parent_id child_id smoke_metric full_metric status kept cell 4 0 g2-i0-a3 g4-i0-a1 0.61 0.71 evaluated y (2,7) 4 1 g2-i1-a0 g4-i1-a2 0.40 - smoke_dropped n - ``` **`leaderboard.md`** — re-rendered each generation: global best + per-island coverage + the archive ranked by `<metric>`. Report the **best** program at stop (not the last), the archive coverage, and a few diverse runners-up. Leave `lae/` untracked.
## Constraints
- A child works **only inside its own `lae/programs/<child_id>/` dir** — it may edit the copied `<editable_files>` and create new files there, but never modify any file outside it (the repo, the read-only harness, the data, other programs' dirs are g
Source provenance
Decision snapshot
recent repository activity
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for alpha-evolve, ready for a manual X post.
alpha-evolve: Use when the user wants to evolve an ML model/program through population-based search rather... 163 stars https://www.openagentskill.com/skills/gaasher-alpha-evolve?ref=x
Listing + install path for alpha-evolve: https://www.openagentskill.com/skills/gaasher-alpha-evolve?ref=x Install: npx skills add gaasher/Agent-Loop-Skills --skill alpha-evolve
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to gaasher but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/gaasher-alpha-evolve?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/gaasher-alpha-evolve?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/gaasher-alpha-evolve/audit)
[](https://www.openagentskill.com/skills/gaasher-alpha-evolve?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)gaasher
@gaasher
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Sandbox only
mono-color
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for 单色海报、双色印刷、单色调视觉、蓝色/绿色孔版印刷、risograph、网点照片、复古或当代编辑排版、zine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
1.9K StarsLast30days Skill
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
61.0K StarsAcademic Research Skills
Academic Research Skills for Claude Code: research → write → review → revise → finalize
38.4K StarsGPT Researcher
Run autonomous deep research over web and local sources
28.0K StarsSandbox only
Install targets
Codex install prompt
Install the "alpha-evolve" agent skill from https://github.com/gaasher/Agent-Loop-Skills/tree/main/loops/alpha-evolve. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Use when the user wants to evolve an ML model/program through population-based search rather than a single sequential refine loop — a generational evolution where parallel proposers each apply one small SEARCH/REPLACE diff to a parent, scored by a cascade-evaluated training run, and children are kept in a MAP-Elites archive across islands (with migration + checkpointing) so diverse high performers survive. A finite, bounded-parallelism re-creation of AlphaEvolve/OpenEvolve, bent for ML autoresearch. Runs to a fixed compute budget or until interrupted. Not for the sequential single-thread autoresearch loops (one change → measure → keep/revert), and not for verifying a known bug or external claim — this is parallel, diversity-preserving search over a program. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"gaasher-alpha-evolve","task":"Install alpha-evolve","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
Research agents
I need my agent to research a topic, compare sources, and produce a concise report.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add gaasher/Agent-Loop-Skills --skill alpha-evolve
Maintenance
active
2mo since push
Risk
Needs review
Permission surface may require sandboxing
GitHub quality
163
63/100 Quality · 77/100 Trust
Coverage tags
Review notes
Permission surface may require sandboxing · Financial research output is not financial advice; require human review before any live investment decision
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
PromisingUseful candidate, but compare it with alternatives before adopting.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
163 GitHub stars
Repo activity
163 stars, 19 forks
Maintenance
2mo since push
License
MIT
Install
npx skills add gaasher/Agent-Loop-Skills --skill alpha-evolve
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add gaasher/Agent-Loop-Skills --skill alpha-evolveDo not use when
Alternative
1.9K Stars
npx skills add yanliudesign/mono-color-skill --skill mono-color
Alternative
61.0K Stars
npx skills add mvanhorn/last30days-skill -g
Alternative
38.4K Stars
npx skills add Imbad0202/academic-research-skills
Alternative
28.0K Stars
npx skills add assafelovic/gpt-researcher
Agent safety v2
Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
Test manually in an isolated workspace and compare against safer alternatives.
high
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
medium
Skill may inspect schemas, query databases, or work with persistent stores.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20alpha-evolve%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20alpha-evolve%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/gaasher-alpha-evolve/install
Agent should check
Copy prompt
Task: Use alpha-evolve in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20alpha-evolve%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/gaasher-alpha-evolve/install
Install command: npx skills add gaasher/Agent-Loop-Skills --skill alpha-evolve
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/gaasher-alpha-evolve/install
LLM text format
/api/skills/gaasher-alpha-evolve/install?format=text
Find alternatives
/api/skills/search?q=alpha-evolve&limit=3
Agent prompt
Use alpha-evolve for this task. Review https://www.openagentskill.com/api/skills/gaasher-alpha-evolve/install, then install with: npx skills add gaasher/Agent-Loop-Skills --skill alpha-evolveRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/gaasher-alpha-evolve
LLM text
/api/registry/manifest/gaasher-alpha-evolve?format=text
Install alias
/api/registry/install/gaasher-alpha-evolve
Recommend
/api/registry/recommend?task=Use%20alpha-evolve%20in%20an%20agent%20workflow&limit=3
Agent fit
Research agents
Use-case tags
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Prototype with this skill first; keep a fallback candidate ready.
Role in stack
Fallback candidate
Primary fit
Research agents
Trust label
Prototype first
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
INFO163 GitHub stars
Stars/forks activity
CHECK163 stars, 19 forks; issue activity unavailable in current metadata
Recent maintenance
PASS2mo since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Useful candidate, but compare it with alternatives before adopting.
Workflow fit
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Work with data stores
I need my agent to inspect database schemas, write SQL, and explain query results.
Automate repeated work
I need my agent to automate a repeated workflow across tools and files.
Workflow fit
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Turn skills into distribution
A workflow for turning newly indexed skills into SEO briefs, social drafts, comparison pages, and reusable publishing workflows.
Inspect, patch, and verify code
A workflow for software agents that inspect repositories, review pull requests, generate tests, and turn findings into shippable patches.
Alternative shortlist
Similar skills that may fit this task.
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for 单色海报、双色印刷、单色调视觉、蓝色/绿色孔版印刷、risograph、网点照片、复古或当代编辑排版、zine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
Academic Research Skills for Claude Code: research → write → review → revise → finalize
Run autonomous deep research over web and local sources
--- name: alpha-evolve description: > Use when the user wants to evolve an ML model/program through population-based search rather than a single sequential refine loop — a generational evolution where parallel proposers each apply one small SEARCH/REPLACE diff to a parent, scored by a cascade-evaluated training run, and children are kept in a MAP-Elites archive across islands (with migration + checkpointing) so diverse high performers survive. A finite, bounded-parallelism re-creation of AlphaEvolve/OpenEvolve, bent for ML autoresearch. Runs to a fixed compute budget or until interrupted. Not for the sequential single-thread autoresearch loops (one change → measure → keep/revert), and not for verifying a known bug or external claim — this is parallel, diversity-preserving search over a program. compatibility: Requires Python 3.9+ metadata: version: "0.1.0" ---
# Alpha-Evolve
> Reference (read if you need the algorithm's details): AlphaEvolve — https://arxiv.org/abs/2506.13131 · > OpenEvolve (open-source impl) — https://github.com/algorithmicsuperintelligence/openevolve
A **population-based evolutionary** loop over a program. The artifact is the editable model code; a **child** is one analysis-informed **SEARCH/REPLACE diff** to a parent, and the feedback signal is a **cascade-evaluated training run** (`<metric>`, smoke→full). Children are placed in a **MAP-Elites archive across islands** (complexity × diversity axes), so a child survives by being either better or more novel, not just better. The discipline this enforces: **diversity is preserved, not collapsed** — diverse high performers co-exist instead of one local optimum winning. You are the controller: sample a parent + inspirations, spawn parallel Mutators to propose and evaluate children, place them, migrate between islands, checkpoint. Loops to a fixed compute budget or until interrupted.
## When to use
Use this for parallel, diversity-preserving search over a model/program where many variants explore at once and the archive keeps the illuminated frontier. Default to broad island coverage; if quality stalls, bias selection toward exploiting top elites; if coverage stalls, bias toward empty cells. Not for the sequential autoresearch loops (one change at a time), and not for fixing a known anomaly.
The cast (both in this folder): `roles/Mutator.md` produces + cascade-evaluates one child (the generation step); `schemas/result.schema.json` is the result a Mutator returns.
## Setup
Resolve bindings interactively. If `loop.run.yaml` exists in the working dir, load it, confirm the values in one line, and skip to the loop. Otherwise: on Claude Code (the `AskUserQuestion` tool is available, `<host>` = `claude-code`) infer a likely value for each binding and present it as the recommended option; on other hosts (`<host>` = `other`) ask each as a quoted plain-text prompt. Then write `loop.run.yaml` (format: `examples/run.example.yaml`) and confirm the values before creating any other files. `<host>` also decides execution: Claude Code spawns real `Agent` Mutators in parallel (capped at `<concurrency>`); other hosts degrade to running a generation's children serially (identical algorithm).
**Probe the box first (mandatory — measure, never assume `<concurrency>`).** Record and report: - **CPU cores** → `<cores>`: `python3 -c "import os; print(os.cpu_count())"`. - **RAM** → `<ram_gb>`: macOS `sysctl -n hw.memsize`; Linux `grep MemTotal /proc/meminfo`. - **Accelerator** → `<accelerator>`/`<vram>`/`<gpu_count>`: `nvidia-smi --query-gpu=name,memory.total,count --format=csv` (NVIDIA); else macOS Apple GPU/MPS; else CPU-only.
| binding | meaning | default | how to infer | |---|---|---|---| | `<metric>` + `<metric_direction>` | scalar to optimize; min/maximize | — | ask; scan eval output for the reported metric | | `<run_cmd>` / `<entrypoint>` | command for one training run (the evaluator) | — | `pyproject.toml`/`.venv`/`uv`/README | | `<editable_files>` | the program being evolved (e.g. `model.py`, `config.yaml`); never the harness or data | — | ask explicitly — this is the code that gets mutated; do not default it (multi-select on Claude Code) | | `<sandbox_root>` | where `lae/` is created | `./sandbox` | — | | `<gate>` + `<budget>` | one full run's size: `time`/`epochs` + amount; the FIXED eval budget applied to every program | — | identify the duration key now (e.g. `train.epochs`) so the controller can override it | | `<total_budget>` | total compute = number of full training runs (or wall-clock minutes); the single cost dial | — | ask | | `<concurrency>` | parallel evaluations `C` | derived from the probe | CPU-only → `max(1, <cores>//4)`; single GPU/MPS → `1` (ask if more fit `<vram>`); multi-GPU → `<gpu_count>` (pin one child/GPU) |
`num_generations` is **derived**: `ceil(<total_budget> / <concurrency>)`. The cascade is **derived** from `<budget>` (not asked): smoke = ~1 epoch / a small subset, full = `<budget>`, gate = child's smoke `<metric>` ≥ parent's smoke. `<budget>`/`<metric>`/eval split are FIXED — never mutation targets (a child may not "train longer" to look better); changing them means re-running the whole loop.
**Advanced (opt-in).** Ask one yes/no: "Use defaults for the evolutionary settings, or customize?" Defaults are faithful to AlphaEvolve/OpenEvolve — use them and ask nothing more. Only on "customize" ask for each (showing the default as recommended): `num_islands` (4), `num_top` (3), `num_diverse` (2), `num_bins` (10), `migration_interval` (5), `diversity_reference_size` (10), `pop_per_island` (40), `seed` (42). Axes are fixed: complexity × diversity. See `examples/run.example.yaml` for the shape.
Print the resolved bindings + the probe + derived `num_generations`, and **do not create files or launch until the user confirms**. Then initialise the sandbox (header rows only; `programs/` is created as children are evaluated): ``` <sandbox_root>/lae/ ├── archive.tsv ← current elites = program database + checkpoint ├── history.tsv ← append-only record of every child ├── leaderboard.md ← rendered UI └── programs/ ← one self-contained dir per program ```
## The controller (loop)
You maintain `num_islands` MAP-Elites maps in `archive.tsv`, the append-only `history.tsv`, running per-axis percentile stats, and `leaderboard.md`. **You are the sole writer of all shared logs** — Mutators only return results, so there are no write races. Copy this checklist and tick items off:
- [ ] Setup done: probe recorded, bindings confirmed, sandbox initialised, `num_generations` derived. - [ ] GEN 0 — in each island, create the baseline program (a copy of `<editable_files>`) + optionally a few stochastic variants; cascade-evaluate; place in the archive. - [ ] Per generation: build EXACTLY `<concurrency>` tasks (round-robin island, seeded-rule parent, top `num_top` + `num_diverse` most-diverse inspirations); make each child dir by **copying** the parent program + harness. - [ ] Run the `C` Mutators (spawn-or-degrade), each with `roles/Mutator.md`, parent code, inspirations, parent artifacts, its child dir, and the smoke/full budgets. - [ ] For each returned child: append a `history.tsv` row; if `evaluated`, compute its niche → cell and place it in the island map iff `<metric>` is better (`kept=y`); record `smoke_dropped`/`crash` without placing. - [ ] Re-render `leaderboard.md`; checkpoint (`archive.tsv` is the checkpoint); print a status line. - [ ] Every `migration_interval` generations: ring-migrate top elites island k → k+1. - [ ] Stop at `<total_budget>` (reserve a little for synthesis), then synthesize the final report.
**Niche computation (you do this, from a child's sandbox):** - **`complexity`** = trainable param count (fallback: total LOC of the editable files **+ any files the child added**), **log10-scaled**. - **`diversity`** = average normalized edit distance of the program's concatenated code (editable + added files) to a random sample of `diversity_reference_size` programs from its island (vs the baseline if the island is near-empty). Higher = more novel. - Normalize each axis with **running ~5th/95th percentiles** (not raw min/max, so one outlier can't collapse the range): `scaled = clamp01((v − p5)/(p95 − p5))`; `bin = min(num_bins−1, int(scaled × num_bins))`; `cell = (complexity_bin, diversity_bin)`. **Re-bin** existing elites when a percentile shifts enough to move an edge (keep the higher `<metric>` on collisions; the archive is small).
**The Mutator's prompt (the sampler):** parent code + inspirations + the parent's rendered artifacts (`<metric>`, per-class accuracy, loss curve, stderr) + the instruction to return one SEARCH/REPLACE diff. Single harness model — no LLM ensemble. The Mutator applies its diff in the child dir, cascade-evaluates at the FIXED `<budget>` (the controller injects/caps the duration key on the run command), and returns a result validated against `schemas/result.schema.json`: ```json {"child_id": "g3-i1-a2", "parent_id": "g1-i1-a0", "approach_summary": "add BatchNorm after conv2", "sandbox_path": "<sandbox_root>/lae/programs/g3-i1-a2", "status": "evaluated", "smoke_metric": 0.61, "metric": 0.71} ``` `status` ∈ {`evaluated`, `smoke_dropped`, `crash`}; `metric` is null unless `evaluated`. Mutators compute nothing about the archive — the controller derives every niche from the sandbox.
**Program sandboxes.** A parallel population doesn't map onto branches, so every program is a self-contained, fully-runnable dir `<sandbox_root>/lae/programs/<child_id>/`; the archive references it by id. Build each child dir by **copying real files** (the parent's `<editable_files>`, then apply the diff, **plus the harness/entrypoint code it imports**) and evaluate from inside it (`cd <child_dir> && <entrypoint>`). **Symlink only large read-only data**, never the entrypoint or any imported `.py`: Python resolves a symlinked script's `__file__` to the link target, so `sys.path[0]` becomes the original dir and the child's `model.py`/`dataset.py` are silently shadowed by the baselines — every architecture/data mutation becomes a no-op (tell-tale: identical loss curves across different "architectures"). **Isolation sanity gate:** the harness logs the param count / a code fingerprint; flag any child whose code changed but whose metric/loss curve is identical to its parent's (shadowed), and fix the sandbox before placing it. The repo working tree is never mutated.
**Final synthesis.** Report the global-best program + its `lae/programs/<id>/` path, the illuminated complexity×diversity map (coverage + who won each region), per-island bests, and 2–3 notably diverse runners-up.
## Ledger
All three logs live under `<sandbox_root>/lae/`, tab-separated, never commas in free text. The controller is the sole writer; resume from `archive.tsv` + `history.tsv` if interrupted.
**`archive.tsv`** — current elites + checkpoint. Header `island cell metric child_id parent_id sandbox_path complexity diversity`: ``` island cell metric child_id parent_id sandbox_path complexity diversity 0 (2,7) 0.7100 g4-i0-a1 g2-i0-a3 lae/programs/g4-i0-a1 2.1M 0.71 ``` **`history.tsv`** — every child, append-only. Header `gen island parent_id child_id smoke_metric full_metric status kept cell`: ``` gen island parent_id child_id smoke_metric full_metric status kept cell 4 0 g2-i0-a3 g4-i0-a1 0.61 0.71 evaluated y (2,7) 4 1 g2-i1-a0 g4-i1-a2 0.40 - smoke_dropped n - ``` **`leaderboard.md`** — re-rendered each generation: global best + per-island coverage + the archive ranked by `<metric>`. Report the **best** program at stop (not the last), the archive coverage, and a few diverse runners-up. Leave `lae/` untracked.
## Constraints
- A child works **only inside its own `lae/programs/<child_id>/` dir** — it may edit the copied `<editable_files>` and create new files there, but never modify any file outside it (the repo, the read-only harness, the data, other programs' dirs are g
Source provenance
Decision snapshot
recent repository activity
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for alpha-evolve, ready for a manual X post.
alpha-evolve: Use when the user wants to evolve an ML model/program through population-based search rather... 163 stars https://www.openagentskill.com/skills/gaasher-alpha-evolve?ref=x
Listing + install path for alpha-evolve: https://www.openagentskill.com/skills/gaasher-alpha-evolve?ref=x Install: npx skills add gaasher/Agent-Loop-Skills --skill alpha-evolve
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to gaasher but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/gaasher-alpha-evolve?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/gaasher-alpha-evolve?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/gaasher-alpha-evolve/audit)
[](https://www.openagentskill.com/skills/gaasher-alpha-evolve?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)gaasher
@gaasher
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Sandbox only
mono-color
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for 单色海报、双色印刷、单色调视觉、蓝色/绿色孔版印刷、risograph、网点照片、复古或当代编辑排版、zine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
1.9K StarsLast30days Skill
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
61.0K StarsAcademic Research Skills
Academic Research Skills for Claude Code: research → write → review → revise → finalize
38.4K StarsGPT Researcher
Run autonomous deep research over web and local sources
28.0K StarsSandbox only
Install targets
Codex install prompt
Install the "alpha-evolve" agent skill from https://github.com/gaasher/Agent-Loop-Skills/tree/main/loops/alpha-evolve. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Use when the user wants to evolve an ML model/program through population-based search rather than a single sequential refine loop — a generational evolution where parallel proposers each apply one small SEARCH/REPLACE diff to a parent, scored by a cascade-evaluated training run, and children are kept in a MAP-Elites archive across islands (with migration + checkpointing) so diverse high performers survive. A finite, bounded-parallelism re-creation of AlphaEvolve/OpenEvolve, bent for ML autoresearch. Runs to a fixed compute budget or until interrupted. Not for the sequential single-thread autoresearch loops (one change → measure → keep/revert), and not for verifying a known bug or external claim — this is parallel, diversity-preserving search over a program. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"gaasher-alpha-evolve","task":"Install alpha-evolve","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
Research agents
I need my agent to research a topic, compare sources, and produce a concise report.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add gaasher/Agent-Loop-Skills --skill alpha-evolve
Maintenance
active
2mo since push
Risk
Needs review
Permission surface may require sandboxing
GitHub quality
163
63/100 Quality · 77/100 Trust
Coverage tags
Review notes
Permission surface may require sandboxing · Financial research output is not financial advice; require human review before any live investment decision
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
PromisingUseful candidate, but compare it with alternatives before adopting.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
163 GitHub stars
Repo activity
163 stars, 19 forks
Maintenance
2mo since push
License
MIT
Install
npx skills add gaasher/Agent-Loop-Skills --skill alpha-evolve
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add gaasher/Agent-Loop-Skills --skill alpha-evolveDo not use when
Alternative
1.9K Stars
npx skills add yanliudesign/mono-color-skill --skill mono-color
Alternative
61.0K Stars
npx skills add mvanhorn/last30days-skill -g
Alternative
38.4K Stars
npx skills add Imbad0202/academic-research-skills
Alternative
28.0K Stars
npx skills add assafelovic/gpt-researcher
Agent safety v2
Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
Test manually in an isolated workspace and compare against safer alternatives.
high
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
medium
Skill may inspect schemas, query databases, or work with persistent stores.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20alpha-evolve%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20alpha-evolve%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/gaasher-alpha-evolve/install
Agent should check
Copy prompt
Task: Use alpha-evolve in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20alpha-evolve%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/gaasher-alpha-evolve/install
Install command: npx skills add gaasher/Agent-Loop-Skills --skill alpha-evolve
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/gaasher-alpha-evolve/install
LLM text format
/api/skills/gaasher-alpha-evolve/install?format=text
Find alternatives
/api/skills/search?q=alpha-evolve&limit=3
Agent prompt
Use alpha-evolve for this task. Review https://www.openagentskill.com/api/skills/gaasher-alpha-evolve/install, then install with: npx skills add gaasher/Agent-Loop-Skills --skill alpha-evolveRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/gaasher-alpha-evolve
LLM text
/api/registry/manifest/gaasher-alpha-evolve?format=text
Install alias
/api/registry/install/gaasher-alpha-evolve
Recommend
/api/registry/recommend?task=Use%20alpha-evolve%20in%20an%20agent%20workflow&limit=3
Agent fit
Research agents
Use-case tags
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Prototype with this skill first; keep a fallback candidate ready.
Role in stack
Fallback candidate
Primary fit
Research agents
Trust label
Prototype first
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
INFO163 GitHub stars
Stars/forks activity
CHECK163 stars, 19 forks; issue activity unavailable in current metadata
Recent maintenance
PASS2mo since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Useful candidate, but compare it with alternatives before adopting.
Workflow fit
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Work with data stores
I need my agent to inspect database schemas, write SQL, and explain query results.
Automate repeated work
I need my agent to automate a repeated workflow across tools and files.
Workflow fit
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Turn skills into distribution
A workflow for turning newly indexed skills into SEO briefs, social drafts, comparison pages, and reusable publishing workflows.
Inspect, patch, and verify code
A workflow for software agents that inspect repositories, review pull requests, generate tests, and turn findings into shippable patches.
Alternative shortlist
Similar skills that may fit this task.
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for 单色海报、双色印刷、单色调视觉、蓝色/绿色孔版印刷、risograph、网点照片、复古或当代编辑排版、zine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
Academic Research Skills for Claude Code: research → write → review → revise → finalize
Run autonomous deep research over web and local sources
--- name: alpha-evolve description: > Use when the user wants to evolve an ML model/program through population-based search rather than a single sequential refine loop — a generational evolution where parallel proposers each apply one small SEARCH/REPLACE diff to a parent, scored by a cascade-evaluated training run, and children are kept in a MAP-Elites archive across islands (with migration + checkpointing) so diverse high performers survive. A finite, bounded-parallelism re-creation of AlphaEvolve/OpenEvolve, bent for ML autoresearch. Runs to a fixed compute budget or until interrupted. Not for the sequential single-thread autoresearch loops (one change → measure → keep/revert), and not for verifying a known bug or external claim — this is parallel, diversity-preserving search over a program. compatibility: Requires Python 3.9+ metadata: version: "0.1.0" ---
# Alpha-Evolve
> Reference (read if you need the algorithm's details): AlphaEvolve — https://arxiv.org/abs/2506.13131 · > OpenEvolve (open-source impl) — https://github.com/algorithmicsuperintelligence/openevolve
A **population-based evolutionary** loop over a program. The artifact is the editable model code; a **child** is one analysis-informed **SEARCH/REPLACE diff** to a parent, and the feedback signal is a **cascade-evaluated training run** (`<metric>`, smoke→full). Children are placed in a **MAP-Elites archive across islands** (complexity × diversity axes), so a child survives by being either better or more novel, not just better. The discipline this enforces: **diversity is preserved, not collapsed** — diverse high performers co-exist instead of one local optimum winning. You are the controller: sample a parent + inspirations, spawn parallel Mutators to propose and evaluate children, place them, migrate between islands, checkpoint. Loops to a fixed compute budget or until interrupted.
## When to use
Use this for parallel, diversity-preserving search over a model/program where many variants explore at once and the archive keeps the illuminated frontier. Default to broad island coverage; if quality stalls, bias selection toward exploiting top elites; if coverage stalls, bias toward empty cells. Not for the sequential autoresearch loops (one change at a time), and not for fixing a known anomaly.
The cast (both in this folder): `roles/Mutator.md` produces + cascade-evaluates one child (the generation step); `schemas/result.schema.json` is the result a Mutator returns.
## Setup
Resolve bindings interactively. If `loop.run.yaml` exists in the working dir, load it, confirm the values in one line, and skip to the loop. Otherwise: on Claude Code (the `AskUserQuestion` tool is available, `<host>` = `claude-code`) infer a likely value for each binding and present it as the recommended option; on other hosts (`<host>` = `other`) ask each as a quoted plain-text prompt. Then write `loop.run.yaml` (format: `examples/run.example.yaml`) and confirm the values before creating any other files. `<host>` also decides execution: Claude Code spawns real `Agent` Mutators in parallel (capped at `<concurrency>`); other hosts degrade to running a generation's children serially (identical algorithm).
**Probe the box first (mandatory — measure, never assume `<concurrency>`).** Record and report: - **CPU cores** → `<cores>`: `python3 -c "import os; print(os.cpu_count())"`. - **RAM** → `<ram_gb>`: macOS `sysctl -n hw.memsize`; Linux `grep MemTotal /proc/meminfo`. - **Accelerator** → `<accelerator>`/`<vram>`/`<gpu_count>`: `nvidia-smi --query-gpu=name,memory.total,count --format=csv` (NVIDIA); else macOS Apple GPU/MPS; else CPU-only.
| binding | meaning | default | how to infer | |---|---|---|---| | `<metric>` + `<metric_direction>` | scalar to optimize; min/maximize | — | ask; scan eval output for the reported metric | | `<run_cmd>` / `<entrypoint>` | command for one training run (the evaluator) | — | `pyproject.toml`/`.venv`/`uv`/README | | `<editable_files>` | the program being evolved (e.g. `model.py`, `config.yaml`); never the harness or data | — | ask explicitly — this is the code that gets mutated; do not default it (multi-select on Claude Code) | | `<sandbox_root>` | where `lae/` is created | `./sandbox` | — | | `<gate>` + `<budget>` | one full run's size: `time`/`epochs` + amount; the FIXED eval budget applied to every program | — | identify the duration key now (e.g. `train.epochs`) so the controller can override it | | `<total_budget>` | total compute = number of full training runs (or wall-clock minutes); the single cost dial | — | ask | | `<concurrency>` | parallel evaluations `C` | derived from the probe | CPU-only → `max(1, <cores>//4)`; single GPU/MPS → `1` (ask if more fit `<vram>`); multi-GPU → `<gpu_count>` (pin one child/GPU) |
`num_generations` is **derived**: `ceil(<total_budget> / <concurrency>)`. The cascade is **derived** from `<budget>` (not asked): smoke = ~1 epoch / a small subset, full = `<budget>`, gate = child's smoke `<metric>` ≥ parent's smoke. `<budget>`/`<metric>`/eval split are FIXED — never mutation targets (a child may not "train longer" to look better); changing them means re-running the whole loop.
**Advanced (opt-in).** Ask one yes/no: "Use defaults for the evolutionary settings, or customize?" Defaults are faithful to AlphaEvolve/OpenEvolve — use them and ask nothing more. Only on "customize" ask for each (showing the default as recommended): `num_islands` (4), `num_top` (3), `num_diverse` (2), `num_bins` (10), `migration_interval` (5), `diversity_reference_size` (10), `pop_per_island` (40), `seed` (42). Axes are fixed: complexity × diversity. See `examples/run.example.yaml` for the shape.
Print the resolved bindings + the probe + derived `num_generations`, and **do not create files or launch until the user confirms**. Then initialise the sandbox (header rows only; `programs/` is created as children are evaluated): ``` <sandbox_root>/lae/ ├── archive.tsv ← current elites = program database + checkpoint ├── history.tsv ← append-only record of every child ├── leaderboard.md ← rendered UI └── programs/ ← one self-contained dir per program ```
## The controller (loop)
You maintain `num_islands` MAP-Elites maps in `archive.tsv`, the append-only `history.tsv`, running per-axis percentile stats, and `leaderboard.md`. **You are the sole writer of all shared logs** — Mutators only return results, so there are no write races. Copy this checklist and tick items off:
- [ ] Setup done: probe recorded, bindings confirmed, sandbox initialised, `num_generations` derived. - [ ] GEN 0 — in each island, create the baseline program (a copy of `<editable_files>`) + optionally a few stochastic variants; cascade-evaluate; place in the archive. - [ ] Per generation: build EXACTLY `<concurrency>` tasks (round-robin island, seeded-rule parent, top `num_top` + `num_diverse` most-diverse inspirations); make each child dir by **copying** the parent program + harness. - [ ] Run the `C` Mutators (spawn-or-degrade), each with `roles/Mutator.md`, parent code, inspirations, parent artifacts, its child dir, and the smoke/full budgets. - [ ] For each returned child: append a `history.tsv` row; if `evaluated`, compute its niche → cell and place it in the island map iff `<metric>` is better (`kept=y`); record `smoke_dropped`/`crash` without placing. - [ ] Re-render `leaderboard.md`; checkpoint (`archive.tsv` is the checkpoint); print a status line. - [ ] Every `migration_interval` generations: ring-migrate top elites island k → k+1. - [ ] Stop at `<total_budget>` (reserve a little for synthesis), then synthesize the final report.
**Niche computation (you do this, from a child's sandbox):** - **`complexity`** = trainable param count (fallback: total LOC of the editable files **+ any files the child added**), **log10-scaled**. - **`diversity`** = average normalized edit distance of the program's concatenated code (editable + added files) to a random sample of `diversity_reference_size` programs from its island (vs the baseline if the island is near-empty). Higher = more novel. - Normalize each axis with **running ~5th/95th percentiles** (not raw min/max, so one outlier can't collapse the range): `scaled = clamp01((v − p5)/(p95 − p5))`; `bin = min(num_bins−1, int(scaled × num_bins))`; `cell = (complexity_bin, diversity_bin)`. **Re-bin** existing elites when a percentile shifts enough to move an edge (keep the higher `<metric>` on collisions; the archive is small).
**The Mutator's prompt (the sampler):** parent code + inspirations + the parent's rendered artifacts (`<metric>`, per-class accuracy, loss curve, stderr) + the instruction to return one SEARCH/REPLACE diff. Single harness model — no LLM ensemble. The Mutator applies its diff in the child dir, cascade-evaluates at the FIXED `<budget>` (the controller injects/caps the duration key on the run command), and returns a result validated against `schemas/result.schema.json`: ```json {"child_id": "g3-i1-a2", "parent_id": "g1-i1-a0", "approach_summary": "add BatchNorm after conv2", "sandbox_path": "<sandbox_root>/lae/programs/g3-i1-a2", "status": "evaluated", "smoke_metric": 0.61, "metric": 0.71} ``` `status` ∈ {`evaluated`, `smoke_dropped`, `crash`}; `metric` is null unless `evaluated`. Mutators compute nothing about the archive — the controller derives every niche from the sandbox.
**Program sandboxes.** A parallel population doesn't map onto branches, so every program is a self-contained, fully-runnable dir `<sandbox_root>/lae/programs/<child_id>/`; the archive references it by id. Build each child dir by **copying real files** (the parent's `<editable_files>`, then apply the diff, **plus the harness/entrypoint code it imports**) and evaluate from inside it (`cd <child_dir> && <entrypoint>`). **Symlink only large read-only data**, never the entrypoint or any imported `.py`: Python resolves a symlinked script's `__file__` to the link target, so `sys.path[0]` becomes the original dir and the child's `model.py`/`dataset.py` are silently shadowed by the baselines — every architecture/data mutation becomes a no-op (tell-tale: identical loss curves across different "architectures"). **Isolation sanity gate:** the harness logs the param count / a code fingerprint; flag any child whose code changed but whose metric/loss curve is identical to its parent's (shadowed), and fix the sandbox before placing it. The repo working tree is never mutated.
**Final synthesis.** Report the global-best program + its `lae/programs/<id>/` path, the illuminated complexity×diversity map (coverage + who won each region), per-island bests, and 2–3 notably diverse runners-up.
## Ledger
All three logs live under `<sandbox_root>/lae/`, tab-separated, never commas in free text. The controller is the sole writer; resume from `archive.tsv` + `history.tsv` if interrupted.
**`archive.tsv`** — current elites + checkpoint. Header `island cell metric child_id parent_id sandbox_path complexity diversity`: ``` island cell metric child_id parent_id sandbox_path complexity diversity 0 (2,7) 0.7100 g4-i0-a1 g2-i0-a3 lae/programs/g4-i0-a1 2.1M 0.71 ``` **`history.tsv`** — every child, append-only. Header `gen island parent_id child_id smoke_metric full_metric status kept cell`: ``` gen island parent_id child_id smoke_metric full_metric status kept cell 4 0 g2-i0-a3 g4-i0-a1 0.61 0.71 evaluated y (2,7) 4 1 g2-i1-a0 g4-i1-a2 0.40 - smoke_dropped n - ``` **`leaderboard.md`** — re-rendered each generation: global best + per-island coverage + the archive ranked by `<metric>`. Report the **best** program at stop (not the last), the archive coverage, and a few diverse runners-up. Leave `lae/` untracked.
## Constraints
- A child works **only inside its own `lae/programs/<child_id>/` dir** — it may edit the copied `<editable_files>` and create new files there, but never modify any file outside it (the repo, the read-only harness, the data, other programs' dirs are g
Source provenance
Decision snapshot
recent repository activity
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for alpha-evolve, ready for a manual X post.
alpha-evolve: Use when the user wants to evolve an ML model/program through population-based search rather... 163 stars https://www.openagentskill.com/skills/gaasher-alpha-evolve?ref=x
Listing + install path for alpha-evolve: https://www.openagentskill.com/skills/gaasher-alpha-evolve?ref=x Install: npx skills add gaasher/Agent-Loop-Skills --skill alpha-evolve
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to gaasher but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/gaasher-alpha-evolve?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/gaasher-alpha-evolve?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/gaasher-alpha-evolve/audit)
[](https://www.openagentskill.com/skills/gaasher-alpha-evolve?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)gaasher
@gaasher
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Sandbox only
mono-color
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for 单色海报、双色印刷、单色调视觉、蓝色/绿色孔版印刷、risograph、网点照片、复古或当代编辑排版、zine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
1.9K StarsLast30days Skill
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
61.0K StarsAcademic Research Skills
Academic Research Skills for Claude Code: research → write → review → revise → finalize
38.4K StarsGPT Researcher
Run autonomous deep research over web and local sources
28.0K StarsSandbox only
Install targets
Codex install prompt
Install the "alpha-evolve" agent skill from https://github.com/gaasher/Agent-Loop-Skills/tree/main/loops/alpha-evolve. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Use when the user wants to evolve an ML model/program through population-based search rather than a single sequential refine loop — a generational evolution where parallel proposers each apply one small SEARCH/REPLACE diff to a parent, scored by a cascade-evaluated training run, and children are kept in a MAP-Elites archive across islands (with migration + checkpointing) so diverse high performers survive. A finite, bounded-parallelism re-creation of AlphaEvolve/OpenEvolve, bent for ML autoresearch. Runs to a fixed compute budget or until interrupted. Not for the sequential single-thread autoresearch loops (one change → measure → keep/revert), and not for verifying a known bug or external claim — this is parallel, diversity-preserving search over a program. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"gaasher-alpha-evolve","task":"Install alpha-evolve","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
Research agents
I need my agent to research a topic, compare sources, and produce a concise report.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add gaasher/Agent-Loop-Skills --skill alpha-evolve
Maintenance
active
2mo since push
Risk
Needs review
Permission surface may require sandboxing
GitHub quality
163
63/100 Quality · 77/100 Trust
Coverage tags
Review notes
Permission surface may require sandboxing · Financial research output is not financial advice; require human review before any live investment decision
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
PromisingUseful candidate, but compare it with alternatives before adopting.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
163 GitHub stars
Repo activity
163 stars, 19 forks
Maintenance
2mo since push
License
MIT
Install
npx skills add gaasher/Agent-Loop-Skills --skill alpha-evolve
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add gaasher/Agent-Loop-Skills --skill alpha-evolveDo not use when
Alternative
1.9K Stars
npx skills add yanliudesign/mono-color-skill --skill mono-color
Alternative
61.0K Stars
npx skills add mvanhorn/last30days-skill -g
Alternative
38.4K Stars
npx skills add Imbad0202/academic-research-skills
Alternative
28.0K Stars
npx skills add assafelovic/gpt-researcher
Agent safety v2
Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
Test manually in an isolated workspace and compare against safer alternatives.
high
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
medium
Skill may inspect schemas, query databases, or work with persistent stores.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20alpha-evolve%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20alpha-evolve%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/gaasher-alpha-evolve/install
Agent should check
Copy prompt
Task: Use alpha-evolve in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20alpha-evolve%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/gaasher-alpha-evolve/install
Install command: npx skills add gaasher/Agent-Loop-Skills --skill alpha-evolve
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/gaasher-alpha-evolve/install
LLM text format
/api/skills/gaasher-alpha-evolve/install?format=text
Find alternatives
/api/skills/search?q=alpha-evolve&limit=3
Agent prompt
Use alpha-evolve for this task. Review https://www.openagentskill.com/api/skills/gaasher-alpha-evolve/install, then install with: npx skills add gaasher/Agent-Loop-Skills --skill alpha-evolveRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/gaasher-alpha-evolve
LLM text
/api/registry/manifest/gaasher-alpha-evolve?format=text
Install alias
/api/registry/install/gaasher-alpha-evolve
Recommend
/api/registry/recommend?task=Use%20alpha-evolve%20in%20an%20agent%20workflow&limit=3
Agent fit
Research agents
Use-case tags
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Prototype with this skill first; keep a fallback candidate ready.
Role in stack
Fallback candidate
Primary fit
Research agents
Trust label
Prototype first
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
INFO163 GitHub stars
Stars/forks activity
CHECK163 stars, 19 forks; issue activity unavailable in current metadata
Recent maintenance
PASS2mo since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Useful candidate, but compare it with alternatives before adopting.
Workflow fit
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Work with data stores
I need my agent to inspect database schemas, write SQL, and explain query results.
Automate repeated work
I need my agent to automate a repeated workflow across tools and files.
Workflow fit
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Turn skills into distribution
A workflow for turning newly indexed skills into SEO briefs, social drafts, comparison pages, and reusable publishing workflows.
Inspect, patch, and verify code
A workflow for software agents that inspect repositories, review pull requests, generate tests, and turn findings into shippable patches.
Alternative shortlist
Similar skills that may fit this task.
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for 单色海报、双色印刷、单色调视觉、蓝色/绿色孔版印刷、risograph、网点照片、复古或当代编辑排版、zine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
Academic Research Skills for Claude Code: research → write → review → revise → finalize
Run autonomous deep research over web and local sources
--- name: alpha-evolve description: > Use when the user wants to evolve an ML model/program through population-based search rather than a single sequential refine loop — a generational evolution where parallel proposers each apply one small SEARCH/REPLACE diff to a parent, scored by a cascade-evaluated training run, and children are kept in a MAP-Elites archive across islands (with migration + checkpointing) so diverse high performers survive. A finite, bounded-parallelism re-creation of AlphaEvolve/OpenEvolve, bent for ML autoresearch. Runs to a fixed compute budget or until interrupted. Not for the sequential single-thread autoresearch loops (one change → measure → keep/revert), and not for verifying a known bug or external claim — this is parallel, diversity-preserving search over a program. compatibility: Requires Python 3.9+ metadata: version: "0.1.0" ---
# Alpha-Evolve
> Reference (read if you need the algorithm's details): AlphaEvolve — https://arxiv.org/abs/2506.13131 · > OpenEvolve (open-source impl) — https://github.com/algorithmicsuperintelligence/openevolve
A **population-based evolutionary** loop over a program. The artifact is the editable model code; a **child** is one analysis-informed **SEARCH/REPLACE diff** to a parent, and the feedback signal is a **cascade-evaluated training run** (`<metric>`, smoke→full). Children are placed in a **MAP-Elites archive across islands** (complexity × diversity axes), so a child survives by being either better or more novel, not just better. The discipline this enforces: **diversity is preserved, not collapsed** — diverse high performers co-exist instead of one local optimum winning. You are the controller: sample a parent + inspirations, spawn parallel Mutators to propose and evaluate children, place them, migrate between islands, checkpoint. Loops to a fixed compute budget or until interrupted.
## When to use
Use this for parallel, diversity-preserving search over a model/program where many variants explore at once and the archive keeps the illuminated frontier. Default to broad island coverage; if quality stalls, bias selection toward exploiting top elites; if coverage stalls, bias toward empty cells. Not for the sequential autoresearch loops (one change at a time), and not for fixing a known anomaly.
The cast (both in this folder): `roles/Mutator.md` produces + cascade-evaluates one child (the generation step); `schemas/result.schema.json` is the result a Mutator returns.
## Setup
Resolve bindings interactively. If `loop.run.yaml` exists in the working dir, load it, confirm the values in one line, and skip to the loop. Otherwise: on Claude Code (the `AskUserQuestion` tool is available, `<host>` = `claude-code`) infer a likely value for each binding and present it as the recommended option; on other hosts (`<host>` = `other`) ask each as a quoted plain-text prompt. Then write `loop.run.yaml` (format: `examples/run.example.yaml`) and confirm the values before creating any other files. `<host>` also decides execution: Claude Code spawns real `Agent` Mutators in parallel (capped at `<concurrency>`); other hosts degrade to running a generation's children serially (identical algorithm).
**Probe the box first (mandatory — measure, never assume `<concurrency>`).** Record and report: - **CPU cores** → `<cores>`: `python3 -c "import os; print(os.cpu_count())"`. - **RAM** → `<ram_gb>`: macOS `sysctl -n hw.memsize`; Linux `grep MemTotal /proc/meminfo`. - **Accelerator** → `<accelerator>`/`<vram>`/`<gpu_count>`: `nvidia-smi --query-gpu=name,memory.total,count --format=csv` (NVIDIA); else macOS Apple GPU/MPS; else CPU-only.
| binding | meaning | default | how to infer | |---|---|---|---| | `<metric>` + `<metric_direction>` | scalar to optimize; min/maximize | — | ask; scan eval output for the reported metric | | `<run_cmd>` / `<entrypoint>` | command for one training run (the evaluator) | — | `pyproject.toml`/`.venv`/`uv`/README | | `<editable_files>` | the program being evolved (e.g. `model.py`, `config.yaml`); never the harness or data | — | ask explicitly — this is the code that gets mutated; do not default it (multi-select on Claude Code) | | `<sandbox_root>` | where `lae/` is created | `./sandbox` | — | | `<gate>` + `<budget>` | one full run's size: `time`/`epochs` + amount; the FIXED eval budget applied to every program | — | identify the duration key now (e.g. `train.epochs`) so the controller can override it | | `<total_budget>` | total compute = number of full training runs (or wall-clock minutes); the single cost dial | — | ask | | `<concurrency>` | parallel evaluations `C` | derived from the probe | CPU-only → `max(1, <cores>//4)`; single GPU/MPS → `1` (ask if more fit `<vram>`); multi-GPU → `<gpu_count>` (pin one child/GPU) |
`num_generations` is **derived**: `ceil(<total_budget> / <concurrency>)`. The cascade is **derived** from `<budget>` (not asked): smoke = ~1 epoch / a small subset, full = `<budget>`, gate = child's smoke `<metric>` ≥ parent's smoke. `<budget>`/`<metric>`/eval split are FIXED — never mutation targets (a child may not "train longer" to look better); changing them means re-running the whole loop.
**Advanced (opt-in).** Ask one yes/no: "Use defaults for the evolutionary settings, or customize?" Defaults are faithful to AlphaEvolve/OpenEvolve — use them and ask nothing more. Only on "customize" ask for each (showing the default as recommended): `num_islands` (4), `num_top` (3), `num_diverse` (2), `num_bins` (10), `migration_interval` (5), `diversity_reference_size` (10), `pop_per_island` (40), `seed` (42). Axes are fixed: complexity × diversity. See `examples/run.example.yaml` for the shape.
Print the resolved bindings + the probe + derived `num_generations`, and **do not create files or launch until the user confirms**. Then initialise the sandbox (header rows only; `programs/` is created as children are evaluated): ``` <sandbox_root>/lae/ ├── archive.tsv ← current elites = program database + checkpoint ├── history.tsv ← append-only record of every child ├── leaderboard.md ← rendered UI └── programs/ ← one self-contained dir per program ```
## The controller (loop)
You maintain `num_islands` MAP-Elites maps in `archive.tsv`, the append-only `history.tsv`, running per-axis percentile stats, and `leaderboard.md`. **You are the sole writer of all shared logs** — Mutators only return results, so there are no write races. Copy this checklist and tick items off:
- [ ] Setup done: probe recorded, bindings confirmed, sandbox initialised, `num_generations` derived. - [ ] GEN 0 — in each island, create the baseline program (a copy of `<editable_files>`) + optionally a few stochastic variants; cascade-evaluate; place in the archive. - [ ] Per generation: build EXACTLY `<concurrency>` tasks (round-robin island, seeded-rule parent, top `num_top` + `num_diverse` most-diverse inspirations); make each child dir by **copying** the parent program + harness. - [ ] Run the `C` Mutators (spawn-or-degrade), each with `roles/Mutator.md`, parent code, inspirations, parent artifacts, its child dir, and the smoke/full budgets. - [ ] For each returned child: append a `history.tsv` row; if `evaluated`, compute its niche → cell and place it in the island map iff `<metric>` is better (`kept=y`); record `smoke_dropped`/`crash` without placing. - [ ] Re-render `leaderboard.md`; checkpoint (`archive.tsv` is the checkpoint); print a status line. - [ ] Every `migration_interval` generations: ring-migrate top elites island k → k+1. - [ ] Stop at `<total_budget>` (reserve a little for synthesis), then synthesize the final report.
**Niche computation (you do this, from a child's sandbox):** - **`complexity`** = trainable param count (fallback: total LOC of the editable files **+ any files the child added**), **log10-scaled**. - **`diversity`** = average normalized edit distance of the program's concatenated code (editable + added files) to a random sample of `diversity_reference_size` programs from its island (vs the baseline if the island is near-empty). Higher = more novel. - Normalize each axis with **running ~5th/95th percentiles** (not raw min/max, so one outlier can't collapse the range): `scaled = clamp01((v − p5)/(p95 − p5))`; `bin = min(num_bins−1, int(scaled × num_bins))`; `cell = (complexity_bin, diversity_bin)`. **Re-bin** existing elites when a percentile shifts enough to move an edge (keep the higher `<metric>` on collisions; the archive is small).
**The Mutator's prompt (the sampler):** parent code + inspirations + the parent's rendered artifacts (`<metric>`, per-class accuracy, loss curve, stderr) + the instruction to return one SEARCH/REPLACE diff. Single harness model — no LLM ensemble. The Mutator applies its diff in the child dir, cascade-evaluates at the FIXED `<budget>` (the controller injects/caps the duration key on the run command), and returns a result validated against `schemas/result.schema.json`: ```json {"child_id": "g3-i1-a2", "parent_id": "g1-i1-a0", "approach_summary": "add BatchNorm after conv2", "sandbox_path": "<sandbox_root>/lae/programs/g3-i1-a2", "status": "evaluated", "smoke_metric": 0.61, "metric": 0.71} ``` `status` ∈ {`evaluated`, `smoke_dropped`, `crash`}; `metric` is null unless `evaluated`. Mutators compute nothing about the archive — the controller derives every niche from the sandbox.
**Program sandboxes.** A parallel population doesn't map onto branches, so every program is a self-contained, fully-runnable dir `<sandbox_root>/lae/programs/<child_id>/`; the archive references it by id. Build each child dir by **copying real files** (the parent's `<editable_files>`, then apply the diff, **plus the harness/entrypoint code it imports**) and evaluate from inside it (`cd <child_dir> && <entrypoint>`). **Symlink only large read-only data**, never the entrypoint or any imported `.py`: Python resolves a symlinked script's `__file__` to the link target, so `sys.path[0]` becomes the original dir and the child's `model.py`/`dataset.py` are silently shadowed by the baselines — every architecture/data mutation becomes a no-op (tell-tale: identical loss curves across different "architectures"). **Isolation sanity gate:** the harness logs the param count / a code fingerprint; flag any child whose code changed but whose metric/loss curve is identical to its parent's (shadowed), and fix the sandbox before placing it. The repo working tree is never mutated.
**Final synthesis.** Report the global-best program + its `lae/programs/<id>/` path, the illuminated complexity×diversity map (coverage + who won each region), per-island bests, and 2–3 notably diverse runners-up.
## Ledger
All three logs live under `<sandbox_root>/lae/`, tab-separated, never commas in free text. The controller is the sole writer; resume from `archive.tsv` + `history.tsv` if interrupted.
**`archive.tsv`** — current elites + checkpoint. Header `island cell metric child_id parent_id sandbox_path complexity diversity`: ``` island cell metric child_id parent_id sandbox_path complexity diversity 0 (2,7) 0.7100 g4-i0-a1 g2-i0-a3 lae/programs/g4-i0-a1 2.1M 0.71 ``` **`history.tsv`** — every child, append-only. Header `gen island parent_id child_id smoke_metric full_metric status kept cell`: ``` gen island parent_id child_id smoke_metric full_metric status kept cell 4 0 g2-i0-a3 g4-i0-a1 0.61 0.71 evaluated y (2,7) 4 1 g2-i1-a0 g4-i1-a2 0.40 - smoke_dropped n - ``` **`leaderboard.md`** — re-rendered each generation: global best + per-island coverage + the archive ranked by `<metric>`. Report the **best** program at stop (not the last), the archive coverage, and a few diverse runners-up. Leave `lae/` untracked.
## Constraints
- A child works **only inside its own `lae/programs/<child_id>/` dir** — it may edit the copied `<editable_files>` and create new files there, but never modify any file outside it (the repo, the read-only harness, the data, other programs' dirs are g
Source provenance
Decision snapshot
recent repository activity
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for alpha-evolve, ready for a manual X post.
alpha-evolve: Use when the user wants to evolve an ML model/program through population-based search rather... 163 stars https://www.openagentskill.com/skills/gaasher-alpha-evolve?ref=x
Listing + install path for alpha-evolve: https://www.openagentskill.com/skills/gaasher-alpha-evolve?ref=x Install: npx skills add gaasher/Agent-Loop-Skills --skill alpha-evolve
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to gaasher but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/gaasher-alpha-evolve?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/gaasher-alpha-evolve?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/gaasher-alpha-evolve/audit)
[](https://www.openagentskill.com/skills/gaasher-alpha-evolve?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)gaasher
@gaasher
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Sandbox only
mono-color
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for 单色海报、双色印刷、单色调视觉、蓝色/绿色孔版印刷、risograph、网点照片、复古或当代编辑排版、zine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
1.9K StarsLast30days Skill
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
61.0K StarsAcademic Research Skills
Academic Research Skills for Claude Code: research → write → review → revise → finalize
38.4K StarsGPT Researcher
Run autonomous deep research over web and local sources
28.0K StarsPermission surface
shell or command execution, filesystem or document access
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
shell or command execution, filesystem or document access
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
shell or command execution, filesystem or document access
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
shell or command execution, filesystem or document access
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness