gh-assign-issues

Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./docs/skills/gh-assign-issues/SKILL.md

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable, concise, and has a well-sequenced workflow with real validation checkpoints for a batch operation. The main weakness is a dangling reference to a non-existent AGENTS.md file, which undermines progressive disclosure.

Suggestions

Either bundle the referenced AGENTS.md under references/ or remove the "(see AGENTS.md)" pointer so all in-body navigation resolves.

Fix the typo in the final red-flag line ("closclosing references") for a clean closing instruction.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence (no explanation of what GitHub, PRs, or milestones are); every section earns its place, fitting the "lean and efficient" anchor.	3 / 3
Actionability	Provides fully executable `gh` commands with concrete jq filters and copy-paste bash loops (steps 1–3), matching the "fully executable, copy-paste ready" anchor.	3 / 3
Workflow Clarity	The batch operation is clearly sequenced with explicit validation checkpoints — pre-flight screening (step 2), post-change verification of the open count (step 4), and a closing ledger (step 5) — satisfying the feedback-loop requirement for batch operations.	3 / 3
Progressive Disclosure	Sections are well organized and the skill is mostly self-contained, but the body points readers to "AGENTS.md" (line 88) and no such bundle file exists in references/scripts/assets, so the signaled navigation does not resolve.	2 / 3
	Total	11 / 12 Passed

Description

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and occupies a clear niche, but it lacks an explicit "Use when..." trigger clause and broad trigger-term coverage, capping completeness and trigger quality at 2.

Suggestions

Add an explicit "Use when..." trigger clause naming the situations that call for this skill (e.g. triaging a batch of issues into a release milestone).

Broaden trigger terms to include natural user phrasings like "move issues to a release", "triage issues", or "re-point issues after a milestone rename".

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "assign GitHub issues to a milestone and/or owners", "in bulk", "verifying each" — matching the anchor for listing several specific actions.	3 / 3
Completeness	Clearly states what the skill does, but there is no "Use when..." clause or equivalent explicit trigger guidance, which the guidelines say caps completeness at 2.	2 / 3
Trigger Term Quality	Natural terms like "GitHub issues", "milestone", "owners", and "assign" are present, but common variations a user would say (e.g. "move issues to a release", "triage") are missing, and the phrasing "Use to" is not a true trigger clause.	2 / 3
Distinctiveness Conflict Risk	The niche — bulk-assigning GitHub issues to a milestone/owners with verification — is distinct and unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 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: Hmbown/CodeWhale
Path: docs/skills/gh-assign-issues/SKILL.md
Commit: f018d3e

Reviewed: about 14 hours 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.