SKILLEMALL.ai

CD 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.

Jamie-BitFlight/claude_skills Claude Code author: Jamie-BitFlight MIT 1 file body ≈ 1 013 tokens Open the sourcegithub.com↗ analyzed 8 d ago

Assign backlog items to a GitHub milestone by bridging per-item files to GitHub Issues.

As a process D 48/100 · Unfinished process — References files that are not bundled: ../gh/references/milestones.md, ../gh/references/issue-stories.md, ../gh/references/projects-v2.md

ProcedureGitHubOperations and projectstype and topics are labelled automatically from the skill text
JSON
Technical rating
C
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
72
Run on models
none yet
Process rating
D
48/100
Unfinished process
References files that are not bundled: ../gh/references/milestones.md, ../gh/references/issue-stories.md, ../gh/references/projects-v2.md
Tools and files w 18
0
Inputs and preconditions w 11
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../gh/references/milestones.md
  • warning missing-ref reference to a missing file: ../gh/references/issue-stories.md
  • warning missing-ref reference to a missing file: ../gh/references/projects-v2.md

Process rating: all ten parameters 48/100

Will not run. References files that are not bundled: ../gh/references/milestones.md, ../gh/references/issue-stories.md, ../gh/references/projects-v2.md
  • 0Tools and files. 3 referenced file(s) missing: ../gh/references/milestones.md, ../gh/references/issue-stories.md, ../gh/references/projects-v2.md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 40Result and completion. Does not say what the result is
  • 50Failures and branches. 0 branches, has a failure section
  • 100Steps. 9 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1013 tokens
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 385: enough signal without eating the budget
  • +4Structure: 11 headings
  • +3Step-by-step instructions: 9 items
  • +4Has examples (6 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.