- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add silverstein/minutes --skill minutes-lint -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add silverstein/minutes --skill minutes-lint -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add silverstein/minutes --skill minutes-lint -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add silverstein/minutes --skill minutes-lint -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/silverstein/minutes/tree/HEAD/.agents/skills/minutes/minutes-lintFrom the publisher
Run a consistency check across policy-authorized normal meetings to find decision conflicts and stale commitments. Restricted meetings are excluded from this agent workflow by default and must never be described as absent evidence.
Run the consistency check:
minutes consistency --stale-after-days 14
Optional filters:
--owner <name> — limit to commitments assigned to a specific person--stale-after-days <N> — change the staleness threshold (default: 7)Parse the JSON output and present it as readable markdown.
For each conflict, show:
**Topic: {topic}**
- Latest: "{latest decision text}" — *{meeting title}* ({date})
- Prior: "{prior decision text}" — *{meeting title}* ({date})
- **Status**: These decisions may contradict each other.
Frontmatter v2: resolved supersessions. When the resolution field is
present on a conflict, the newer decision has a supersedes: entry in its
frontmatter. Treat this as informational, not a red flag. Format as:
**Topic: {topic}** ✓ Resolved
- Current: "{latest decision text}" — *{meeting title}* ({date})
- Superseded: "{prior decision text}" — *{meeting title}* ({date})
- **Status**: {resolution text}
If the latest decision also carries an authority field (high/medium/low),
surface it next to the title. Authority is optional — when absent, omit the tag.
For each stale item, show:
- [ ] **@{who}**: {task} (due {due_date}, {age_days} days overdue)
- Last discussed: *{meeting title}* ({date})
If no conflicts and no stale commitments, say: "No decision conflicts or stale commitments found across your meetings. Everything looks consistent."
/minutes-debrief on the most recent conflicting meeting, or /minutes-search "{topic}" to review the full decision historyminutes commitments --json; treat a nonzero exit as unavailable, never emptygraph.db (it does not exist)Health-check your meeting knowledge for contradictions, stale commitments, and decision conflicts. Use when the user asks "any conflicts in my meetings", "check for stale action items", "lint my meeti
---name: minutes-lintdescription: Health-check your meeting knowledge for contradictions, stale commitments, and decision conflicts. Use when…---# .agents/skills/minutes/minutes-lint/SKILL.mdOverview
Health-check your meeting knowledge for contradictions, stale commitments, and decision conflicts. Use when the user asks "any conflicts in my meetings", "check for stale action items", "lint my meetings", "consistency check", "are there contradictions", or wants to audit their decision history.
FAQ
Download .agents/skills/minutes/minutes-lint/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/silverstein/minutes.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.