issue-management

Manage GitHub Issues 2.0 relationships with gh CLI: parent issues, sub-issues, blocked-by, and blocking links.

Quality

86%

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

Quality

Content

100%

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

The body is exemplary: lean, fully actionable, and well-organized, with executable commands and a safe workflow that includes validation checkpoints and error recovery.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: it never explains what GitHub Issues or gh are, and each line (including the non-obvious '--add-sub-issue' move semantics and the blocking/blocked-by equivalence) earns its place.	3 / 3
Actionability	It provides fully executable, copy-paste-ready 'gh' commands with concrete issue numbers, URLs, and comma-separated lists, plus explicit JSON field names for scripting.	3 / 3
Workflow Clarity	It includes a preflight validation checkpoint with a recovery action ('If those flags are missing, update gh') and a numbered 'Safe workflow' with an explicit verify step, giving clear sequencing and a feedback loop.	3 / 3
Progressive Disclosure	With no bundle files present, the content is appropriately organized into clear single-level sections (reference format, parent/sub-issue, blocked-by/blocking, inspecting, safe workflow) with no nested references.	3 / 3
	Total	12 / 12 Passed

Description

72%

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 distinct, naming the concrete relationship types it manages with natural trigger terms, but it lacks an explicit 'when to use' clause, which caps its completeness.

Suggestions

Append an explicit trigger clause such as 'Use when creating, editing, inspecting, or removing links between GitHub issues (parent/sub-issue, blocked-by, blocking).' to lift completeness to 3.

Replace the single verb 'Manage' with a short enumerated action list (e.g., 'create, edit, inspect, and remove') to better satisfy the specificity anchor for multiple concrete actions.

Dimension	Reasoning	Score
Specificity	The description names a concrete domain (GitHub Issues 2.0 relationships) and lists four specific relationship types, but collapses all actions into the single verb 'Manage' rather than enumerating distinct actions like create, edit, inspect, or remove.	2 / 3
Completeness	It clearly answers 'what' the skill does, but there is no 'Use when...' clause or equivalent explicit trigger guidance in the description field, so completeness is capped at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	It uses natural terms users would actually say — 'parent issues', 'sub-issues', 'blocked-by', 'blocking links', 'GitHub Issues' — giving good coverage of how the need is phrased in practice.	3 / 3
Distinctiveness Conflict Risk	The niche is sharply defined — managing Issues 2.0 relationship links via the gh CLI — making it clearly distinguishable 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: remotion-dev/remotion
Path: .agents/skills/issue-management/SKILL.md
Commit: 1b58387

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