CtrlK
BlogDocsLog inGet started
Tessl Logo

043-planning-github-issues

Use when you need GitHub CLI (`gh`) installation/authentication guidance and a sanitized GitHub issue inventory workflow. The agent does not ingest GitHub issue or milestone output directly; it asks the user for sanitized issue summaries before analysis or @014-agile-user-story handoff. This should trigger for requests such as GitHub issue summary workflow; GitHub CLI setup for issues; Prepare sanitized GitHub issue inventory. Part of cursor-rules-java project

66

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

The body is a well-structured overview with clean progressive disclosure to one real reference file, but it is held back by repetition of the sanitized-ingestion constraint, ask-based rather than executable workflow steps, and validation/error detail that sits only in the reference.

Suggestions

State the "no direct ingestion / sanitized-only" constraint once in the Constraints section and reference it from the workflow steps instead of restating it in the intro, the "What is covered" list, and every step.

Surface a brief error-recovery/feedback loop in the body (or explicitly point to the reference's Step 6) so the workflow's validation checkpoints are self-contained.

Remove or condense the "When to use this skill" section, since it duplicates the trigger phrases already present in the frontmatter description.

DimensionReasoningScore

Conciseness

Mostly efficient but the "no direct ingestion / sanitized" constraint is restated across the intro, the "What is covered" list, Constraints, and each workflow step, and "When to use" duplicates the frontmatter triggers — it could be tightened.

2 / 3

Actionability

Concrete commands are present (`gh --version`, `gh auth status`, `gh auth login`, `--repo`), but the core workflow is ask-based and the fully executable detail (per-OS install steps, error handling) lives in the reference rather than the body.

2 / 3

Workflow Clarity

The five steps are clearly sequenced with an explicit stop/ask/wait gate checkpoint, but error-recovery feedback loops and per-step validation are in the reference, not the body, so it stops short of the top anchor.

2 / 3

Progressive Disclosure

The body is an overview pointing to a single, clearly signaled, verified one-level-deep reference (references/043-planning-github-issues.md), matching the clean overview anchor.

3 / 3

Total

9

/

12

Passed

Description

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.

The description is strong across all four dimensions: it states concrete capabilities, uses natural trigger terms, explicitly pairs what-and-when, and occupies a distinctive niche. It is third-person throughout, incurring no voice penalty, though it is somewhat verbose for a trigger description.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "GitHub CLI (`gh`) installation/authentication guidance", "sanitized GitHub issue inventory workflow", and "asks the user for sanitized issue summaries...@014-agile-user-story handoff" — matching the top anchor.

3 / 3

Completeness

Explicitly answers both what (install/auth guidance + sanitized inventory workflow + handoff) and when ("Use when you need..." and "This should trigger for requests such as...").

3 / 3

Trigger Term Quality

Good coverage of natural terms users would say ("GitHub CLI", "gh", "installation/authentication", "GitHub CLI setup for issues"), beyond the level-2 "some relevant keywords" anchor.

3 / 3

Distinctiveness Conflict Risk

Carves a clear niche (GitHub CLI setup for issues + sanitized issue inventory) with distinct triggers, unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
jabrena/cursor-rules-java
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.