minutes-tag

Lightweight outcome tagging for meetings — won, lost, stalled, great, or noise. Use whenever the user says "tag this meeting", "mark that as a win", "that one was a loss", "tag yesterday's call as stalled", "mark this great", "that meeting was noise", "label that meeting", or any time they describe a meeting outcome in passing. Tagging takes 5 seconds and unlocks /minutes-mirror correlation analysis — the more meetings get tagged, the smarter mirror gets at telling the user what behavior patterns lead to wins. Surface this skill any time the user mentions a meeting result, win, loss, or wasted time.

Quality

93%

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

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.

A well-structured, highly actionable skill body with clear phased workflow, executable commands, a real bundled helper script, and explicit validation/error-handling. The main improvement opportunity is tightening explanatory prose to better honor the skill's own speed-first philosophy.

Suggestions

Tighten the repeated speed-philosophy prose (e.g., 'Don't be precious about it', 'that defeats the speed promise', 'it breaks the speed promise') into a single concise rationale to reduce token load.

Condense the lifetime-nudge marker-file explanation; the mechanism can be stated in one line without the surrounding justification.

Consider moving the extended 'What the script guarantees' bullet list into the script's own docstring or a reference file, keeping SKILL.md focused on invocation.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and action-oriented, but the ~120-line body for a '5-second' tagging skill carries some justificatory prose (the speed philosophy repeated, the lifetime-nudge mechanism explained in detail) that could be trimmed without losing guidance value.	4 / 5
Actionability	Fully executable throughout: concrete `minutes list`/`minutes search` commands, a real bundled `tag_apply.py` invocation with full argument signature, and specific note-parsing examples covering common cases.	5 / 5
Workflow Clarity	Five clearly sequenced phases with an explicit validation checkpoint in Phase 5 (`minutes get` parseability check) and error-recovery guidance, satisfying the destructive-operation validation requirement.	5 / 5
Progressive Disclosure	Well-organized into phases and gotchas with the fragile frontmatter-editing logic appropriately externalized into a single one-level-deep bundled script (scripts/tag_apply.py) that is clearly signaled and exists on disk.	5 / 5
	Total	19 / 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.

A strong, third-person description that clearly states the skill's purpose and gives extensive natural trigger phrases covering many user phrasings. The only minor weakness is that the core action is a single verb (tagging) with value variations rather than multiple distinct actions.

Dimension	Reasoning	Score
Specificity	Names the domain ('outcome tagging for meetings') and the concrete outcome values (won, lost, stalled, great, noise), but the underlying action is singular (tagging) rather than multiple distinct verbs, so it sits just below the comprehensive multi-action anchor.	4 / 5
Completeness	Explicitly answers both what ('Lightweight outcome tagging for meetings') and when ('Use whenever the user says...', 'Surface this skill any time the user mentions a meeting result, win, loss, or wasted time') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural-language triggers with many synonyms and phrasings users would actually say ('tag this meeting', 'mark that as a win', 'that meeting was noise', 'label that meeting', 'tag yesterday's call as stalled').	5 / 5
Distinctiveness Conflict Risk	Clear niche (meeting outcome tagging tied to /minutes-mirror) with distinct, outcome-specific triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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-tag/SKILL.md
Commit: a9a4a8b

Reviewed: 1 day 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.