metalmind

Use when the user asks for brief, terse, fragment-style responses — phrases like 'be brief', 'less filler', 'no fluff', 'short answer', 'marsh', 'marsh mode', 'inquisitor mode'. Also invoke when the conversation drifts back to verbose prose mid-session and the active output style is `marsh` (check `outputStyle` in ~/.claude/settings.json). Re-anchors the Marsh / Era-1 Inquisitor persona so it survives compaction and task pressure.

Use when the user asks for brief, low-filler responses without the Marsh / Inquisitor persona — phrases like 'be brief', 'short answer', 'no preamble', 'telegraph', 'telegraph mode', 'terse mode'. Also invoke when the active output style is `telegraph` (check `outputStyle` in ~/.claude/settings.json) and a long-running session has drifted back to verbose prose. Re-anchors the Telegraph operator persona so it survives compaction and task pressure.

Use when creating or editing markdown notes in a metalmind vault — any time the user says 'save this', 'note that', 'add to the vault', updates an existing note, or pipes a body through `metalmind scribe create|update|patch`. Covers Obsidian Flavored Markdown (wikilinks, embeds, callouts, tags, block refs, highlights, tasks) as the supported syntax dialect and metalmind conventions; scribe stamps frontmatter, plain-stem wikilinks (no `kind:` prefix), folder-by-intent not by project, link new notes from their MOC. Invoke before writing any note body, even if the user's request is one sentence.

Recall prior decisions, architecture notes, and context from the metalmind knowledge vault. Use before any non-trivial task — architecture, design, debugging, planning — to check what was already decided. Do not use for trivial one-line edits or pure syntax lookups.

Use when the user says "save this", "note that", "add to the vault", or wants to persist a session insight to their vault. Decides folder (Plans/Learnings/Work/Personal/Memory/Daily), proposes path + content, writes via `metalmind scribe create|update|patch`. NEVER write directly with the file-write tool — always go through metalmind scribe.

Use when the user says "save this", "note that", "add to the vault", or wants to persist a session insight to their vault. Decides folder (Plans/Learnings/Work/Personal/Memory/Daily), proposes path + content, writes via `metalmind scribe create|update|patch`. NEVER write directly with the file-write tool — always go through metalmind scribe.

Full operational reference for the metalmind CLI — vault recall, note CRUD, daily notes, forge, archive, and notifications. Use when writing vault notes, managing daily action items, running forge commands, archiving notes, or when you need metalmind command flags and gotchas beyond the basic recall pattern in CLAUDE.md. Also use when the user mentions 'scribe', 'atium', 'forge', 'gold', 'flare', or asks about vault note conventions.

Convene a 7-persona deliberative council on substantive engineering and strategic decisions — architecture choices, technology bets, large refactors, build-vs-buy, team/process changes, hiring — plus non-engineering calls (career, business, life). Outputs a verdict with confidence %, 3 critical risks, 5 next steps, and a minority report. Use whenever getting the decision wrong costs weeks or more. Trigger phrases: 'convene the synod/council/crew', 'should we [migrate/rewrite/adopt/split]', 'should I [quit/move/take this offer]', 'stress-test [this decision/plan]', 'help me decide between [paths]', 'review my [strategy/architecture]'. Do NOT convene for tactical work: single PR review (yield to code-review), one bug (yield to team-debug), 2-3 shortlisted libraries (yield to ai-dev-tool-analyzer), in-flight implementation (yield to brainstorming). Synod is for questions that affect the next 6 months, not the next 60 minutes.

Spawning, coordinating, and debugging multi-agent teams. MUST be invoked BEFORE any TeamCreate call, BEFORE invoking /team-feature, /team-debug, /team-pr-review, /team-multi-repo-audit, or any other team-* skill, and AS SOON AS a teammate idle_notification arrives without readable message content. Also invoke when the user mentions 'team', 'spawn agents', 'agents in parallel', 'team_name', 'split-screen agents', 'iTerm panes for agents', when troubleshooting a stuck/silent teammate, when planning to TeamDelete a team, or when explaining the team-feature flow to the user. Covers the team_name+name spawn discipline, the idle≠silence rule, the SendMessage-vs-text rule, the TaskList-as-canonical-handoff rule, the architect-first spawn order, and the lifecycle/manual-nuke override. Use this skill anytime any aspect of multi-agent coordination touches the conversation.