gh-assign-issues

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

Quality

79%

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

Fix and improve this skill with Tessl

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

Quality

Content

88%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 body is highly actionable with executable commands and a well-sequenced, validated workflow appropriate for a batch operation. It is concise and well-structured, with only minor opportunities to tighten prose.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence with `gh`, with no padding about GitHub concepts; a few prose sentences in the red-flags section restate workflow guidance and could be trimmed.	4 / 5
Actionability	Each step supplies copy-paste-ready, executable `gh api` / `gh issue view` / `gh issue edit` commands covering the common cases, including per-issue success reporting.	5 / 5
Workflow Clarity	The five-step workflow is clearly sequenced with explicit validation checkpoints (pre-flight screening in step 2, open-count verification in step 4) and a feedback loop for a batch operation.	5 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections (When to use, Workflow, Red flags) with no nested references; it is self-contained but slightly over 50 lines, so it falls just short of the ideal split.	4 / 5
	Total	18 / 20 Passed

Description

70%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.

The description is concrete and distinctive, naming specific actions and natural trigger terms. Its main weakness is the absence of an explicit "Use when..." scenario, which caps completeness.

Suggestions

Add an explicit "Use when..." clause naming the triage/release scenarios, e.g. "Use when you have a list of issue numbers to move into a release milestone or assign to owners."

Include a couple of natural synonyms (e.g. "triage", "re-point") to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	"assign GitHub issues to a milestone and/or owners in bulk, verifying each" names several concrete actions (milestone, owners, bulk, verify) but does not enumerate the full range of related operations.	4 / 5
Completeness	The "what" is clear (assign issues to milestone/owners in bulk, verifying each), but there is no explicit "Use when..." trigger scenario, so completeness is capped at 3 per the missing-trigger guidance.	3 / 5
Trigger Term Quality	Natural terms like "assign GitHub issues", "milestone", and "owners in bulk" are present and would be said by users, though a few common synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	"assign GitHub issues to a milestone and/or owners in bulk" carves a clear niche with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	16 / 20 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: 21282f1

Reviewed: 6 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.