菜单
Take a request — a Linear issue or a feature description — all the way to a reviewed, ready PR: triage it, work out the right approach, propose it for a quick OK, implement, then ship. Use when the user wants the agent to plan and build something end to end.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Take a finished change from working diff to a ready-for-review PR, ending with the PR URL as plain text. Use when the user says "ship it" or wants to go from a working change to an opened PR.
Commit the current change, push a branch, and open a draft PR. Use when the user wants to open a PR for finished work.
How to drive the `ct` CLI to run matches and produce every number and graph a control experiment ships. Covers `ct run eval`, `ct run monitor`, `ct run summarize`, `ct game-metrics metrics / graph roc / graph pareto`, `ct traj`, and the viewers. Load this when you launch a match, compute safety or usefulness, regenerate a graph, or need the exact reproduce command for an output. White loads it always; main and others load it on demand.
The empirical-research method and quality bar for AI-control experiments run through the ct CLI. Reduce uncertainty fast, iterate on qualitative plus quantitative evidence, size for power, keep splits clean, report honestly, and hold P1 observability, P2 affordance discipline, and the per-team B/R/W/M criteria. Loaded by every role.
The public, LessWrong-style writeup of a control experiment. Ruthlessly compressed for a reader with zero context, leading with the surprise, citing public-viewer trajectory URLs only. Load this in the writing phase when producing the shipped post into `outputs/`. It lifts the STRONG-tagged claims from the internal [report-writing]; same evidence base, far less detail. Before shipping it runs the lw-review gate below.
The red (attacker) role for ONE protocol in an automated control-research run. Load this when you are spawned as red_<protocol>. Holds red's self-managed loop, guarded objective, iteration discipline, and validity rules. Every shared fact (folder layout, iteration mechanics, the stop gate, the game, safety formula, the quality bar, ct commands) lives in a general skill and is referenced here by name, never copied.
| name | deliver |
| description | Take a request — a Linear issue or a feature description — all the way to a reviewed, ready PR: triage it, work out the right approach, propose it for a quick OK, implement, then ship. Use when the user wants the agent to plan and build something end to end. |
From a request to a reviewed PR. Do the thinking yourself — work out the right approach and propose just that one; offer alternatives only when the choice is genuinely underdetermined. The user weighs in twice, lightly: on the proposal and on the finished work. Work in a git worktree if you're on a shared checkout — git worktree add a branch, then copy the repo-root .env into it and symlink the repo-root .settings/ so ct and environments resolve.
/ship.