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.

64

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 ./.claude/plugins/minutes/skills/minutes-graph/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 concise, well-structured, and highly actionable with explicit validation checkpoints and feedback loops; the only minor gap is the absence of example command invocations or sample output.

DimensionReasoningScore

Conciseness

Lean and efficient throughout; assumes Claude's competence and never explains concepts Claude already knows, with every section earning its tokens.

5 / 5

Actionability

Provides concrete, executable `minutes` commands with arguments for each capability, but lacks example invocations or sample output to fully cover common cases.

4 / 5

Workflow Clarity

Numbered workflow with explicit validation checkpoints (exit status 0, hard stops on errors, confirmation before merge) and a Gotchas section giving feedback loops for error recovery.

5 / 5

Progressive Disclosure

No bundle files are present; the under-50-line body is well-organized into clearly headed sections (Privacy boundary, Available commands, Workflow, Output, Gotchas), satisfying the simple-skill exception.

5 / 5

Total

19

/

20

Passed

Description

63%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 is specific and clearly delineates a niche, but it lacks an explicit 'Use when...' trigger clause, which caps completeness and weakens trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause naming the natural phrases users say (e.g., 'Use when the user asks who they are losing touch with, wants relationship rankings, commitments, or person profiles from meeting minutes').

Replace internal jargon ('bounded native CLI surfaces', 'durable graph cache') in the description with at least some user-facing synonyms while keeping the safety boundary in the body.

Include common variations/synonyms (e.g., 'meeting minutes', 'contacts', 'follow-ups') to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities (relationship rankings, commitments, aliases, person profiles, topic research) and names the bounded native CLI surfaces, giving comprehensive coverage.

5 / 5

Completeness

Has a clear 'what' but no explicit 'Use when...' or equivalent trigger guidance for when Claude should invoke the skill, capping completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Includes relevant domain terms (relationship rankings, commitments, aliases, person profiles, topic research) but omits natural phrases a user would actually say, leaning on internal jargon like 'bounded native CLI surfaces'.

3 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Minutes relationship/commitment data via a bounded CLI) with distinct triggers; minor overlap risk with general research or person-lookup skills.

4 / 5

Total

15

/

20

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.