CtrlK
BlogDocsLog inGet started
Tessl Logo

issue-management

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

65

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/issue-management/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 throughout, well-organized into clear sections, and includes a verification step in its workflow; its main weaknesses are minor trimmable prose and the absence of an explicit error-recovery feedback loop.

DimensionReasoningScore

Conciseness

The body is code-driven and mostly lean, but lines like "Choose the command based on which issue you are already editing" and the "Equivalent mental model" restatement could be trimmed without losing guidance.

4 / 5

Actionability

Every section provides copy-paste-ready, executable `gh issue` commands (e.g., `gh issue edit 123 --parent 100`, `gh issue view <number> --json parent,subIssues,...`) covering the common create/edit/inspect cases.

5 / 5

Workflow Clarity

The "Safe workflow" section gives a clear numbered sequence with a verification checkpoint (step 3), but it lacks an explicit validate→fix→retry feedback loop for the destructive remove operations.

4 / 5

Progressive Disclosure

No bundle files exist and none are needed; the single-purpose skill is organized into clearly headed sections (reference format, parent/sub-issue, blocked-by/blocking, inspecting, safe workflow), satisfying the simple-skill exception for well-organized self-contained content.

5 / 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 specific and clearly niched, naming the tool and four concrete relationship types, but it omits any explicit "when to use" trigger guidance, which the rubric caps at completeness 3.

Suggestions

Add a "Use when..." clause naming trigger phrases (e.g., linking parent/sub-issues, marking issues blocked-by or blocking another issue).

Expand the single verb "Manage" into the actual operations (create, edit, inspect, remove) to lift specificity toward 5.

Include a synonym such as "issue dependencies" to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Enumerates concrete capabilities — "parent issues, sub-issues, blocked-by, and blocking links" — with the tool "gh CLI", but relies on the single generic verb "Manage" rather than multiple distinct action verbs, leaving minor gaps versus a comprehensive list.

4 / 5

Completeness

The description gives a clear "what" ("Manage GitHub Issues 2.0 relationships ...") but contains no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Natural terms a user would say ("parent issues", "sub-issues", "blocked-by", "blocking", "gh CLI") are present and relevant, though synonyms like "issue dependencies" or "link issues" are absent.

4 / 5

Distinctiveness Conflict Risk

"GitHub Issues 2.0 relationships" scoped to specific link types via "gh CLI" carves a clear niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

16

/

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
remotion-dev/remotion
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.