CtrlK
BlogDocsLog inGet started
Tessl Logo

minutes-graph

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", "all mentions of Y across meetings", "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.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and well-sequenced with strong validation checkpoints, and it wisely delegates heavy lifting to a bundled script. Its main weakness is conciseness — repeated warnings and inline detail (index schema, script internals, long gotchas) that could be tightened or moved to reference files.

Suggestions

De-duplicate the 'warn before building' / 'users hate hanging commands' guidance — state it once in Phase 1 and reference it from Phase 2 and Gotchas rather than repeating the full sentence three times.

Move the full index JSON schema and the 10-step 'What the script does, in order' enumeration into a reference file (e.g. references/INDEX_SCHEMA.md) and link to it, keeping SKILL.md a lean overview.

Trim the gotchas list by merging near-duplicates (e.g. the slug-keying and 'don't invent entities' points overlap with the Lookup rules and Phase 1 guidance) to reduce inline volume.

DimensionReasoningScore

Conciseness

Mostly efficient and full of domain-specific guidance Claude wouldn't know, but padded with redundancy — 'Users hate commands that hang silently more than they hate one-line confirmations' and 'Always warn before building, even on the auto-trigger path' each recur across Phase 1, Phase 2, and Gotchas, and the 10-step 'What the script does, in order' re-explains logic already in the bundled script.

2 / 3

Actionability

Fully executable main path — 'python3 "${CLAUDE_PLUGIN_ROOT}/skills/minutes-graph/scripts/graph_build.py" --incremental' — plus a concrete query-recipe table mapping each user question to a specific index lookup, a full index JSON schema, and a copy-paste ASCII chart format.

3 / 3

Workflow Clarity

Clear Phase 0→1→2→3 sequence with explicit checkpoints: warn-before-build confirmation, mtime-based freshness check for incremental refresh, status JSON feedback (ok/fresh), and an upfront company/product detection guard that prevents the 'build → discover data isn't there → rebuild' loop.

3 / 3

Progressive Disclosure

The heavy build logic is correctly externalized to scripts/graph_build.py (verified present and referenced), and sections are well-organized, but there are no reference files — the full index JSON schema, the 10-step script internals, and a 12-item gotchas list all live inline in SKILL.md, so content that could be split out remains in the overview.

2 / 3

Total

10

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong across the board: it states concrete capabilities, gives a rich set of natural trigger phrases, and cleanly delineates its niche from text search and the existing minutes CLI. Voice is predominantly third-person/imperative ('Builds...', 'Surface this skill'), with only a minor 'your meetings' possessive reference.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'query who/what/when across all your meetings as structured data', 'co-occurrence and cross-entity queries', 'Builds a JSON entity index on first run...then answers queries instantly' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both 'what' (cross-meeting entity graph that builds a JSON index and answers co-occurrence/cross-entity queries) and 'when' ('Use whenever the user says...'), satisfying the 'clearly answers both what AND when with explicit triggers' anchor.

3 / 3

Trigger Term Quality

Excellent coverage of natural phrasings users would say: 'show me everyone who mentioned X', 'all mentions of Y across meetings', 'who knows about Z', 'first time we talked about', 'trend for X over time', 'who's been mentioned alongside' — squarely the 'good coverage of natural terms' anchor.

3 / 3

Distinctiveness Conflict Risk

Clear niche — 'across all meetings', 'query meetings as an index rather than full-text search', 'queries that text search can't answer' — with triggers unlikely to fire for the wrong skill, matching the 'clear niche with distinct triggers' anchor.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
silverstein/minutes
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.