SkillAgentSearch skills...

minutes-graph

Policy-safe relationship rankings, commitments, aliases, person profiles, and topic research. Always use Minutes' bounded native CLI surfaces; never build or read a durable graph cache.

Install / Use

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

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

80/100

Supported Platforms

Zed

Our assessment of minutes-graph

minutes-graph scores 80/100 on our quality scale, 537th of 604 Data & Analytics skills we index.

Its SKILL.md is 2.8 KB long, split into 6 sections and no 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
11/20
Description
15/15
Adoption
14/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so minutes-graph is actively maintained.
  • 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.

minutes-graph compared with similar skills

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

SkillScoreStarsUpdatedFormat
minutes-graph (this skill)by silverstein801.5k54d agoSKILL.md
claude-memby thedotmack100117.7ktodayCLAUDE.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md

Frequently asked questions

How do I install minutes-graph?
Run npx skills add silverstein/minutes --skill minutes-graph. The install tabs above show the steps for each supported agent.
Which AI agents does minutes-graph 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-graph safe to use?
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-graph still maintained?
The repository was last updated about 2 months ago, so minutes-graph is actively maintained.

name: minutes-graph description: Policy-safe relationship rankings, commitments, aliases, person profiles, and topic research. Always use Minutes' bounded native CLI surfaces; never build or read a durable graph cache. compatibility: opencode

/minutes-graph

Minutes builds relationship rankings, exact person profiles, and commitments from one supervised, process-private SQLite projection of stable policy-authorized Markdown plus confirmed identity corrections. One ordered snapshot authority spans corpus and corrections, and the worker is hard-limited for memory, output, and wall time. Topic research uses the separately bounded live-source search boundary. Both paths re-attest policy before returning facts. Do not fall back to a retired durable index or read meeting files directly.

Privacy boundary

  • Never walk meeting files, parse frontmatter yourself, or read raw transcripts for this skill.
  • Never run graph_build.py or read ~/.minutes/graph/index.json; those are retired legacy surfaces.
  • Never create a replacement graph cache, spreadsheet, JSON file, or database.
  • Never pass --include-restricted. Restricted meetings are intentionally absent from this agent-facing skill.
  • Treat any authorization, resource-budget, correction-race, or projection error as a hard stop. Do not fall back to filesystem reads.

Available commands

  • minutes people --json — bounded relationship rankings and losing-touch signals.
  • minutes commitments --json — bounded graph commitments.
  • minutes people merge <canonical> <alias...> — confirm an identity correction in the local vocabulary; uncertain names are never merged automatically.
  • minutes person "<name>" — bounded person profile.
  • minutes research "<topic>" — bounded topic research.

Workflow

  1. Classify the request and use the narrowest command above.
  2. Require exit status 0. Use only the bounded native result and never substitute filesystem reads.
  3. For a proposed alias, show the suggestion and ask for confirmation before running minutes people merge; a wrong merge is worse than no merge.
  4. Do not imply that restricted history or a relationship fact is absent when any command fails.

Output

Return only the bounded native result. Never invent rankings, commitments, or relationship signals from raw files.

Gotchas

  • A failed person profile cannot be interpreted as “never met.” Report the source unavailable.
  • Do not imply that a later sensitivity change proves a historical fact absent; report only the current authorized projection.
  • Alias suggestions are evidence, not permission to rewrite identity. Require explicit confirmation before merging.
  • Use minutes research "<topic>" for bounded company, product, or topic research. If it fails, report the source unavailable; never fall back to raw corpus reads.

Related Skills

View on GitHub
GitHub Stars1.5k
CategoryData
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