Minutes Tag
Lightweight outcome tagging for meetings, won, lost, stalled, great, or noise.
Install
npx skills add silverstein/minutes --skill minutes-tag -g -a claude-code -y- Repository
- silverstein/minutes1.6k
- Category
- Engineering
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 2,073 tokens
- Runs scripts
- Yes, review before use
What it does
Lightweight outcome tagging for meetings, won, lost, stalled, great, or noise. Use whenever the user says "tag this meeting", "mark that as a win", "that one was a loss", "tag yesterday's call as stalled", "mark this great", "that meeting was noise", "label that meeting", or any time they describe a meeting outcome in passing. Tagging takes 5 seconds and unlocks /minutes-mirror correlation analysis, the more meetings get tagged, the smarter mirror gets at telling the user what behavior patterns lead to wins. Surface this skill any time the user mentions a meeting result, win, loss, or wasted time.
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-tag"
/minutes-tag
Lightweight outcome tagging, adds an outcome: field to a meeting's frontmatter so /minutes-mirror can correlate the user's behavior with their results over time.
The whole point of this skill is speed. Tagging should take 5 seconds, not 5 questions. Don't be precious about it, most users will never adopt tagging if it feels like data entry.
How it works
Phase 1: Identify the meeting
Three patterns the user might use. Always filter to meetings, not voice memos, voice memos can't be "won" or "lost".
1. Most recent ("tag this meeting", "mark that as a win", "tag the call I just finished"):
minutes list --content-type meeting --limit 1
Use the most recent. Don't ask which one, that defeats the speed promise. The default behavior should always be "the call you just had".
2. By date ("tag yesterday's call", "tag the Tuesday call"):
minutes list --content-type meeting --limit 10
Pick the meeting matching the date. If multiple meetings match the same day, ask once: "You had <N> meetings <date>. Which one?" with options listing titles.
3. By name ("tag my call with Sarah as a win"):
minutes search "<name>" --content-type meeting --limit 5
Pick the most recent. If ambiguous, ask once.
Phase 2: Identify the tag
If the user already named the outcome in their message ("tag that as a win"), use it directly. Don't ask again, they already told you.
If they haven't, ask via AskUserQuestion with these standard options:
