Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →silverstein/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-f
Passed 12 of 17 test cases with the skill, and 5 of 17 without it.
and 6 more in the full report
9 fixed6 passed either way6 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
A search for recent interactions with a client returns 8 meeting transcript files from the past 60 days. How many full meeting documents should be fetched via `minutes get` to build the brief?
| Checked | Without skill | With skill |
|---|---|---|
| Limits full transcript retrieval to at most two meeting documents | Missed | Passed |
The instructions your model reads when the skill loads.
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.
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 "${CLAUDE_PLUGIN_ROOT}/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 "${CLAUDE_PLUGIN_ROOT}/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.
gog CLI (if installed):
gog calendar list --today --json 2>/dev/null
test cases passed, vs 5 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.