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.

60

Quality

68%

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 ./.opencode/skills/minutes-graph/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

The body is a tight, well-structured instruction-only skill with concrete CLI commands, a sequenced workflow with validation checkpoints, and clear boundaries. Minor gaps are limited to slight cross-section redundancy and the absence of example invocations or sample outputs.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, but the "Do not imply restricted history is absent" guidance is restated across Workflow step 4 and the Gotchas section, a minor redundancy that could be trimmed.

4 / 5

Actionability

Concrete copy-paste-ready commands are listed (e.g. `minutes people --json`, `minutes people merge <canonical> <alias...>`), but no example invocations or sample outputs are shown, leaving a minor gap.

4 / 5

Workflow Clarity

The four-step workflow has explicit validation ("Require exit status 0", confirmation before merge, hard-stop on errors), but lacks a fix-and-retry feedback loop since failures are terminal hard stops.

4 / 5

Progressive Disclosure

At under 50 lines with no need for external references, the content is cleanly organized into well-signaled sections (Privacy boundary, Available commands, Workflow, Output, Gotchas), meeting the simple-skill exception for a top score.

5 / 5

Total

17

/

20

Passed

Description

58%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.

The description clearly conveys what the skill produces within a well-bounded Minutes niche, but it omits any explicit "Use when..." trigger guidance and leans on technical jargon over natural user phrasing. Strong on distinctiveness and capability specificity, weaker on trigger terms and completeness.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks about relationship rankings, commitments, person aliases, or topic research from Minutes."

Replace jargon like "bounded native CLI surfaces" and "durable graph cache" with natural phrasings a user would actually say.

Reframe the capability list as concrete actions (e.g. "Rank relationships, surface commitments, confirm aliases, build person profiles, research topics").

DimensionReasoningScore

Specificity

Names several concrete capabilities ("relationship rankings, commitments, aliases, person profiles, and topic research") but lists them as nouns rather than explicit actions, leaving minor phrasing gaps versus the comprehensive verb-based anchor.

4 / 5

Completeness

The "what" is clear, but there is no "Use when..." clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Some relevant keywords appear (commitments, person profiles, topic research) but "bounded native CLI surfaces" and "durable graph cache" are technical jargon, and common natural user phrasings are missing.

3 / 5

Distinctiveness Conflict Risk

The Minutes-specific niche and explicit "never build or read a durable graph cache" boundary make it mostly distinct with only minor overlap risk, though the absent trigger clause slightly weakens distinctiveness.

4 / 5

Total

14

/

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.