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

92%

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 strong, highly actionable skill body: exact commands, a deterministic helper script, explicit validation and error-recovery loops, and well-defined data-quality thresholds. The weaknesses are redundancy between the phase sections and the Gotchas list, and a monolithic SKILL.md that keeps per-run reference material inline instead of splitting it into a one-level-deep reference file.

Suggestions

Deduplicate Gotchas against the phase sections: the ≥5-meeting and ≥3-per-tag thresholds (Phase 2b) and the LLM token-counting caveat (Phase 2a) are each stated twice — keep them in one place and reference it.

Move the 14-row metrics-field table and the two markdown output templates to a references/ file (e.g., references/metrics.md and references/output-templates.md), leaving SKILL.md a leaner overview that points one level deep.

Trim coaching-tone prose that repeats itself: "The point is not to roast you" (intro) and "This is coaching, not roasting" (Gotchas) make the same point; state it once.

DimensionReasoningScore

Conciseness

The body is dense with genuinely non-obvious operational content (CLI flags, exit codes, thresholds, output formats) and assumes Claude's competence, but several points are stated twice: the ≥5-meeting and ≥3-per-tag thresholds appear in Phase 2b and again in Gotchas, "LLMs are bad at exact token counting" appears in Phase 2a and Gotchas, and the kindness/no-roast point is made in the intro and repeated in Gotchas. Efficient with minor trimming opportunities — not 3, since none of the repetition is conceptual padding Claude already knows.

4 / 5

Actionability

Fully executable throughout: exact bash commands ("minutes voices --json", "minutes list --content-type meeting --limit 5"), a complete pipeline with `set -o pipefail`, a verified bundled script path, an output-field table, a `printf` caching command, exit-code-3 recovery instructions, and copy-ready output format templates covering both modes. Matches the copy-paste-ready anchor with common cases covered.

5 / 5

Workflow Clarity

Phases 0–3 are clearly sequenced with explicit validation checkpoints ("Require exit status 0", "Require both sides of the pipeline to exit successfully"), error-recovery feedback loops (exit code 3 → re-run with a found speaker label or update the cache), an explicit ambiguity default, and honest-failure rules when data thresholds aren't met ("Baseline computed from only N meetings, treat with caution").

5 / 5

Progressive Disclosure

The deterministic-metrics logic is appropriately externalized to the real bundled script (verified at scripts/mirror_metrics.py) and clearly signaled with its interface documented, and sections are well-organized. Not 5: the ~210-line body is the full content rather than an overview — the 14-row metrics table and the two output-format templates are per-run details that could live one level deep in a reference file, and the bundle has no references/ directory at all.

4 / 5

Total

18

/

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.

An excellent description: concrete capability list, exhaustive natural trigger phrases, and explicit when-to-use guidance with a clear, well-scoped niche. The only deduction is the second-person voice ("your own behavior"), which the rubric penalizes on specificity.

DimensionReasoningScore

Specificity

Names multiple concrete capabilities — "talk-time ratio, filler words, hedging language, monologue length, energy patterns" plus win/loss behavior comparison — which matches the comprehensive anchor, but the second-person voice ("your own behavior", "what your behavior in winning meetings looks like") incurs the rubric's −1 specificity penalty vs. the third-person convention.

4 / 5

Completeness

Explicitly answers both questions: a clear "what" ("Self-coaching analysis of your own behavior across meetings" with named metrics) and an explicit "when" ("Use this whenever the user says...") with concrete trigger phrases — a direct match for the anchor, unlike the score-4 case where 'when' is less explicit.

5 / 5

Trigger Term Quality

"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", "feedback on me" — comprehensive coverage of natural phrases a user would actually say, including synonyms, plus explicit instruction to trigger on curiosity about performance even without the word "mirror". Not 4 because no common variation is missing.

5 / 5

Distinctiveness Conflict Risk

A clear niche (personal meeting-behavior self-analysis) with distinct triggers like "mirror" and "how did I do", and broad phrases like "coach me" and "any kind of personal feedback" are explicitly scoped to "their own meeting behavior". Not 4: the scoping eliminates the minor overlap risk with general coaching/feedback skills.

5 / 5

Total

19

/

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

.claude/plugins/minutes/skills/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.