菜单
Capture methodology friction, process corrections, and operational learnings for the SWARM vault. Rule Zero — methodology notes are the spec; when something goes wrong, write it down so the system learns. Triggers on "/remember", "capture friction", "log this correction", "the system did X wrong".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Find connections between claims and update topic maps. Requires semantic judgment to identify genuine evidence relationships. Use after /extract creates claims, when exploring connections, or when a topic map needs synthesis. Triggers on "/cross-link", "/cross-link [claim]", "find connections", "update topic maps", "connect these claims".
Extract structured claims from SWARM experiment runs, sweep results, and red-team reports. Comprehensive extraction is the default — every governance finding, adversarial pattern, and parameter sensitivity result gets extracted. Zero extraction from a domain-relevant run is a BUG. Triggers on "/extract", "/extract [file]", "extract findings", "mine this run", "process this experiment".
Explore and analyze the SWARM knowledge graph — detect orphan claims, find dense connection clusters, trace evidence chains, identify synthesis opportunities. Triggers on "/graph", "graph analysis", "find orphans", "what connects to X".
Research a topic relevant to SWARM AI safety and grow the vault with findings. Queries external sources, synthesizes into claim candidates, follows the extraction pipeline. Triggers on "/learn", "/learn [topic]", "research this", "find papers on".
Surface the next highest-priority action from the SWARM synthesis pipeline queue and maintenance conditions. Recommends what to work on based on queue state, pending observations, stale claims, and research threads. Triggers on "/next", "what should I work on", "next action", "what's pending".
Run the full SWARM synthesis pipeline on one or more experiment runs — seed, extract, cross-link, update, validate in sequence. Triggers on "/pipeline", "/pipeline [run-folder]", "full pipeline", "process everything".
| name | remember |
| description | Capture methodology friction, process corrections, and operational learnings for the SWARM vault. Rule Zero — methodology notes are the spec; when something goes wrong, write it down so the system learns. Triggers on "/remember", "capture friction", "log this correction", "the system did X wrong". |
| user-invocable | true |
| allowed-tools | Read, Write, Glob |
| context | fork |
Target: $ARGUMENTS
Capture operational friction so the SWARM vault learns from experience.
vault/ops/methodology/ is the canonical specification of how this system operates. When behavior diverges from methodology, or when methodology should change, write it down here. /rethink reviews these notes. /arscontexta:architect reasons about patterns. Together they prevent drift.
Create in vault/ops/observations/:
---
description: [one sentence: what happened]
category: methodology | process | friction | surprise | quality
observed: YYYY-MM-DD
status: pending
---
# [prose-as-title: what the system did or failed to do]
[Body: what happened, what should have happened, what the gap is]
---
Topics:
- [[methodology]]
Create in vault/ops/tensions/:
---
description: [one sentence: what contradicts what]
observed: YYYY-MM-DD
involves:
- "[[claim A]]"
- "[[claim B]]"
status: pending
---
# [prose-as-title: the conflict]
[Body: what evidence supports each side, why this is unresolved]
---
Topics:
- [[methodology]]
After capturing, the note will be picked up by /rethink when observation count reaches threshold (currently 10).