minutes-record

Start or stop recording a meeting, call, or voice memo. Use this whenever the user says "record", "start recording", "capture this meeting", "stop recording", "I'm in a meeting", "take notes on this call", or wants to transcribe live audio. Also use when they ask about recording status or want to know if something is being recorded.

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body is a tight, actionable reference: concrete commands with expected outputs, a clear start/stop workflow with status feedback, and one well-signaled bundled reference for the deep audio-device setup. It avoids both concept-explaining fluff and deeply nested references.

Dimension	Reasoning	Score
Conciseness	The body is lean and task-focused with no explanations of concepts Claude already knows; prose like the 0600-permission rationale and mid-meeting live-transcript note each earn their place rather than padding.	3 / 3
Actionability	Fully executable, copy-paste-ready commands throughout (`minutes record --title`, `minutes transcript --since 5m`, `minutes setup --parakeet`) with expected JSON outputs shown, matching the top anchor.	3 / 3
Workflow Clarity	The start -> (optional status/live transcript) -> stop sequence is clearly laid out, the stop step enumerates its four sub-steps, and the Gotchas section supplies error-recovery feedback (stale PID, 'already recording').	3 / 3
Progressive Disclosure	A well-organized overview keeps BlackHole detail out of the main body and points to a single, clearly signaled, one-level-deep reference (`references/audio-devices.md`), which exists in the bundle as referenced.	3 / 3
	Total	12 / 12 Passed

Description

100%

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 concrete, trigger-rich, and explicitly pairs capability with usage conditions in the third-person/imperative style of the rubric's good examples. It is one of the stronger reference-style descriptions, fully resolving what and when.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Start or stop recording a meeting, call, or voice memo', 'transcribe live audio', and checking 'recording status' — matching the anchor for several specific concrete actions rather than a single vague domain.	3 / 3
Completeness	Clearly answers both 'what' (record/transcribe meeting, call, or voice memo) and 'when' via an explicit 'Use this whenever the user says...' clause plus a status-query case, matching the top anchor.	3 / 3
Trigger Term Quality	Dense natural phrasings users would actually say ('record', 'start recording', 'capture this meeting', 'I'm in a meeting', 'take notes on this call') give strong coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear audio-recording/transcription niche with distinctive triggers unlikely to collide with other skills; not generic enough to conflict broadly.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

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
Path: .opencode/skills/minutes-record/SKILL.md
Commit: 7a61dd5

Reviewed: about 18 hours ago

Table of Contents

Discovery Implementation Validation

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.