minutes-lint
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.
npx skills add silverstein/minutes --skill minutes-lint --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.
# /minutes-lint 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. ## How to run the lint 1. **Run the consistency check**: ```bash 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) 2. **Parse the JSON output** and present it as readable markdown. ## Formatting the report ### Decision Conflicts 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}) - Supersede
- How to run the lint
- Formatting the report
- Decision Conflicts
- Stale Commitments
- Clean bill of health
- When to suggest next steps
- Gotchas
minutes consistency --stale-after-days 14
What does the minutes-lint skill do?
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.
How do I install it?
Run `npx skills add silverstein/minutes --skill minutes-lint --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.