minutes-graph

Featured

Cross-meeting entity graph — query who/what/when across all your meetings as structured data, with co-occurrence and cross-entity queries that text search can't answer. Use whenever the user says "show me everyone who mentioned X", "every time we talked about Y", "who knows about Z", "graph", "across all meetings", "entity search", "first time we talked about", "trend for X over time", "who's been mentioned alongside", or wants to query meetings as an index rather than full-text search. Builds a JSON entity index on first run (one-time slow), then answers queries instantly. Surface this skill for relationship intelligence, due diligence, or any "across all my history" question that text search alone can't answer.

AI & Automation 1,609 stars 187 forks Updated today MIT

Install

View on GitHub

Quality Score: 93/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

## Skill Path Before running helper scripts or opening bundled references, set: ```bash export MINUTES_SKILLS_ROOT="$(git rev-parse --show-toplevel)/.agents/skills/minutes" export MINUTES_SKILL_ROOT="$MINUTES_SKILLS_ROOT/minutes-graph" ``` # /minutes-graph Cross-meeting entity graph that lets you query your meeting history as structured data — **people and topics** out of the box, with companies and products as an opt-in deep-extraction path. Minutes already exposes `minutes people`, `minutes person`, and `minutes insights` for first-class entity queries. **Graph layers on top of those** to answer questions the CLI can't: - "What's the co-occurrence between Sarah and pricing?" - "First time the term 'X' appears in my history" - "Frequency trend for topic Y over the last 6 months" - "Who's been mentioned in the same meetings as Sarah?" - "What topics came up when we talked about hiring?" Defer to the existing CLI when it suffices. Use graph for the queries the CLI can't answer. Anything about companies or products requires opt-in deep extraction (see Phase 1). ## How it works Graph has two modes: **build** (creates the index) and **query** (uses it). ### Phase 0: Determine the user's intent If the user explicitly says "build" / "rebuild" / "refresh the graph" → Phase 1 (build mode). Otherwise → Phase 2 (query mode). Query mode auto-builds the index if it doesn't exist, and incrementally refreshes it if new meetings exist since the last build. **Detect company/prod...

Details

Author
silverstein
Repository
silverstein/minutes
Created
8 months ago
Last Updated
today
Language
Rust
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

minutes-prep

Interactive meeting preparation — builds a relationship brief and talking points before a call. Use when the user says "prep me for my call with", "I'm meeting with X", "prepare me for", "what should I bring up with", "meeting prep", "get ready for my call", or wants to review history with someone before a meeting.

1,609 Updated today
silverstein
AI & Automation Featured

minutes-brief

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.

1,609 Updated today
silverstein
AI & Automation Listed

context-graph

Build and query a knowledge graph from someone's own markdown notes — extracting people, companies, projects and the relationships between them, so answers are grounded in their actual notes instead of guessed or retrieved by keyword. Use this when a user wants to make an Obsidian vault or notes folder queryable, asks questions spanning many notes ("who do I know at X", "which contacts relate to this project"), wants Claude to stop re-reading whole files to answer, or asks to build a knowledge graph, context layer, or semantic index over their notes. Runs a structural pass with a script, then a model pass that extracts entities and relationships, and answers later questions from the graph.

1 Updated 3 months ago
jessicahiggs