Menu
End-of-day close. Synthesizes today's signals into one paragraph and up to three threads, runs Architect / Witness / Contrarian over the day, and captures the user's correction — tagged from the canonical taxonomy — to the vault.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Govern AI spend without surveilling your team — the AI-spend governance loop. Set OKRs, harden the right context (tray→slate), bounded agents surface a finding ready for ratification, ratify a policy to the provenance trail, get a spend-ROI report that cites its sources. The leader governs usage; the team's private context is never read.
The parallel per-agent swarm that beats cold-start. After install, each bounded agent reads its canonical source (git/claude-code → Analyst, granola → SDR, cross-stream → Auditor) in parallel and posts a candidate — the one fact, commitment, or risk worth acting on — before any deliberation. Read-only, LLM-optional. Run this to show the vault won't start empty.
Twelve-agent deliberation on the user's psychological state across four registers (Structural / Somatic / Temporal / Symbolic). Asks three forced-choice questions, runs all 12 agents via Opus 4.7 in parallel, surfaces their disagreement grouped by register, and writes the user's correction — tagged from the canonical taxonomy — to the local vault.
The 60-second taste of Liminal. Runs one bounded deliberation on a sample brief — three agents read the same brief and disagree, at least one refuses out of its lane, you correct one read, and the correction becomes the record. Ends by pointing at the desktop app so the vault outlives the session. Run this first.
Audit an existing Claude Code workspace for canon-substrate gaps — the failure mode where users build sophisticated agent stacks without a CORPUS_MAP / SCHEMA / decisions/ layer underneath, leaving every agent's "consult on demand" reference list resolving to nothing. Reports ship-blocking issues, fragile-but-working issues, and noise. Use when invited into someone's `.claude/agents/` directory to do an audit-and-recommend pass.
Materialize the canon-substrate foundation pack into a target workspace. Reads a diagnose-substrate JSON report + a small config file, copies the recommended template files into the target, substitutes high-frequency placeholders (PROJECT NAME, OWNER NAME, sensitivity tiers), and emits a landing prompt the user pastes into their Claude Code session to finish the customization. Pairs with diagnose-substrate — diagnose first, scaffold second. Step (b) of SPEC §14's productized Diagnostic + Foundation Pack pattern.
| name | close |
| description | End-of-day close. Synthesizes today's signals into one paragraph and up to three threads, runs Architect / Witness / Contrarian over the day, and captures the user's correction — tagged from the canonical taxonomy — to the vault. |
| disable-model-invocation | true |
| allowed-tools | Bash(node *) |
| argument-hint | [optional: surfacing_id from daemon notification] |
The substrate has been ingesting all day. /close reads today's signals and runs the bounded agents over the synthesis. The correction loop is the same as /check: they disagree, you correct one, the record grows.
If the user invoked /close from a daemon notification and $ARGUMENTS contains a surfacing_id, pass it along:
node ${CLAUDE_PLUGIN_ROOT}/skills/close/close.js --surfacing-id=<uuid>
Otherwise:
node ${CLAUDE_PLUGIN_ROOT}/skills/close/close.js
Returns JSON with vault_id, signal_count, signal_summary, up to three threads, and the three agent interpretations.
If vault_id is null and reason is no_signals_today, report that and stop.
Show the user:
signal_summary paragraph, verbatim.Then:
"Which reading is wrong, and why? Your correction enters the vault."
Map the user's reason to one of the nine canonical correction tags. See the /check skill for the full taxonomy: wrong_frame, wrong_intensity, wrong_theory, right_but_useless, right_but_already_known, too_generic, missed_compensation, assumes_facts_not_in_evidence, off_by_layer.
node ${CLAUDE_PLUGIN_ROOT}/skills/check/store-correction.js <vault_id> "<agent_name>" "<tag>" "<reason>"
Confirm and end the close.
too_generic against whichever agent they single out.