create-milestone

Creates a GitHub milestone on the current repository and returns its number for downstream use. Use when starting a new sprint, release, or theme grouping of backlog items. No args triggers guided intake (title, due date, description); 'quick {title}' skips to description only. Checks for duplicates before creating. Returns milestone number for /group-items-to-milestone.

Quality

83%

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

75%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 skill body is actionable and well-structured with a clear sequenced workflow and validation via the duplicate check. Promoting the wave-ordering guidance to a reference file and adding a retry/feedback loop on errors would lift the remaining dimensions.

Suggestions

Move the Step 2.5 wave-ordering detail (dependency mapping, restart points, description template) into a reference file and keep a brief pointer in SKILL.md to improve progressive disclosure and conciseness.

Replace 'print and stop' error handling with a validate-fix-retry feedback loop (e.g., on API error, surface the response and retry once) to push workflow_clarity toward the top anchor.

Specify how to parse and confirm the created milestone number programmatically rather than relying on scanning an output line, tightening actionability.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient and free of concepts Claude already knows, though the Step 2.5 wave-ordering block is fairly elaborate and could be trimmed or moved to a reference.	4 / 5
Actionability	Provides concrete executable commands (the `uv run …github_project_setup.py milestone create` invocation) and specific MCP calls (`backlog_list_milestones(state="open")`), with only minor gaps in output-handling detail.	4 / 5
Workflow Clarity	Steps 1–4 are clearly sequenced with a duplicate-check validation checkpoint and an error-handling section, but error handling is 'print and stop' rather than a validate-fix-retry feedback loop, so it does not reach the top anchor.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections with signaled external references (MCP tools, the gh script path, downstream slash commands); no bundle files exist, and the sizeable inlined wave-ordering section keeps it just below the clean-overview anchor.	4 / 5
	Total	16 / 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, well-targeted description that crisply states the capability, gives explicit use-when triggers, and distinguishes the skill from neighbors. The only minor gap is slightly thinner coverage of trigger synonyms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Creates a GitHub milestone', 'returns its number', 'Checks for duplicates before creating', and intake modes — giving comprehensive coverage of what the skill does.	5 / 5
Completeness	Explicitly answers both 'what' ('Creates a GitHub milestone… returns its number') and 'when' ('Use when starting a new sprint, release, or theme grouping') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural user phrases are present ('sprint', 'release', 'theme grouping of backlog items', 'milestone'), but a few common synonyms/variations are missing, so it sits just below the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (GitHub milestone creation tied to /group-items-to-milestone) with distinct 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: Jamie-BitFlight/claude_skills
Path: .claude/skills/create-milestone/SKILL.md
Commit: 3e0b2af

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.