Minutes Brief
Fast non-interactive briefing before any meeting, auto-detects your next calendar...
Install
npx skills add silverstein/minutes --skill minutes-brief -g -a claude-code -y- Repository
- silverstein/minutes1.6k
- Category
- Engineering
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 2,918 tokens
- Runs scripts
- No, instructions only
What it does
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.
Skill Path
Before running helper scripts or opening bundled references, set:
export MINUTES_SKILLS_ROOT="$(git rev-parse --show-toplevel)/.agents/skills/minutes"
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:
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 person, persist it:
node "$MINUTES_SKILLS_ROOT/_runtime/hooks/lib/minutes-learn-cli.mjs" set-alias "Sarah Chen" "Sarah" "User confirmed these refer to the same person"
Then skip to Phase 1.
2. With "auto" or no argument (/minutes-brief, "brief me on my next call")
ā Auto-detect the next upcoming calendar event. Try sources in order, use the first that works:
-
Google Calendar MCP (best, Claude users):
gcal_list_events(timeMin: "<now ISO>", timeMax: "<+2hr ISO>", condenseEventDetails: false)Filter to events with 2+ attendees, skip all-day events, pick the soonest. Pull attendee names from the event.
-
gogCLI (if installed):gog calendar list --today --json 2>/dev/null
