菜单
The capsule verb, invoked explicitly — reconcile from the live memory, write a resume-ready capsule, then stop. Mid-session checkpoint or completion capsule; a rolling best-effort version of the same write also runs automatically on every Stop event via daemons/stop-capsule-writer.mjs.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
The resume verb, invoked explicitly — load the newest valid capsule by created_at, re-ground against live memory, then ACT on waiting_on. Mid-session or on explicit ask; the post-clear boot fires the same procedure automatically via daemons/resume-verb.mjs.
Run the volunteering ledger before declaring work done. Forces surfacing of what changed/didn't, what was noticed-but-not-fixed, what was guessed, and what tradeoffs were made on the principal's behalf. The standard - the principal should never be surprised later by something the agent knew at the time.
Capture a confident agent claim (Phase 1) or resolve one as right/wrong (Phase 2) in vault/memory/TRUST_DECAY.md. Builds the longitudinal record of agent calibration over time. Pairs with /honesty-check (which should reduce Phase 1 frequency) and /diagnose (which surfaces causes that often reveal Phase 2 events).
One evidence-gated pass that sequences /dream, /reconcile, /sweep-now, and /digest over your own vault, with a /system-check gate and a ledger-review pass over the measurement layer (Honesty Ledger, Trust Decay, Failure Modes). Stays exactly as human-gated as the legs it calls -- stages, never auto-applies. Skips a leg gracefully when there is nothing to do; every leg that runs leaves an evidence line.
Dispatch Hestia to run all 3 vault sweeps (DELEGATION_TRACKER stale items, HEAT_INDEX dormant flips, broken wikilinks) and append the result to HESTIA_SWEEP_LOG.
Route ONE bounded, mechanical task to the Codex CLI as a non-Claude executor, under the same review-before-merge gate as any other agent-produced diff. Use when the user explicitly asks to hand a task to Codex, or names OpenAI Codex / a non-Claude executor for a mechanical change (rename a symbol across files, add a config entry, apply a scripted find/replace). Not for open-ended or strategic work -- that stays with the operating Claude session.
| name | context-capsule |
| description | The capsule verb, invoked explicitly — reconcile from the live memory, write a resume-ready capsule, then stop. Mid-session checkpoint or completion capsule; a rolling best-effort version of the same write also runs automatically on every Stop event via daemons/stop-capsule-writer.mjs. |
| trigger | /context-capsule |
| status | Two-verb lifecycle — supersedes the v1 capsule skill and absorbs /close (there is no separate close ceremony). |
| related | ["docs/two-verb-lifecycle.md (design doc — schema, content gate, sovereignty rules)","daemons/capsule-verb.mjs (validateCapsuleText — required fields + content gate)","daemons/capsule-content-gate.mjs (content gate; shared with the stop-writer)","skills/resume/SKILL.md (the mirror verb)"] |
The entire job: reconcile → write the capsule → sync the vault → STOP. The capsule absorbs /close: there is no separate close ceremony, and no separate stamping step — writing a valid capsule (content gate passes, required fields non-empty) is the capsule contract.
A rolling, best-effort version of this write already runs on every Stop event via daemons/stop-capsule-writer.mjs — you don't need this skill for ordinary turn-by-turn capture. Invoke /context-capsule for the explicit cases: a mid-session checkpoint before risky work, a completion capsule when a thread ships, or a handoff.
/clear passes through whether or not a capsule landed; never tell the operator to wait on capsule machinery.vault/memory/capsules/<YYYY-MM-DD>-<slug>.md:
# comments on them, waiting_on quoted (never bare null): id, objective, waiting_on, next_valid_action; plus parent_capsule_id, status: active, trigger, expires, tags, created_at. Stamp created_at with the real current date-time at this write, ISO-8601 with offset (e.g. 2026-07-25T11:12:04-07:00) — the selector parses this field, and a date-only stamp backdates the capsule to midnight UTC where it loses to every same-day autosave. resume_trigger and success_criteria are OPTIONAL — include them when they add real signal, omit otherwise.[REFERENCE ONLY] banner, then: Done (don't redo) · Historical-Errors → Resolutions · Historical-Rejected-Approaches · Files-Read / Files-Modified · Operating-Facts · Pending-Gates · Claimed-Rows. Historical- prefixes and latest-wins stay (anti-zombie).waiting_on is the resume contract: write it so a fresh session can act from it alone — concrete items, owners, gates.node daemons/vault-sync.mjs. It resolves the installed root from .aigent/state.json, stages only capsule/memory changes, and handles no-remote or push-failure outcomes without prompting or gating the lifecycle.daemons/capsule-content-gate.mjs) before writing — there is no separate trusted-writer pass to catch a mistake after the fact.active → resumed → resolved. The resume RUNTIME marks the capsule resumed mechanically at load (daemons/resume-verb.mjs via markCapsuleConsumed) — never edit a capsule's status by hand, and never expect the same capsule to be silently re-resumed on a later clear. A capsule superseded by a newer one, or resumed >30 days, resolves. /open//close are retired — resume absorbs open, this verb absorbs close.