メニュー
Reproduce a generation: copy each winner's whole agent directory into the next generation and wipe its session memory (children inherit structure, not history). Use for evolving agents/teams across generations. `evolve()`.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | cave-evolve |
| description | Reproduce a generation: copy each winner's whole agent directory into the next generation and wipe its session memory (children inherit structure, not history). Use for evolving agents/teams across generations. `evolve()`. |
The genetic operator over agent directories: evolve(winner_dirs, out_dir) copies each winner's whole AIOS dir into out_dir/{prefix}_{i} and removes its knowledge of previous sessions — the next generation, born advanced (the dir) but memory-free. Returns the child dirs.
from cave_teams import evolve, select_winners
children = evolve(winner_dirs, out_dir="gen2") # -> list of child dirs
Not a cave() build-op — evolve is a genetic filesystem operation (it returns child directories, not a Link). Call it directly. It pairs with cave-tournament (select winners) and cave-sim (run it over generations).
cave-tournament · cave-sim · cave-world
Part of the cave-teams plugin — the language + full DSL is the cave-teams skill; drive any pattern from data with the cave skill.
Drive the whole cave-teams library from one function, as DATA — build/run any team from a spec in any sequence, save a team to your proven library, reuse a proven team anywhere, and discover teams across projects. Use when you want to serialize a team, run a team from JSON/dict, save+reuse a proven team across repos ("golden"), or have a higher system / global app drive cave-teams. NOT how you normally program (use the cave-teams DSL for that). Triggers: "cave()", "metacontrol", "run from a spec", "team as data", "golden team", "reuse a proven team", "scan for .cave", "global cave".
Build and run programmable agent teams with cave-teams — the provider-agnostic version of Claude Code Teams. Use when the user wants to wire multiple agents together, run agents in sequence or parallel, build a multi-agent pipeline/workflow, make a "team" of coding agents (Claude Code, Codex, MiniMax, or any), loop an agent until a check passes, run a contest between agents, or compose agents with the >> / | DSL. Triggers: "agent team", "multi-agent", "orchestrate agents", "wire these agents", "run agents in parallel", "cave-teams", "agent pipeline", "agent workflow".
Program WHEN each agent may be messaged — conditions on messages, the GUARDRAILS of a leader-driven team run. Use to gate agents on runtime state: after these two respond, only when a flag holds, any predicate over the message log. THIS is what makes cave-teams programmable where Claude Code Teams' flow is fixed.
Run agents that craft, compete, and evolve over generations — the user buys the best, winners reproduce. A compiler (a domain → a trained agent) and a research lab (selection discovers what works) in one engine. `crafter_sim()`.
N agents read and write a shared state over rounds, with a mutator that folds each contribution in and an optional adjudicator (stigmergy arena). Use for agents collaborating on a shared board, a market, a workspace they all see. `blackboard()`.
Run different agents depending on a condition (guarded choice / router). Use for 'if X do this else that', routing, triage, picking a path by the state. `choice()` / `router()`.