CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

start-milestone

Transitions a GitHub milestone from planning to active execution. Use when the team is ready to begin a sprint or release cycle — bulk-transitions open issue labels from status:needs-grooming to status:in-progress, updates GitHub Projects V2 Status to In Progress, and confirms before applying changes. Requires milestone number as argument. Use after /group-items-to-milestone.

74

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

93%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-crafted workflow skill body: lean, fully executable, and properly split across reference files. The single notable gap is verification depth — the workflow relies on the script's per-issue reporting and exit code but never instructs re-checking milestone/issue state after the transition, which is the only thing separating it from a top workflow-clarity score.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence: exact MCP tool calls, exact uv run commands with flags, and compact templates, with no explanation of concepts Claude already knows. Every section is functional, matching the anchor for lean and efficient content.

5 / 5

Actionability

Fully executable throughout: 'mcp__plugin_dh_backlog__backlog_list_milestones(state="open")' with parameters, copy-paste bash commands including a --dry-run variant, and a script that 'reports per-issue results, and exits non-zero if any issue fails'. No gaps between instruction and execution.

5 / 5

Workflow Clarity

A clear 6-step sequence with real checkpoints for a batch operation: milestone resolution with fallback list, a user confirmation gate, dry-run preview, and per-issue failure reporting with an explicit error-handling section. Validation is present so the batch-operation cap does not apply, but there is no post-run verification of the final state or fix-retry feedback loop, keeping it below the anchor-5 example.

4 / 5

Progressive Disclosure

The body is a concise workflow overview with well-signaled, one-level-deep references ('API references: milestones.md | projects-v2.md' up top and again in Step 5) and bulk execution delegated to the github_project_setup.py script. Content is appropriately split, matching the anchor for clear overview with one-level references.

5 / 5

Total

19

/

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 description in third-person voice with concrete actions, an explicit use-when trigger, and clear distinction from related skills. The only weakness is that natural user phrasings for invoking the skill (e.g., 'start/kick off the milestone') are implied rather than covered as trigger synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions with exact artifact names — 'bulk-transitions open issue labels from status:needs-grooming to status:in-progress, updates GitHub Projects V2 Status to In Progress, and confirms before applying changes' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both what ('bulk-transitions... labels... updates GitHub Projects V2 Status... confirms before applying changes') and when ('Use when the team is ready to begin a sprint or release cycle'), plus argument requirement and ordering ('Use after /group-items-to-milestone').

5 / 5

Trigger Term Quality

Natural terms like 'GitHub milestone', 'sprint', 'release cycle', and 'start' are present, but common user phrasings such as 'start a milestone', 'kickoff', or 'begin the sprint' are not explicitly covered. Not 5 because a few natural trigger variations are missing; not 3 because coverage goes well beyond minimal keywords.

4 / 5

Distinctiveness Conflict Risk

Highly specific label names (status:needs-grooming, status:in-progress), the Projects V2 field, and the named predecessor skill carve out a clear niche with minimal overlap risk against sibling backlog skills.

5 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 3 suspicious

Warning

Total

14

/

16

Passed

Repository

Jamie-BitFlight/claude_skills

Path

.claude/skills/start-milestone/SKILL.md

Reviewed

Table of Contents

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.