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

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 tight, fail-closed procedural spec with exact tool calls, field mappings, and validation checkpoints — highly actionable and clearly sequenced. Its only weaknesses are minor redundant safety restatements and a single-file structure that, while well-organized, doesn't leverage progressive disclosure via references.

Suggestions

Consolidate the repeated hashing/audience and 'don't truncate/paraphrase' constraints into a single canonical statement referenced once, to trim conciseness redundancy.

Consider extracting the Fail-closed handling cases into a short references file (e.g. FAIL_CLOSED.md) to model one-level-deep progressive disclosure and lift the body under the simple-skill line.

Add a brief one-line recap of the required MCP connections at the top of the Workflow section so the precondition is co-located with the steps that depend on it.

Dimension	Reasoning	Score
Conciseness	The body is dense and procedural with no concept over-explanation (no 'what is MCP/SHA-256' filler), but several safety constraints are restated across steps (e.g. hashing/audience and 'don't truncate'), so it is efficient with minor trimmable repetition rather than perfectly lean.	4 / 5
Actionability	Fully actionable instruction-only guidance: exact tool calls with parameters (Minutes `get_meeting_insights` with `include_restricted: false`, X1 `draft_coordination_closeout`), exact field mappings, schema names, and local SHA-256 computations — no code is expected for this instruction skill and the guidance is copy-ready.	5 / 5
Workflow Clarity	A clearly sequenced 1–6 workflow with explicit validation checkpoints (step 5's "If any is missing, stop and keep the work open") and a fail-closed section providing feedback loops for stale/duplicate/conflicted states, satisfying the top anchor for a risky operation.	5 / 5
Progressive Disclosure	No bundle files exist and the content is well-organized into Required connections, Workflow, and Fail-closed handling sections; it scores 4 rather than 5 because the body exceeds the ~50-line simple-skill threshold and offers no one-level-deep references to split into, so structure is good but not the split/overview pattern the 5 anchor describes.	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 sharply scoped, third-person description that answers both what and when with concrete triggers and a clear anti-trigger boundary. It is just short of maximum specificity and trigger-term breadth only because the niche is intentionally narrow.

Dimension	Reasoning	Score
Specificity	Names the domain (Minutes/X1 closeout) and several concrete actions — "Prepare a sourced Minutes meeting outcome" and "close, defer, escalate, or retire a specific X1 coordination thread" — with only minor coverage gaps, fitting the 'lists several specific actions' anchor rather than the comprehensive 5.	4 / 5
Completeness	It 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…") with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Natural trigger phrases like "meeting decision or commitment to close, defer, escalate, or retire a specific X1 coordination thread" give good keyword coverage; it stops short of the 5 because the niche admits few synonyms/extensions.	4 / 5
Distinctiveness Conflict Risk	The narrow Minutes-to-X1 closeout niche plus the explicit "Never use it to infer settlement, move money, contact anyone, or close X1 work automatically" boundary yields a clear niche with minimal conflict risk.	5 / 5
	Total	18 / 20 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: .agents/skills/minutes/minutes-x1-closeout/SKILL.md
Commit: 2d8379f

Reviewed: 3 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.