minutes-note

$npx mdskill add silverstein/minutes/minutes-note

Add timestamped notes during or after meetings for summarization.

  • Captures user thoughts during recordings or annotates past meetings.
  • Depends on active recording or existing meeting file for annotation.
  • Uses plain text input and timestamps notes to recording position.
  • Feeds notes as high-priority context into the LLM summarizer.

SKILL.md

.github/skills/minutes-noteView on GitHub ↗
---
name: minutes-note
description: Add a note to the current recording or annotate a past meeting. Use whenever the user says "note that", "remember this", "mark this as important", "add a note about", "annotate the meeting", or wants to capture a thought during or after a recording. Plain text input — no markdown needed.
---

# /minutes-note

Add a timestamped note during a recording, or annotate a past meeting.

## During a recording

```bash
# Add a note to the active recording (auto-timestamped)
minutes note "Alex wants monthly billing not annual billing"
minutes note "Case agreed — compromise at monthly billing for experiment"
```

Each note gets a timestamp matching the recording position (e.g., `[4:23]`). Notes feed into the LLM summarizer as high-priority context — the AI knows what you thought was important and weights those parts of the transcript more heavily in the summary.

## After a meeting

```bash
# Annotate an existing meeting file
minutes note "Follow-up: Alex confirmed via email on Mar 18" --meeting ~/meetings/2026-03-17-pricing-call.md
```

Appends to the `## Notes` section of the meeting file with a date stamp.

## Tips

- Notes are plain text — just type what you're thinking, no formatting needed
- Short notes work best: "pricing pushback" > "Alex expressed concerns about the current pricing structure and suggested..."
- Notes are searchable via `minutes search`

## Gotchas

- **Must have an active recording for live notes** — `minutes note "..."` without `--meeting` requires a recording in progress. Check with `minutes status` first. If no recording is active, use `--meeting <path>` to annotate an existing file.
- **`--meeting` requires the full path** — Use the exact path from `minutes list` or `minutes search`, e.g., `--meeting ~/meetings/2026-03-17-pricing-call.md`. Tab completion works.
- **Notes don't support markdown** — The note content is plain text. Markdown formatting like `**bold**` or `- lists` will be stored literally, not rendered.
- **Quotes in notes need escaping** — If your note contains quotes, wrap the whole thing in single quotes or escape them: `minutes note 'Alex said "no way"'`.

More from silverstein/minutes

SkillDescription
minutes-briefFast 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.
minutes-cleanupManage 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.
minutes-copilotStart 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.
minutes-debriefPost-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.
minutes-graphCross-meeting entity graph — query who/what/when across all your meetings as structured data, with co-occurrence and cross-entity queries that text search can't answer. Use whenever the user says "show me everyone who mentioned X", "all mentions of Y across meetings", "who knows about Z", "graph", "across all meetings", "entity search", "first time we talked about", "trend for X over time", "who's been mentioned alongside", or wants to query meetings as an index rather than full-text search. Builds a JSON entity index on first run (one-time slow), then answers queries instantly. Surface this skill for relationship intelligence, due diligence, or any "across all my history" question that text search alone can't answer.
minutes-ideasSurface 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.
minutes-ingestExtract 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.
minutes-lintHealth-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.
minutes-listList 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.
minutes-live-sidekickAct as the user's live meeting sidekick inside the current terminal agent session. Use when the user explicitly asks you, the terminal agent, to watch a meeting, follow the live transcript, answer during the call, offer strategist thoughts, silently watch for risks, or track decisions. Do not use this skill to start or control the separate Minutes Coach HUD; explicit Coach or HUD lifecycle requests belong to minutes-copilot, and an ambiguous request such as "coach me live" requires one short surface clarification.