CtrlK
BlogDocsLog inGet started
Tessl Logo

minutes-verify

Verify that Minutes is properly set up and working — model downloaded, mic accessible, directories exist, no stale state. Use when the user says "is minutes working", "check my setup", "verify minutes", "test recording setup", "why isn't minutes working", "minutes health check", or after running setup for the first time.

76

Quality

94%

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

93%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 well-structured, actionable verification skill that delegates execution to a bundled script while giving Claude concise remediation guidance and gotchas. Workflow clarity is the only slightly soft dimension because the flow is prose rather than an explicitly numbered sequence.

Suggestions

Add a short numbered run sequence (1. export env vars, 2. run verify-setup.sh, 3. report per-check results, 4. apply fixes for any FAIL) to make the workflow checkpoints explicit.

State upfront that the script exits non-zero when any check fails, so Claude knows to treat the exit code as the validation signal.

DimensionReasoningScore

Conciseness

The body is lean and every section (skill path, one verification command, a checks table, targeted remediation, gotchas) contains Minutes-specific operational knowledge Claude would not already know, with no padding or explanation of generic concepts.

5 / 5

Actionability

It gives a copy-paste-ready command (bash "$MINUTES_SKILL_ROOT/scripts/verify-setup.sh") with env setup, a table of what is checked, and concrete remediation commands (cargo build, minutes setup --model small, mkdir -p, rm) for each failure mode.

5 / 5

Workflow Clarity

The sequence (set env vars, run script, read pass/fail output, report, remediate failures) is clear and the script supplies per-check validation, but the steps are presented as prose and a bulleted fix list rather than an explicitly numbered sequence with checkpoints.

4 / 5

Progressive Disclosure

The body is a well-organized overview with clearly signaled one-level-deep reference to the bundled scripts/verify-setup.sh, no nested references, and content appropriately kept inline for a skill of this size.

5 / 5

Total

19

/

20

Passed

Description

95%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 strong description with an explicit what/when structure, third-person imperative voice, and a rich set of natural trigger phrases. The only minor gap is that the capabilities are framed as a single verify action with checked-items rather than multiple distinct concrete operations.

DimensionReasoningScore

Specificity

The description lists concrete checks ("model downloaded, mic accessible, directories exist, no stale state") naming the domain and several specific components, but the single overarching verb "Verify" with a list of checked items leaves minor gaps versus fully enumerated distinct actions.

4 / 5

Completeness

It explicitly answers both what ("Verify that Minutes is properly set up and working ...") and when ("Use when the user says ...") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

It provides comprehensive natural user phrases ("is minutes working", "check my setup", "verify minutes", "test recording setup", "why isn't minutes working", "minutes health check") plus a contextual trigger ("after running setup for the first time"), covering synonyms and paraphrases a user would actually say.

5 / 5

Distinctiveness Conflict Risk

The Minutes-specific niche and uniquely branded trigger phrases ("minutes working", "minutes health check") make it clearly distinguishable from other skills with minimal overlap risk.

5 / 5

Total

19

/

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.