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. This should trigger for requests such as gh issue list; List GitHub issues; Issues in milestone; GitHub CLI issues; gh issue view comments. Part of cursor-rules-java project
64
75%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/043-planning-github-issues/SKILL.mdQuality
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 skill description that clearly articulates specific capabilities (GitHub CLI issue operations), provides explicit trigger guidance with both a 'Use when' clause and example trigger phrases, and is highly distinctive in its niche. The description is comprehensive without being verbose, covering installation gating behavior and cross-skill handoff. Minor note: it uses second-person implied ('you need') in the opening but this is borderline and doesn't significantly detract.
| 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 stories. Also describes the interactive install gate behavior. | 3 / 3 |
Completeness | Clearly answers both 'what' (verify installation, list issues, fetch bodies/comments, hand off for user stories) and 'when' with explicit 'Use when' clause and a 'This should trigger for' clause listing specific trigger phrases. | 3 / 3 |
Trigger Term Quality | Includes excellent natural trigger terms that users would actually say: 'gh issue list', 'List GitHub issues', 'Issues in milestone', 'GitHub CLI issues', 'gh issue view comments'. Covers both CLI-style and natural language variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — scoped specifically to GitHub CLI (`gh`) issue operations, with clear niche triggers like 'gh issue list' and 'milestone'. The mention of the specific handoff skill (@014-agile-user-story) and project context (cursor-rules-java) further distinguish it. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%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 workflow with a distinctive interactive install gate pattern and appropriate safety constraints around not fabricating data. However, it lacks concrete executable examples (no actual command with sample output, no markdown table template), repeats the interactive gate concept excessively, and misses validation/error-recovery steps in the workflow. The reference file structure is reasonable but unverifiable without bundle files.
Suggestions
Add at least one concrete, copy-paste-ready example showing `gh issue list --json number,title,state,milestone --limit 20` with a sample markdown table output format.
Include an explicit error-recovery step in the workflow for when `gh auth status` fails (e.g., run `gh auth login` and re-verify).
Remove the redundant 'What is covered' bullet list since the workflow steps and constraints already cover the same ground, improving conciseness.
Add a concrete example of the `gh issue view --json body,comments` command with a brief sample of how to format the output for analysis.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph is overly dense and repeats the interactive gate concept multiple times. The 'What is covered' section partially duplicates the workflow and constraints sections. Some tightening would help, but it's not egregiously verbose. | 2 / 3 |
Actionability | The skill mentions specific commands like `gh --version`, `gh auth status`, `gh issue list --json`, and `gh issue view --comments`, but provides no executable code examples, no example markdown table output, and no concrete `--json` field selections or formatting snippets. It describes what to do rather than showing how. | 2 / 3 |
Workflow Clarity | The five workflow steps are clearly sequenced and the interactive gate is emphasized as a stopping point. However, there are no explicit validation checkpoints beyond the initial auth check—no error recovery steps if `gh auth status` fails, no feedback loop if issue listing returns unexpected results, and the chain to another skill lacks detail on what content to pass. | 2 / 3 |
Progressive Disclosure | The skill references a detailed file at `references/043-planning-github-issues.md` and cross-references `@014-agile-user-story` and `112-java-maven-plugins`, which is good structure. However, no bundle files were provided to verify the reference exists, and the main body contains content that could be more concisely summarized if the reference file carried the detail. The 'What is covered' list is somewhat redundant with the workflow. | 2 / 3 |
Total | 8 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jabrena/cursor-rules-java
- Commit
3fa5789
- 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.