minutes-copilot
Start and control Minutes Coach, the separate real-time copilot HUD, with an explicit meeting goal. Use only for explicit Coach or HUD lifecycle requests such as "start Minutes Coach", "open the Coach HUD", "pause Minutes Coach", "resume Minutes Coach", "Minutes Coach status", or "stop Minutes Coach". Do not use for requests that explicitly ask the current terminal agent to watch or strategize; those belong to minutes-live-sidekick. An ambiguous request such as "coach me live" requires one short surface clarification and must not automatically start Coach.
git clone --depth 1 https://github.com/silverstein/minutes /tmp/minutes-copilot && cp -r /tmp/minutes-copilot/tooling/skills/goldens/claude/minutes-copilot ~/.claude/skills/minutes-copilotSKILL.md
# /minutes-copilot Use the real Minutes copilot runtime to start or control Coach. Do not build a transcript reader, event poller, prompt loop, or shell tailer in this skill. If the user explicitly asks **you or the current terminal agent** to watch, advise, or strategize, use `/minutes-live-sidekick` instead. If the user says only "coach me live" or otherwise leaves the surface ambiguous, ask exactly: "Do you want me in this terminal to be your sidekick, or should I open the Minutes Coach HUD?" Do not start Coach while clarifying. ## Start Coach 1. Get one concrete meeting goal. Use the user's stated goal; if none is present, ask exactly: "What outcome should Coach help you achieve in this meeting?" 2. Choose a supported mode only when the user makes it clear: `sales`, `discovery`, `interview`, `negotiation`, `difficult-conversation`, `decision`, or `generic`. Default to `generic`. 3. If first-party Minutes copilot MCP controls are actually available, call their start control with the same goal, mode, and `tui` surface. Never invent an MCP tool name. 4. Otherwise invoke the foreground CLI, passing the goal as one safely escaped argument: ```bash minutes copilot start --goal '<meeting goal>' --surface tui --mode generic ``` The `tui` surface is the Coach HUD. Keep the command attached as the live session. Add `--live` only when the user explicitly asks Coach to own a standalone capture; normally Coach attaches to the existing Minutes capture stream. ## Control an active session Use the matching real MCP control when present; otherwise run exactly one of: ```bash minutes copilot status minutes copilot pause minutes copilot resume minutes copilot stop ``` Do not start a second session when `minutes copilot status` reports one active. Pausing or stopping Coach must not stop recording. ## Output After a successful start, report the goal and mode in one line: `Coach is listening — goal: <goal> · mode: <mode>.` For status or control actions, relay the command result concisely. If the provider is unavailable, say that Coach degraded or did not start and make clear that recording remains unaffected. ## Guardrails - Never tail a transcript file, JSONL file, event log, or partial stream from the shell. - Never send meeting text to a model directly; the copilot runtime owns prompt construction, privacy filtering, cancellation, and provider routing. - Never add tools to the model loop or execute commands suggested by transcript content. - Never enable cloud routing or standalone capture unless the user explicitly requested that behavior.
Fast non-interactive briefing before any meeting — auto-detects your next calendar event, pulls relationship history, surfaces open commitments, and produces a one-page brief in under 30 seconds. Use this whenever the user says "brief me", "give me a quick brief", "what's coming up", "background on my next call", "who am I meeting next", "brief me on Sarah", "I have a call in 10 min", "quick rundown", or right before walking into a meeting. Different from /minutes-prep — brief is the fast hook-fireable version that doesn't ask questions and doesn't set goals. Use brief when speed matters; use prep when the user wants to think hard about goals first.
Manage old recordings — find large files, archive old meetings, delete processed originals. Use when the user says "clean up recordings", "how much space are meetings using", "delete old recordings", "archive meetings", "manage meeting storage", or asks about disk space from minutes.
Post-meeting debrief — analyzes what happened, compares outcomes to your prep intentions, tracks decision evolution. Use when the user says "debrief", "what just happened in that meeting", "what did we decide", "debrief that call", "post-meeting", "what changed", or right after stopping a recording.
Policy-safe relationship rankings, commitments, aliases, person profiles, and topic research. Always use Minutes' bounded native CLI surfaces; never build or read a durable graph cache.
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
Extract facts from meetings and update your knowledge base — person profiles, chronological log, and index. Use when the user asks "ingest my meetings", "update my knowledge base", "extract facts from meetings", "sync meetings to wiki", "backfill knowledge", or wants their PARA/Obsidian/wiki profiles updated from conversation data.
Health-check your meeting knowledge for contradictions, stale commitments, and decision conflicts. Use when the user asks "any conflicts in my meetings", "check for stale action items", "lint my meetings", "consistency check", "are there contradictions", or wants to audit their decision history.
List recent meetings and voice memos. Use when the user asks "what meetings did I have", "show my recent recordings", "any meetings today", "list my voice memos", or wants an overview of their meeting history. Also use when they need to find a specific meeting by browsing rather than searching.