Skip to content
cccskills
FreePublished on GitHub

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.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Fast non-interactive briefing before any meeting — auto-detects your next calendar event, pulls relationship history, surfaces open commitments, and produces a one-page brief in under 30 seconds. Use this whenever the user says "brief me", "give me a quick brief", "what's coming up", "background on my next call", "who am I meeting next", "brief me on Sarah", "I have a call in 10 min", "quick rundown", or right before walking into a meeting. Different from /minutes-prep — brief is the fast hook-fireable version that doesn't ask questions and doesn't set goals. Use brief when speed matters; use prep when the user wants to think hard about goals first.

The English summary is being prepared. Showing the original description.

silverstein/minutes1.6KUpdated Oct 21, 2026

Manage old recordings — find large files, archive old meetings, delete processed originals. Use when the user says "clean up recordings", "how much space are meetings using", "delete old recordings", "archive meetings", "manage meeting storage", or asks about disk space from minutes.

The English summary is being prepared. Showing the original description.

silverstein/minutes1.6KUpdated Oct 21, 2026

Start and control Minutes Coach, the separate real-time copilot HUD, with an explicit meeting goal. Use only for explicit Coach or HUD lifecycle requests such as "start Minutes Coach", "open the Coach HUD", "pause Minutes Coach", "resume Minutes Coach", "Minutes Coach status", or "stop Minutes Coach". Do not use for requests that explicitly ask the current terminal agent to watch or strategize; those belong to minutes-live-sidekick. An ambiguous request such as "coach me live" requires one short surface clarification and must not automatically start Coach.

The English summary is being prepared. Showing the original description.

silverstein/minutes1.6KUpdated Oct 21, 2026

Post-meeting debrief — analyzes what happened, compares outcomes to your prep intentions, tracks decision evolution. Use when the user says "debrief", "what just happened in that meeting", "what did we decide", "debrief that call", "post-meeting", "what changed", or right after stopping a recording.

The English summary is being prepared. Showing the original description.

silverstein/minutes1.6KUpdated Oct 21, 2026

Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.

The English summary is being prepared. Showing the original description.

silverstein/minutes1.6KUpdated Oct 21, 2026

Extract facts from meetings and update your knowledge base — person profiles, chronological log, and index. Use when the user asks "ingest my meetings", "update my knowledge base", "extract facts from meetings", "sync meetings to wiki", "backfill knowledge", or wants their PARA/Obsidian/wiki profiles updated from conversation data.

The English summary is being prepared. Showing the original description.

silverstein/minutes1.6KUpdated Oct 21, 2026

See all skills by silverstein

Report a problem with this skill