Tessl • The management layer for AI agent skills

An excellent operational skill: executable commands, strong pre-flight and post-hoc validation for a batch operation, and no basic-concept padding. Its only weaknesses are mild redundancy between the red-flags section and the workflow steps, and the absence of any trigger guidance carried over from the description.

Dimension	Reasoning	Score
Conciseness	The body is lean and operational — every section adds non-obvious knowledge (silent no-op on bad milestone titles, PR-vs-issue detection via the url, idempotent edits) rather than explaining concepts Claude already knows. Minor trimming is possible: the "Red flags / don't" section restates several workflow points (title guessing, PR screening, step-4 verification), which keeps it below 5.	4 / 5
Actionability	Fully executable copy-paste commands: real `gh api` and `gh issue view` calls with concrete `--jq` filters, a loop with per-issue success/failure handling, and explicitly marked placeholders ("# substitute the real issue numbers", "add --add-assignee handle"). The common cases (bulk milestone assignment, owner assignment) are covered specifically.	5 / 5
Workflow Clarity	A clear five-step sequence with explicit validation checkpoints: milestone title confirmation with open-count baseline, pre-flight PR/state screening, per-issue success reporting, post-change verification via open-count delta and spot-checks, and a final ledger. Error-recovery guidance (stop and ask if milestone missing; FAIL message enumerating likely causes) is present, so the batch-operation cap at 3 does not apply.	5 / 5
Progressive Disclosure	Well-organized sections (When to use, Workflow, Red flags) with no nested references and no bundle files to mis-route — appropriate for a single cohesive procedure. It falls short of 5 because at ~93 lines the red-flags section duplicates workflow content that could be consolidated, and the simple-skill exception is framed for skills under 50 lines.	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.

A concise, distinct description with concrete actions and natural trigger terms, but it completely lacks a "Use when…" clause, capping completeness. Adding one or two trigger conditions would lift it substantially.

Suggestions

Add a "Use when…" clause, e.g. "Use when you have a list of issue numbers from triage to move into a release milestone or assign to owners."

Include common synonyms such as "assignees" or "triage" so users' natural phrasing matches the description.

Optionally name the retargeting use case ("re-point issues after a milestone rename") to cover the body's second scenario.

Dimension	Reasoning	Score
Specificity	Names the domain ("GitHub issues") and several concrete actions — "assign … to a milestone and/or owners", "in bulk", "verifying each" — matching the anchor for several specific actions with minor gaps. It falls short of 5 because coverage is compact and omits retargeting/re-pointing variations that the body supports.	4 / 5
Completeness	The "what" is clear (bulk milestone/owner assignment with verification), but there is no "Use when…" clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 4 because the "when" is entirely absent rather than merely under-specified.	3 / 5
Trigger Term Quality	Contains natural terms a user would say when needing this skill: "assign", "GitHub issues", "milestone", "owners", "bulk". A few natural synonyms are missing ("triage", "assignees", "re-point issues"), placing it at good-but-not-comprehensive coverage rather than 5.	4 / 5
Distinctiveness Conflict Risk	A clear niche — bulk milestone/owner assignment of GitHub issues — with distinct trigger terms and minimal overlap with adjacent skills (commit messages, releases, general gh usage). Not lower: no generic phrasing that would attract the wrong skill.	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
Revision: ff466b2

Reviewed: 23 days ago

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.

gh-assign-issues

Table of Contents

Is this your skill?