CtrlK
BlogDocsLog inGet started
Tessl Logo

create-github-issue

Create GitHub issues using the gh CLI. Use when the user wants to create a new issue, report a bug, request a feature, or create a task in GitHub. Trigger keywords - create issue, new issue, file bug, report bug, feature request, github issue.

67

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.

A well-structured, highly actionable skill body with copy-paste gh CLI templates for each issue type and clear prerequisites/post-creation guidance. It is efficient and well-organized, with only minor room to tighten placeholder prose and add an explicit post-creation verification step.

DimensionReasoningScore

Conciseness

The body is mostly lean directive prose and copy-paste commands with minimal over-explanation of concepts Claude already knows; a few template placeholder descriptions and the 'Useful Options' table could be trimmed slightly, fitting the 4-anchor 'efficient; minor instances of over-explanation' rather than the 5-anchor's fully lean state.

4 / 5

Actionability

Provides fully executable, copy-paste-ready `gh issue create` commands with complete heredoc bodies for bug, feature, and task templates covering the common cases, matching the 5-anchor 'fully executable; copy-paste ready code or commands'.

5 / 5

Workflow Clarity

Clear sequence across Prerequisites, template selection, creation, and post-creation steps with a prerequisite checkpoint (`gh auth status`) and an explicit 'After Creating' section; not a 5 because there is no explicit verify-the-issue-was-created step or error-recovery loop, and not below 4 because the operation is non-destructive so the batch/destructive cap does not apply.

4 / 5

Progressive Disclosure

Single self-contained SKILL.md (~155 lines) with well-organized sections and no bundle files to navigate; content is appropriately inlined for a skill of this size, fitting the 4-anchor 'good structure; most content appropriately placed' rather than the 5-anchor which presumes well-signaled external references.

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.

A strong, third-person description that explicitly answers both what and when with a solid set of natural trigger keywords. The only weakness is that the capability list is a single action (creating issues), so specificity is good but not comprehensive.

DimensionReasoningScore

Specificity

Names the domain (GitHub issues via gh CLI) and one concrete action ('Create GitHub issues'), plus the bug/feature/task variants, but the action set is essentially a single operation rather than a comprehensive list, matching the '1-2 concrete actions' anchor rather than the 4-anchor's 'several specific actions'.

3 / 5

Completeness

Clearly states what it does ('Create GitHub issues using the gh CLI') and when to use it ('Use when the user wants to create a new issue, report a bug, request a feature, or create a task in GitHub') with concrete trigger phrases, matching the 5-anchor that explicitly answers both what and when.

5 / 5

Trigger Term Quality

Explicit trigger keywords 'create issue, new issue, file bug, report bug, feature request, github issue' cover the natural phrases users say, with only minor synonyms missing, fitting the 'good keyword coverage; a few natural terms missing' anchor rather than the 5-anchor's exhaustive synonym/file-extension list.

4 / 5

Distinctiveness Conflict Risk

The description is scoped to a clear niche ('Create GitHub issues using the gh CLI') with distinct trigger phrases unlikely to fire for unrelated skills, matching the 5-anchor's 'clear niche with distinct triggers; minimal conflict risk'.

5 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
NVIDIA/OpenShell
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.