Name: minutes-x1-closeout
Rating: 71.2 (1 reviews)
Author: silverstein

minutes-x1-closeout

Prepare a sourced Minutes meeting outcome for human-governed closeout of existing X1 work. Use when the user wants a meeting decision or commitment to close, defer, escalate, or retire a specific X1 coordination thread. Never use it to infer settlement, move money, contact anyone, or close X1 work automatically.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

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

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.

An exceptionally concrete, fail-closed workflow with strong validation checkpoints and unambiguous steps. The only trimmable content is a handful of explanatory trust-rationale sentences, and the body is long enough that moving the fail-closed handling to a reference file would ease the token budget.

Suggestions

Trim the explanatory asides about why hashing and participant counts don't prove verification; the operative rules (audience stays unbound, never send source_meeting) stand on their own.

Consider moving the Fail-closed handling section into a reference file to keep SKILL.md as a lean overview, since the body is ~88 lines.

Dimension	Reasoning	Score
Conciseness	Dense, prescriptive steps with no explanations of concepts Claude already knows, but a few trust-rationale asides ('Hashing the source reference minimizes it; it doesn't make the source X1-verified', 'The participant count doesn't prove who attended') could be trimmed.	4 / 5
Actionability	Fully concrete guidance for an instruction-only skill: exact MCP calls with parameters ('get_meeting_insights with include_restricted: false'), a complete sourceProposal field spec with literal values, and exact expected return fields to verify.	5 / 5
Workflow Clarity	Six clearly sequenced steps with explicit validation checkpoints ('This must return writesPerformed: false... If any is missing, stop and keep the work open'), ambiguity handling (zero or multiple matching threads asks the user), and a fail-closed section with stale/duplicate/conflicted recovery actions.	5 / 5
Progressive Disclosure	Well-organized sections (Required connections, Workflow, Fail-closed handling) with no buried references and nothing inlined that clearly belongs in a separate file, but at ~88 lines it exceeds the under-50-line simple-skill exception and the fail-closed detail could live in a reference file.	4 / 5
	Total	18 / 20 Passed

Description

87%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 with an explicit Use-when trigger clause, concrete disposition verbs, and clear negative boundaries. Its only weakness is reliance on product-specific jargon (Minutes, X1, coordination thread) that may not match how users naturally phrase requests.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ('human-governed closeout of existing X1 work', 'close, defer, escalate, or retire a specific X1 coordination thread'), with minor gaps such as the proposal-drafting artifacts it produces.	4 / 5
Completeness	Explicitly answers both what ('Prepare a sourced Minutes meeting outcome for human-governed closeout of existing X1 work') and when ('Use when the user wants a meeting decision or commitment to close, defer, escalate, or retire...') with concrete trigger phrases, plus an explicit never-use boundary.	5 / 5
Trigger Term Quality	Good natural trigger phrases ('meeting decision', 'commitment', 'close, defer, escalate, or retire') that a user would plausibly say, though the vocabulary is dominated by the niche 'Minutes'/'X1' product terms and misses a few everyday synonyms.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Minutes-to-X1 closeout handoff) with distinct triggers, and the 'Never use it to infer settlement, move money, contact anyone, or close X1 work automatically' clause sharply limits wrong-skill activation.	5 / 5
	Total	18 / 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-x1-closeout/SKILL.md
Commit: 5fbe77b

Reviewed: 6 days 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.