CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

group-items-to-milestone

Assign backlog items to a GitHub milestone by bridging per-item files to GitHub Issues. Use when populating a sprint or release milestone, after create-milestone, or when a milestone number is specified with optional P0/P1/P2 or title filter. Creates missing GitHub Issues for selected P0/P1 items, assigns all selected items to the milestone, and updates Project V2 Status to Backlog.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

68%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, actionable workflow document with concrete commands and clear sequencing. The main weakness is missing post-batch verification/feedback loops for a mutating multi-issue operation.

Suggestions

Add a verification step after assignment (e.g., re-run backlog_list_milestones or list the milestone's issues to confirm each selected issue is attached and counts changed) to close the validate→fix→retry loop on this batch mutation.

Add error-handling and retry guidance for the set-milestone and update-status commands, not just issue creation, so partial failures are detectable and recoverable.

Provide a concrete story-format body template in Step 4 (Story / Description / Acceptance Criteria / Context with example phrasing) instead of the "{story body}" placeholder so issue creation is copy-paste ready.

DimensionReasoningScore

Conciseness

Lean and efficient — concrete tool calls, compact selection/report templates, no explanation of concepts Claude already knows. Only minor trimmable redundancy (Step 1's 'If milestone not found… report and stop' is restated in Error Handling).

4 / 5

Actionability

Mostly executable guidance: exact tool calls with arguments (backlog_list_milestones(state="open"), mcp__plugin_dh_backlog__backlog_list) and runnable uv-run commands per step. Minor gap: `--body "{story body}"` is a placeholder and the Story/Description/Acceptance Criteria format is named but not templated.

4 / 5

Workflow Clarity

The 7-step sequence is clearly ordered with pre-flight checks (stop on closed/missing milestone, verify issue state, user confirmation before acting), but this is a batch mutation (bulk issue creation, milestone assignment, status updates) with no post-operation verification that assignments succeeded and no retry loop — 'Issue creation fails: log error per item, continue' is continue-on-error, not a feedback loop — so the batch-operation cap of 3 applies.

3 / 5

Progressive Disclosure

No bundle directories exist; the only references are well-signaled one-level-deep links at the top ('API references: milestones.md | issue-stories.md | projects-v2.md') and all workflow detail is appropriately kept inline at ~110 lines. Minor gap: the links point into another skill's bundle (../gh/references/) — a cross-skill dependency rather than a self-contained bundle.

4 / 5

Total

15

/

20

Passed

Description

88%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 a complete what/when pair and concrete triggers. Keyword coverage is good but not exhaustive of natural synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete, comprehensive actions — 'Creates missing GitHub Issues for selected P0/P1 items, assigns all selected items to the milestone, and updates Project V2 Status to Backlog' — covering the full pipeline (create, assign, status update). No coverage gap that would drop it to anchor 4.

5 / 5

Completeness

Explicitly answers both: what ('Assign backlog items to a GitHub milestone by bridging per-item files to GitHub Issues…') and when ('Use when populating a sprint or release milestone, after create-milestone, or when a milestone number is specified with optional P0/P1/P2 or title filter') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural keyword coverage — 'populating a sprint or release milestone', 'backlog', 'P0/P1/P2', 'milestone number' — but misses common synonyms a user might say (e.g., 'roadmap', 'epic', 'release planning'), so it is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

Clear niche (milestone population via backlog-file-to-issue bridging) with distinct triggers, but closely related sibling skills (create-milestone, groom-milestone referenced in the workflow) create minor overlap risk.

4 / 5

Total

18

/

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/group-items-to-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.