minutes-tag
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
npx skills add silverstein/minutes --skill minutes-tag --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-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"): ```bash 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"): ```bash minutes list --content-type meeting --limit 10 ``` Pick the
- Skill Path
- How it works
- Phase 1: Identify the meeting
- Phase 2: Identify the tag
- Phase 3: Capture a note only if the user gave one in their message
- Phase 4: Edit the frontmatter via the bundled helper script
- Phase 5: Confirm and nudge
- Gotchas
export MINUTES_SKILLS_ROOT="$(git rev-parse --show-toplevel)/.opencode/skills" export MINUTES_SKILL_ROOT="$MINUTES_SKILLS_ROOT/minutes-tag" minutes list --content-type meeting --limit 1 minutes list --content-type meeting --limit 10 minutes search "<name>" --content-type meeting --limit 5 python3 "$MINUTES_SKILL_ROOT/scripts/tag_apply.py" \ minutes get "<filename-without-.md>" 2>&1 | head -3 ls ~/.minutes/tag-nudge-shown 2>/dev/null mkdir -p ~/.minutes && touch ~/.minutes/tag-nudge-shown
What does the minutes-tag skill do?
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
How do I install it?
Run `npx skills add silverstein/minutes --skill minutes-tag --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.