minutes-brief
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
npx skills add silverstein/minutes --skill minutes-brief --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
## Skill Path Before running helper scripts or opening bundled references, set: ```bash export MINUTES_SKILLS_ROOT="$(git rev-parse --show-toplevel)/.opencode/skills" export MINUTES_SKILL_ROOT="$MINUTES_SKILLS_ROOT/minutes-brief" ``` # /minutes-brief Fast, non-interactive briefing that synthesizes your relationship history with someone into a one-page brief — designed so you can read it in 60 seconds before walking into a call. This is the **proactive layer**. It's built to be invoked silently by a hook (e.g., 15 min before a calendar event) and to also work as a manual `/minutes-brief` command. Unlike `/minutes-prep`, brief asks no questions and sets no goals — it just hands you the facts. ## How it works ### Phase 0: Determine the target Three ways the user can invoke this: **1. With a name** (`/minutes-brief sarah`, "brief me on Alex") → Use that name directly. Before searching, check for learned aliases: ```bash node "$MINUTES_SKILLS_ROOT/_runtime/hooks/lib/minutes-learn-cli.mjs" aliases "<name>" 2>/dev/null ``` If aliases exist, search across all returned variants and treat them as the same person for the rest of the flow. If the user explicitly says two names are the same per
- Skill Path
- How it works
- Phase 0: Determine the target
- Phase 1: Gather data in parallel
- Phase 2: Read what you actually need
- Phase 3: Synthesize the brief
- Phase 4: Save and display
- Phase 5: One-line nudge
- Gotchas
export MINUTES_SKILLS_ROOT="$(git rev-parse --show-toplevel)/.opencode/skills" export MINUTES_SKILL_ROOT="$MINUTES_SKILLS_ROOT/minutes-brief" node "$MINUTES_SKILLS_ROOT/_runtime/hooks/lib/minutes-learn-cli.mjs" aliases "<name>" 2>/dev/null node "$MINUTES_SKILLS_ROOT/_runtime/hooks/lib/minutes-learn-cli.mjs" set-alias "Sarah Chen" "Sarah" "User confirmed these refer to the same person" gog calendar list --today --json 2>/dev/null minutes person "<name>" Clean JSON on stdout by default (insights does NOT accept --json — output is already JSON). minutes insights --participant "<name>" --kind decision --since <30-days-ago> minutes search "<name>" --limit 10 --since <60-days-ago> --format json minutes search "<name>" --limit 1 --format json
What does the minutes-brief skill do?
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
How do I install it?
Run `npx skills add silverstein/minutes --skill minutes-brief --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From silverstein/minutes, a repository with 1,410 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.