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.
npx skills add silverstein/minutes --skill minutes-graph --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-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.
- Privacy boundary
- Available commands
- Workflow
- Output
- Gotchas
What does the minutes-graph skill do?
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.
How do I install it?
Run `npx skills add silverstein/minutes --skill minutes-graph --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.