SkillAgentSearch skills...

minutes-lint

Health-check your meeting knowledge for contradictions, stale commitments, and decision conflicts

Install / Use

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

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

84/100

Category

Automation

Supported Platforms

Zed

Our assessment of minutes-lint

minutes-lint scores 84/100 on our quality scale, 2076th of 2,790 Automation skills we index.

Its SKILL.md is 3.2 KB long, well organised into 8 sections with 3 code examples: a solid amount of guidance for an agent.

With 1,500 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
18/20
Description
12/15
Adoption
14/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so minutes-lint is actively maintained.
  • Our last check on 2026-10-14 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-01. Automated pattern scan on 2026-10-01. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

minutes-lint compared with similar skills

All 4 of these similar skills score higher than minutes-lint; compare them before choosing.

SkillScoreStarsUpdatedFormat
minutes-lint (this skill)by silverstein841.5k54d agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md
Scraplingby D4Vinci100103.6k2d agoMCP Server

Frequently asked questions

How do I install minutes-lint?
Run npx skills add silverstein/minutes --skill minutes-lint. The install tabs above show the steps for each supported agent.
Which AI agents does minutes-lint work with?
It is written for Zed, as a SKILL.md file. Other agents that read the same format can often use it too.
Is minutes-lint safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is minutes-lint still maintained?
The repository was last updated about 2 months ago, so minutes-lint is actively maintained.

name: minutes-lint description: 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. compatibility: opencode

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

Related Skills

View on GitHub
GitHub Stars1.5k
CategoryAutomation
Updated1mo ago
Forks165

Languages

Rust

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions