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
80
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 defines its scope around GitHub CLI issue operations. It excels in all dimensions: specific actions are enumerated, natural trigger terms are provided with both CLI and conversational variations, both 'what' and 'when' are explicitly addressed, and the niche is distinct enough to avoid conflicts. The description also helpfully mentions behavioral details like the interactive install gate.
| 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 an explicit 'Use when' clause at the start and a 'This should trigger for' clause with specific example 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 with a clear niche around GitHub CLI issue operations. The specific mention of `gh` CLI, markdown tables, milestone filtering, and the handoff to @014-agile-user-story makes it very unlikely to conflict with other skills. | 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 provides a reasonable high-level workflow for GitHub CLI issue operations with a clear interactive gate pattern and appropriate cross-references to other skills. 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 beyond the initial install check. It reads more as a description of what to do than a precise, actionable guide.
Suggestions
Add at least one concrete, copy-paste-ready example showing `gh issue list --json number,title,state,milestone --limit 20` piped into a markdown table format with expected output.
Include a brief example of `gh issue view <number> --json body,comments` with a sample of how to format/summarize the output for analysis.
Add explicit error-handling guidance for common failure modes: auth failure, wrong repo context, milestone not found — with retry steps to form proper feedback loops.
Remove the 'What is covered' bullet list since it largely duplicates the Workflow and Constraints sections, improving conciseness.
| 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 rather than demonstrates. | 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 gate (e.g., what to do if auth fails, if the repo context is wrong, or if the milestone doesn't exist), and no feedback/retry loops for error cases. | 2 / 3 |
Progressive Disclosure | The skill references a detailed file at `references/043-planning-github-issues.md` and cross-references other skills (`112-java-maven-plugins`, `@014-agile-user-story`), which is good structure. However, no bundle files were provided to verify these references exist, and the main body contains some content that could be offloaded (the 'What is covered' list largely duplicates the workflow). The reference is one-level deep and clearly signaled, which is positive. | 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
ef4eba3
- 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.