CtrlK
BlogDocsLog inGet started
Tessl Logo

minutes-copilot

Start and control Minutes Coach, the separate real-time copilot HUD, with an explicit meeting goal. Use only for explicit Coach or HUD lifecycle requests such as "start Minutes Coach", "open the Coach HUD", "pause Minutes Coach", "resume Minutes Coach", "Minutes Coach status", or "stop Minutes Coach". Do not use for requests that explicitly ask the current terminal agent to watch or strategize; those belong to minutes-live-sidekick. An ambiguous request such as "coach me live" requires one short surface clarification and must not automatically start Coach.

77

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 exemplary: every instruction is executable, the workflow is sequenced with explicit conflict checks and failure handling, and the guardrails concisely fence off the failure modes (transcript tailing, cloud routing, tool injection). Nothing is padded and no external references are needed at this size.

DimensionReasoningScore

Conciseness

The body is lean and imperative throughout ("Never tail a transcript file... Never send meeting text to a model directly"), explains nothing Claude already knows, and every line instructs, matching the lean/efficient anchor at 5 rather than the minor-trimming anchor at 4.

5 / 5

Actionability

Commands are copy-paste ready and cover the common cases ("minutes copilot start --goal '<meeting goal>' --surface tui --mode generic" plus status/pause/resume/stop), clarification prompts are given verbatim, and the MCP-first-then-CLI fallback is concretely specified, satisfying the fully-executable top anchor.

5 / 5

Workflow Clarity

The start flow is a clear numbered sequence with an explicit checkpoint ("Do not start a second session when `minutes copilot status` reports one active") and an error-recovery path ("If the provider is unavailable, say that Coach degraded or did not start and make clear that recording remains unaffected"), matching the explicit-validation anchor; this is not a destructive or batch operation so no cap applies.

5 / 5

Progressive Disclosure

The skill is under 50 lines, has no need for external reference files (none exist in the bundle), and is organized into well-labeled sections (Start Coach, Control an active session, Output, Guardrails), so the simple-skill exception applies and the structure merits the top score.

5 / 5

Total

20

/

20

Passed

Description

92%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: it states concrete capabilities, gives explicit trigger phrases users would naturally say, delimits scope against a sibling skill, and prescribes behavior for ambiguous requests. The only minor gap is a few missing natural synonyms for triggering Coach.

Suggestions

Add one or two natural trigger variants such as "launch Minutes Coach" or "meeting copilot" to broaden keyword coverage for users who don't use the exact lifecycle verbs.

Optionally note in the description that mode selection (sales, discovery, etc.) is part of the start flow so the capability surface is fully enumerated.

DimensionReasoningScore

Specificity

"Start and control Minutes Coach, the separate real-time copilot HUD, with an explicit meeting goal" names the domain and the enumerated triggers ("start Minutes Coach", "pause Minutes Coach", "Minutes Coach status", "stop Minutes Coach") comprehensively cover the skill's full lifecycle action set, matching the comprehensive-coverage anchor rather than the minor-gaps anchor at 4.

5 / 5

Completeness

The description explicitly answers both what ("Start and control Minutes Coach... with an explicit meeting goal") and when ("Use only for explicit Coach or HUD lifecycle requests such as...") with concrete quoted trigger phrases, matching the top anchor; the 'when' is fully explicit, not merely present as at 4.

5 / 5

Trigger Term Quality

Phrases like "start Minutes Coach", "open the Coach HUD", and "coach me live" are natural user utterances with strong coverage, but a few natural variations (e.g., "launch Coach", bare "copilot") are missing, fitting the good-coverage-with-a-few-gaps anchor at 4 rather than comprehensive synonym coverage at 5.

4 / 5

Distinctiveness Conflict Risk

A clear niche is staked out with an explicit disambiguation ("Do not use for requests that explicitly ask the current terminal agent to watch or strategize; those belong to minutes-live-sidekick") and ambiguity handling for "coach me live", giving minimal conflict risk with distinct triggers.

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.

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