043-planning-github-issues

Use when you need the GitHub CLI (`gh`) to verify installation, list issues (all or by milestone) as markdown tables, fetch issue bodies and comments for analysis, or hand off to @014-agile-user-story when creating user stories from GitHub threads. Uses an interactive install gate — if `gh` is missing, ask whether to show installation guidance before any issue commands. Part of the skills-for-java project

Quality

78%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/043-planning-github-issues/SKILL.md

Quality

Discovery

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong description that clearly articulates specific capabilities (listing issues, fetching comments, install verification), includes explicit 'Use when' trigger guidance, and uses natural keywords users would employ. The cross-reference to a sibling skill and the install gate behavior add useful distinctiveness. Minor note: it uses imperative/instructional voice ('Use when...') rather than third person declarative, but this is the standard pattern shown in the rubric's good examples.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: verify installation, list issues as markdown tables, fetch issue bodies and comments, hand off to another skill for user story creation. Also describes the interactive install gate behavior.	3 / 3
Completeness	The description opens with an explicit 'Use when' clause that clearly answers both what (verify installation, list issues, fetch issue data, hand off for user stories) and when (when needing gh CLI for these specific tasks). Both dimensions are well-covered.	3 / 3
Trigger Term Quality	Includes strong natural trigger terms users would say: 'GitHub CLI', 'gh', 'list issues', 'milestone', 'markdown tables', 'issue bodies', 'comments', 'user stories', 'GitHub threads'. Good coverage of variations and natural language.	3 / 3
Distinctiveness Conflict Risk	Clearly scoped to GitHub CLI (`gh`) operations specifically around issues, milestones, and the handoff to a named sibling skill (@014-agile-user-story). The mention of the install gate and specific project context ('skills-for-java') further distinguishes it from generic GitHub or issue-tracking skills.	3 / 3
	Total	12 / 12 Passed

Implementation

57%

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

The skill establishes a clear behavioral pattern (interactive install gate, auth check, issue operations, chaining to another skill) and uses good progressive disclosure by deferring details to a reference file. However, it lacks concrete executable examples—no actual command with flags and expected output is shown—and the workflow steps are described in prose rather than a clear numbered sequence. The opening paragraph is also somewhat verbose and repetitive with the constraints section.

Suggestions

Add at least 2-3 concrete, copy-paste ready command examples (e.g., `gh issue list --state open --milestone 'v1.0' --json number,title,state` with expected markdown table output format)

Replace the prose-based workflow description with a numbered step sequence including explicit validation checkpoints (e.g., 1. Check `gh --version` → if missing, STOP and ask → 2. Verify `gh auth status` → if not authenticated, guide login → 3. List/view issues)

Remove redundancy between the opening paragraph and the Constraints section regarding the interactive gate pattern—state it once clearly in the workflow steps

Dimension	Reasoning	Score
Conciseness	The opening paragraph is dense and repetitive—it restates the interactive gate concept multiple times across the intro and constraints. Some phrases like 'consultative pattern in 112-java-maven-plugins' add context but the overall content could be significantly tightened. However, it doesn't over-explain basic concepts Claude already knows.	2 / 3
Actionability	The skill mentions specific commands (`gh --version`, `gh auth status`, `gh issue list --json`, `gh issue view --comments`, `gh api`) but never provides executable examples with actual flags, JSON field selections, or markdown table rendering code. It describes what to do rather than showing copy-paste ready commands.	2 / 3
Workflow Clarity	There is a clear implied sequence (install gate → auth check → list/view issues → chain to 014), and the interactive gate is emphasized as a mandatory checkpoint. However, the steps are not explicitly numbered or sequenced, validation checkpoints beyond the install gate are implicit, and there's no error recovery guidance for auth failures or API errors.	2 / 3
Progressive Disclosure	The skill provides a clear overview with well-organized sections (intro, constraints, when to use, reference) and points to a single reference file for detailed guidance and examples. This is a clean one-level-deep reference structure with clear navigation.	3 / 3
	Total	9 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/cursor-rules-java
Commit: 81b047f

Reviewed: about 24 hours 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.