CtrlK
BlogDocsLog inGet started
Tessl Logo

gh-assign-issues

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

72

Quality

88%

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

92%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 high-quality, executable batch-operation skill with strong validation checkpoints and lean prose. The only blemish is a typo and minor redundancy in the closing red-flags list.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's familiarity with gh; every section earns its place. A single typo ("closclosing" on the last line) and a few slightly redundant cautionary restatements keep it just below the lean anchor of 5.

4 / 5

Actionability

Fully executable gh commands with jq filters, PR-vs-issue screening, and an idempotent edit loop with per-issue ok/FAIL reporting — copy-paste ready and covering the common cases.

5 / 5

Workflow Clarity

A batch operation with an explicit pre-flight screening checkpoint (skip PRs/closed), a post-edit verification step (open-count delta + spot-check), and a feedback path for silent failures, satisfying the batch-validation requirement.

5 / 5

Progressive Disclosure

Self-contained single-file skill with well-organized sections (When to use, Workflow, Red flags) and no need for external references; navigation is clear and content is appropriately scoped for a focused skill.

5 / 5

Total

19

/

20

Passed

Description

83%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 tight, third-person description that states concrete capabilities and includes an explicit trigger clause. It is specific and distinctive, with only minor gaps in trigger-term breadth and situational when-guidance.

Suggestions

Broaden trigger terms with natural synonyms users say (e.g. "triage", "backlog grooming", "retarget issues to a release", "re-point") to lift trigger_term_quality.

Add a concrete situational trigger (e.g. "Use when a milestone was renamed/created and its issues need re-pointing, or after triage to assign owners in bulk") to reach the explicit-when anchor.

DimensionReasoningScore

Specificity

Names multiple concrete actions — "assign GitHub issues to a milestone and/or owners in bulk, verifying each" — covering milestone retargeting, owner assignment, bulk operation, and per-issue verification.

5 / 5

Completeness

A clear "Use to..." clause gives both the what and a trigger, but the when is generic rather than keyed to concrete situational triggers, so it sits just below the explicit-trigger-phrases anchor of 5.

4 / 5

Trigger Term Quality

Natural terms like "GitHub issues", "milestone", "assign... owners", and "in bulk" are present, but common synonyms such as "triage", "backlog", "retarget", or "re-point" are missing.

4 / 5

Distinctiveness Conflict Risk

The niche is narrow and explicit — bulk milestone/assignee assignment with verification — making conflict with unrelated skills minimal.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Hmbown/CodeWhale
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.