CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

65

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/minutes/minutes-graph/SKILL.md

The canonical home for this skill is minutes-graph in silverstein/minutes

SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

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

A tight, actionable skill body with concrete CLI commands, explicit safety boundaries, and clean section structure. The only real weakness is a slightly over-detailed architecture preamble and the absence of a retry loop in the workflow.

Suggestions

Trim the opening paragraph's internal-implementation detail (SQLite projection, snapshot authority, worker limits) to the constraints Claude actually needs to honor.

Add an explicit fix-and-retry step for non-zero exit codes (e.g., 'on failure, surface the bounded error and re-run with corrected arguments; never fall back to filesystem reads') to close the workflow feedback loop.

DimensionReasoningScore

Conciseness

Mostly lean and free of generic concept explanation, but the opening paragraph over-shares internal architecture ("process-private SQLite projection", "ordered snapshot authority", worker hard-limits) that Claude does not need to invoke the commands.

4 / 5

Actionability

Fully executable, copy-paste-ready commands with concrete argument syntax (e.g., `minutes people merge <canonical> <alias...>`, `minutes person "<name>"`) covering the common cases.

5 / 5

Workflow Clarity

A clear 4-step sequence with real validation checkpoints (require exit status 0, confirm before merging, hard-stop on error), but it lacks an explicit fix-and-retry feedback loop for failed commands.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references and well-organized into clearly signaled sections (Privacy boundary, Available commands, Workflow, Output, Gotchas), matching the simple-skill exception for a top score.

5 / 5

Total

18

/

20

Passed

Description

70%Weight 40%Scale 1-5

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

A specific, distinctive description that clearly states what the skill produces and carves out a unique niche, but it omits any explicit 'when to use this' trigger guidance, which caps completeness. Voice is correctly third-person.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers (e.g., 'Use when the user asks about relationship rankings, commitments, person history, or wants to merge name aliases from meeting minutes').

Consider adding common-synonym trigger terms like 'contacts', 'people', or 'meeting notes' alongside the current vocabulary.

DimensionReasoningScore

Specificity

Lists several concrete capabilities ("relationship rankings, commitments, aliases, person profiles, and topic research") but as noun-phrase deliverables rather than action verbs, leaving a minor gap versus the comprehensive-action anchor.

4 / 5

Completeness

The "what" is clear and specific, but there is no "Use when..." clause or equivalent trigger guidance, so completeness is capped at 3 per the missing-trigger guideline.

3 / 5

Trigger Term Quality

Good natural-term coverage ("relationship rankings", "commitments", "aliases", "person profiles", "topic research") a user might say, though more common synonyms like "contacts" or "meeting notes" are absent.

4 / 5

Distinctiveness Conflict Risk

The Minutes-branded niche (relationship/commitment graph via bounded CLI) with explicit anti-cache boundary gives it a clear, distinct trigger set with minimal overlap risk.

5 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.