CtrlK
BlogDocsLog inGet started
Tessl Logo

minutes-debrief

Post-meeting debrief — analyzes what happened, compares outcomes to your prep intentions, tracks decision evolution. Use when the user says "debrief", "what just happened in that meeting", "what did we decide", "debrief that call", "post-meeting", "what changed", or right after stopping a recording.

76

Quality

96%

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

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 a well-structured, highly actionable multi-phase workflow with executable commands, explicit validation checkpoints, and clear error-recovery branches. It is lean throughout with only minor trim opportunities in the sensitive-meeting section.

DimensionReasoningScore

Conciseness

Largely lean and efficient — assumes Claude's competence with no basic-concept explanations and uses tight code blocks — but Phase 2a's length and a few restated sensitivity clauses ('Sensitivity is binding, not advisory' plus surrounding re-explanation) could be trimmed slightly.

4 / 5

Actionability

Provides fully executable, copy-paste-ready commands (e.g. 'minutes list --limit 5', 'minutes get "<exact path>" --json', exact minutes-learn-cli.mjs invocations with arguments) plus concrete AskUserQuestion option text and output templates covering common cases.

5 / 5

Workflow Clarity

Multi-phase flow (1→2→2a/2b→3→4a/4b→5→6) is clearly sequenced with explicit validation checkpoints ('require exit status 0', no-recording handling, multiple-recording disambiguation, speaker-confidence branches) and feedback loops for error recovery.

5 / 5

Progressive Disclosure

Single self-contained file with no external bundle references needed; content is well-organized into clearly headed phases and a Gotchas section, making navigation easy with no nested-reference problem.

5 / 5

Total

19

/

20

Passed

Description

100%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 exemplary: it pairs three concrete capabilities with a rich, natural set of trigger phrases and an explicit Use-when clause, fully covering both what and when with low conflict risk. No vague fluff or over-claims are present.

DimensionReasoningScore

Specificity

Names three concrete, distinct actions — 'analyzes what happened, compares outcomes to your prep intentions, tracks decision evolution' — giving comprehensive coverage of the skill's capabilities with no gaps.

5 / 5

Completeness

Explicitly answers both 'what' (post-meeting debrief that analyzes/compares/tracks) and 'when' (a 'Use when...' clause with concrete trigger phrases and a temporal cue), matching the top anchor.

5 / 5

Trigger Term Quality

Lists extensive natural user phrases including synonyms — 'debrief', 'what just happened in that meeting', 'what did we decide', 'debrief that call', 'post-meeting', 'what changed' — matching the comprehensive-coverage anchor.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (post-meeting debrief tied to recordings) with distinct, specific triggers unlikely to fire for unrelated skills, matching the minimal-conflict-risk anchor.

5 / 5

Total

20

/

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.

Validation — 15 / 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.