minutes-tag SKILL.md skillA
minutes-tag from silverstein/minutes is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add silverstein/minutes/minutes-tag@git:20260409.ca98744Pins git:20260409.ca98744 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- silverstein/minutes
- Path
.claude/plugins/minutes/skills/minutes-tag/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260409.ca98744, committed Apr 9, 2026
- First version recorded
- Apr 9, 2026
- Size
- 8,803 bytes
- Repository stars
- 1,591
- License
- MIT
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…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# /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 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"):
```bash
…Read the whole file at its exact version.
How to install
mdr add silverstein/minutes/minutes-tag@sha256:6f4e54342b73d3aaThe line at the top of this page pins the label git:20260409.ca98744, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_5fii7jpd5qk5tu7e)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Apr 9, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260409.ca98744 latest | 2026-04-09 | ca98744 | 8,803 B | A | view · diff |
| git:20260409.6818e1c | 2026-04-09 | 6818e1c | 8,802 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8803 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
silverstein/minutes · 1,591 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5fii7jpd5qk5tu7e GET https://markdownregistry.com/api/v1/resolve?ref=silverstein/minutes/minutes-tag GET https://markdownregistry.com/api/v1/blob/6f4e54342b73d3aa686636a07d2e3fb36b3f2df69ec33919e101498427326f89
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from silverstein/minutes
Every file in silverstein/minutes