CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

minutes-mirror

Self-coaching analysis of your own behavior across meetings — talk-time ratio, filler words, hedging language, monologue length, energy patterns, and (when meetings are tagged via /minutes-tag) what your behavior in winning meetings looks like vs losing ones. Use this whenever the user says "how did I do", "review my last meeting", "mirror", "self-review", "show my patterns", "coach me", "where am I weak", "talk time", "am I improving", "what do I do in meetings I win", "feedback on me", or asks for any kind of personal feedback on their own meeting behavior. This is the rare skill that gives the user a mirror to their own habits — surface it whenever they show curiosity about their own performance, even if they don't use the word "mirror".

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

77%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 exceptionally actionable and workflow-safe: exact commands, documented script I/O, exit-code recovery loops, and honest-degradation rules for sparse data. Its weaknesses are redundancy in the Gotchas section — thresholds restated from Phase 2b and a long-transcript counting gotcha that contradicts the script mandate — and a referenced helper script that is absent from the provided bundle.

Suggestions

Deduplicate the Gotchas section: remove 'Pattern mode needs at least 5 meetings' and 'Outcome correlations need at least 3 per group' (Phase 2b states both), and delete or rewrite the 'Long-transcript accuracy degrades' gotcha, which contradicts the instruction to compute all counts via mirror_metrics.py.

Resolve the broken bundle reference: scripts/mirror_metrics.py is referenced by the core pipeline command but does not exist in the provided bundle — add it, or inline the metric logic and drop the external path.

Tighten command consistency: pass --json to 'minutes list' in both modes (Phase 2b says 'filter its JSON results' but the command omits the flag), and specify the actual 'bounded search' command for locating a user-named meeting.

DimensionReasoningScore

Conciseness

The body is mostly efficient — commands, the metric-field table, and both output templates carry operational weight — but the Gotchas section restates the '>=5 meetings' and '>=3 per tag group' thresholds already specified in Phase 2b, and the 'Long-transcript accuracy degrades' gotcha ('sample three 1500-word segments and extrapolate') directly contradicts the mandate to 'Compute the metrics with the bundled helper script, not by counting in-context'. This is 'some unnecessary explanation or could be tightened' rather than the merely trimmable minor instances of anchor 4.

3 / 5

Actionability

Fully executable throughout: exact commands ('minutes voices --json', 'cat ~/.minutes/config/self.txt', 'mkdir -p ~/.minutes/config; printf …'), the complete 'set -o pipefail' pipeline into mirror_metrics.py with the '--self' flag, a field-by-field table of script output, exit-code semantics with a concrete recovery path ('On exit code 3 … re-run with one of those, or update ~/.minutes/config/self.txt'), and copy-paste output templates. This matches the copy-paste-ready anchor; no gaps for the common single-meeting and pattern cases.

5 / 5

Workflow Clarity

Five clearly sequenced phases (0-3) with explicit validation ('Require exit status 0', 'Require both sides of the pipeline to exit successfully'), genuine feedback loops (exit code 3 → re-run with the discovered speaker labels; ask-once-and-cache in Phase 0), and degradation checkpoints ('Baseline computed from only N meetings, treat with caution', 'If every result is null, skip the outcome-correlation section'). This is the validate→fix→retry anchor fully realized; 4 would apply only if recovery guidance were missing.

5 / 5

Progressive Disclosure

In-file structure is clean (phased headers, tables, templates) and the single external reference — ${CLAUDE_PLUGIN_ROOT}/skills/minutes-mirror/scripts/mirror_metrics.py — is clearly signaled and only one level deep. However, no scripts/, references/, or assets/ directories exist in the provided bundle, so the skill's central dependency cannot be verified to exist and the core pipeline command is unresolvable; that broken primary reference prevents the 'minor organization gaps' fit of anchor 4.

3 / 5

Total

16

/

20

Passed

Description

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

This is an exemplary description on completeness and trigger coverage: it names the domain, enumerates concrete capabilities, lists a rich set of natural trigger phrases, and adds a behavioral fallback cue for implicit requests. Its only deductions are the second-person voice in the capability statement ('your own behavior') and minor overlap risk from broad phrases like 'feedback on me'.

DimensionReasoningScore

Specificity

Lists six concrete capabilities — 'talk-time ratio, filler words, hedging language, monologue length, energy patterns' plus winning-vs-losing behavior comparison — which matches the comprehensive anchor. However, the capability statement is second person ('Self-coaching analysis of your own behavior across meetings'), and the guidelines explicitly reduce specificity by 1 for second-person voice, so 5 drops to 4; 3 is too low since coverage goes well beyond 1-2 actions.

4 / 5

Completeness

Explicitly answers both questions: what ('Self-coaching analysis of your own behavior across meetings — talk-time ratio, filler words, hedging language, monologue length, energy patterns…') and when ('Use this whenever the user says…') with concrete trigger phrases. This is a direct match for the top anchor; 4 would require the 'when' to be less explicit than it is.

5 / 5

Trigger Term Quality

Quotes an extensive set of natural user phrasings — 'how did I do', 'review my last meeting', 'mirror', 'self-review', 'show my patterns', 'coach me', 'where am I weak', 'am I improving', 'feedback on me' — plus a behavioral catch-all ('whenever they show curiosity about their own performance'). This is comprehensive natural-term coverage including synonyms; 4 would apply only if natural variants were missing.

5 / 5

Distinctiveness Conflict Risk

Stakes out a clear niche (a mirror to the user's own meeting behavior) with mostly distinctive triggers ('mirror', 'how did I do', 'show my patterns'), but broad phrases like 'feedback on me' and 'review my last meeting' could plausibly trigger a meeting-summary or general-coaching skill — minor overlap risk with closely related skills, exactly the anchor-4 fit. Not 5 given that overlap; not 3 since the core triggers are unique to this skill.

4 / 5

Total

18

/

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

Path

tooling/skills/goldens/claude/minutes-mirror/SKILL.md

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.