CtrlK
BlogDocsLog inGet started
Tessl Logo

gh-create-issue

Use when user wants to create a GitHub issue for the current repository. Must read and follow the repository's issue template format.

68

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 delivers concrete, executable gh CLI guidance organized into a clear five-step workflow with a confirmation gate, and appropriately avoids bundle files for a single-purpose skill. Tightening the duplicated mktemp explanation and the restated Notes would improve token efficiency.

DimensionReasoningScore

Conciseness

The body is mostly executable commands with little conceptual padding, but the mktemp pattern is shown in both Step 4 and Step 5 and the Notes section restates guidance already given in the workflow, giving minor over-explanation that could be trimmed.

4 / 5

Actionability

It provides copy-paste ready, fully executable commands (mktemp, heredoc body construction, gh issue create with --title/--body-file/--label/--template/--web, rm cleanup) covering both the labeled and unlabeled cases, matching the anchor for fully executable guidance covering common cases.

5 / 5

Workflow Clarity

Five steps are clearly sequenced with a preview/confirmation checkpoint before creation, but there is no explicit error-recovery feedback loop after the gh issue create call, leaving it just short of the full validation-and-feedback anchor.

4 / 5

Progressive Disclosure

Content is well organized into a numbered workflow and a Notes section with no nested references and no bundle files needed, but the body slightly exceeds the simple-skill threshold and carries some inline redundancy rather than being optimally split, fitting good-but-not-ideal structure.

4 / 5

Total

17

/

20

Passed

Description

82%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 well-formed: it states a concrete purpose, includes an explicit 'Use when' trigger, and is scoped narrowly enough to avoid overlap with other skills. Its only weakness is limited action breadth, which is largely inherent to a single-purpose skill.

DimensionReasoningScore

Specificity

Names the domain ('create a GitHub issue') and a concrete supporting action ('Must read and follow the repository's issue template format'), but lists only 1-2 actions rather than several, matching the anchor for naming a domain with limited concrete actions.

3 / 5

Completeness

It explicitly answers both what ('create a GitHub issue ... Must read and follow the repository's issue template format') and when ('Use when user wants to create a GitHub issue for the current repository') with a concrete 'Use when' trigger clause, matching the anchor that requires explicit what and when with concrete triggers.

5 / 5

Trigger Term Quality

Natural trigger phrases like 'create a GitHub issue', 'current repository', and 'issue template format' appear, but common synonyms such as 'file/open/report an issue', 'bug report', or 'feature request' are missing, fitting good-but-not-comprehensive keyword coverage.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche scoped to GitHub issue creation against repo-specific templates, with distinct triggers that are unlikely to fire for unrelated skills, matching the anchor for a clear niche with minimal conflict risk.

5 / 5

Total

17

/

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
CherryHQ/cherry-studio
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.