agentsclimarketplace

Minutes lint

Skill silverstein/minutes/.agents/skills/minutes/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.From its SKILL.md

Install
npx -y skills add silverstein/minutes --skill minutes-lint

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

3.2 KB, as published. Nobody here has run it

/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:

    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})
- 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.

Stale Commitments

For each stale item, show:

- [ ] **@{who}**: {task} (due {due_date}, {age_days} days overdue)
  - Last discussed: *{meeting title}* ({date})

Clean bill of health

If no conflicts and no stale commitments, say: "No decision conflicts or stale commitments found across your meetings. Everything looks consistent."

When to suggest next steps

  • If there are decision conflicts: suggest running /minutes-debrief on the most recent conflicting meeting, or /minutes-search "{topic}" to review the full decision history
  • If there are stale commitments: suggest the user update the action item status in the meeting file, or bring it up in the next meeting with that person
  • Relationship-graph commitments come from minutes commitments --json; treat a nonzero exit as unavailable, never empty

Gotchas

  • The consistency check reads live Markdown — it uses stable source snapshots, not a durable graph cache. If a result looks wrong, inspect and correct the referenced meeting source; do not suggest deleting or rebuilding graph.db (it does not exist)
  • Stale != forgotten — some action items are intentionally deferred. Don't alarm the user; present the data and let them decide
  • Decision conflicts are topic-based — two meetings discussing "pricing" with different conclusions will flag, even if the later decision intentionally superseded the earlier one. Context matters.

What ships with it: 1 file

216 B alongside SKILL.md

agents/

Gives 0 of the 12 instructions most quality gates skills give

Counted across 1,524 of the 2,830 authors here whose files we hold, read 2026-09-06

  • Read full output and check exit codein 45 of 1524, across 40 files
  • Verify output confirms the claimin 44 of 1524, across 39 files
  • Identify the command that proves the claimin 43 of 1524, across 39 files
  • Execute the full verification commandin 36 of 1524, across 30 files
  • Produce a verification reportin 34 of 1524, across 18 files
  • Review git diff changesin 30 of 1524, across 16 files
  • Fix build failures immediatelyin 29 of 1524, across 9 files
  • Group findings by severityin 28 of 1524
  • State claim only with evidencein 27 of 1524, across 22 files
  • Verify regression tests with red-green cyclein 26 of 1524, across 22 files
  • Run the full test suitein 26 of 1524, across 25 files
  • Run test suite with coveragein 25 of 1524, across 10 files

Said here and by no other author read

  • run consistency check across authorized meetings
  • parse json output into readable markdown
  • format decision conflicts with topic and status
  • format stale commitments with assignee and due date
  • surface authority field if present
  • suggest debriefing conflicting meetings

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 613,297. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.