菜单
Compose an arena + gate + season into one GameWorld — a whole simulation/economy that is itself a Link, so worlds nest inside worlds. Use for 'a world of agents', simulations, economies, agents that craft/compete/evolve. `GameWorld`.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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()`.
| name | cave-world |
| description | Compose an arena + gate + season into one GameWorld — a whole simulation/economy that is itself a Link, so worlds nest inside worlds. Use for 'a world of agents', simulations, economies, agents that craft/compete/evolve. `GameWorld`. |
GameWorld composes the arena, the gate, and the season into one object — and it's a Link, so a world can be a player inside a bigger world (world_as_agent). Instantiate, subclass, or build from a small spec.
from cave_teams import GameWorld, world_as_agent
w = GameWorld.from_spec({"rounds": 3, "seasons": 2, "reset_to": "board"}, agents, mutator, deity=deity)
inner = world_as_agent(w, derive_action) # a whole world plays as ONE agent in a bigger world
mutator is a required Python callable — register_fn it and reference the name in the spec.
{"op": "world",
"spec": {"rounds": 3, "seasons": 2, "reset_to": "board"},
"agents": {"a": <spec>}, "mutator": "my_mutator", "deity": <spec>}
// mutator referenced by name (register_fn)
If the spec is malformed, cave() returns {"status": "construction_error", "hint": "read the cave-world skill"} — the error names this skill.
cave-blackboard · cave-season · cave-sim
Part of the cave-teams plugin — the language + full DSL is the cave-teams skill; drive any pattern from data with the cave skill.