CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

83%

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

75%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.

Highly actionable content with complete executable commands for all three issue types and explicit validation checkpoints for the attestation and labeling policy. The main weakness is duplicated policy prose across the Bug Reports and Feature Requests sections that inflates token cost without adding information.

Suggestions

Extract the shared attestation policy ('Confirm that the human operator personally uses OpenShell...', 'Do not add a type label automatically', 'Inspect current repository labels before applying any') into a single 'Shared policy' section referenced by the Bug Reports, Feature Requests, and Tasks sections, removing the near-verbatim repetition.

Add brief error-handling guidance after the gh commands (e.g., what to do if 'gh issue create' fails due to authentication or template mismatch) to close the workflow-clarity validation gap.

Consider moving the three full heredoc templates into references/ files (e.g., references/bug-template.md) and keeping a one-line pointer plus the policy in SKILL.md, keeping the main file closer to an overview.

DimensionReasoningScore

Conciseness

The attestation policy ('Confirm that the human operator personally uses OpenShell and directly encountered the problem...') and 'Do not add a type label automatically' are repeated nearly verbatim in both the Bug Reports and Feature Requests sections, which could be tightened into one shared policy block. Otherwise the content is project-specific policy with no filler or explanation of concepts Claude already knows — better than anchor 2 but not the lean anchor-4 fit.

3 / 5

Actionability

Three complete, copy-paste-ready 'gh issue create' heredoc commands cover the common cases (bug, feature, task), plus a concrete options table and an exact post-creation output format ('Created issue [#123](...)'). Fully executable guidance matching the top anchor.

5 / 5

Workflow Clarity

Coherent sequence from auth prerequisite through attestation check ('ask for it before creating the issue'), label inspection ('Inspect current repository labels before applying any'), template selection, and post-creation steps. Not a 5 because there is no error-handling guidance if the gh command fails; not a 3 because explicit validation checkpoints are present.

4 / 5

Progressive Disclosure

No bundle files exist; the single file is well-organized with clear section headers, and cross-references to ../../../CONTRIBUTING.md and ../label-issue/SKILL.md are clearly signaled and one level deep. Inline templates are the core executable content and appropriately placed, though the ~35-line heredocs make the file longer than a strict overview would be — a minor organization gap versus anchor 5.

4 / 5

Total

16

/

20

Passed

Description

87%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 description: concrete tool and actions, explicit 'Use when' clause, and a dedicated trigger-keyword list. The only soft spot is that the enumerated actions are all variations of one capability, which slightly limits breadth of coverage.

DimensionReasoningScore

Specificity

Names the concrete tool ('gh CLI') and enumerates several specific actions ('create a new issue, report a bug, request a feature, or create a task in GitHub'). Not a 5 because all listed actions are variants of the single 'create issue' capability rather than comprehensive coverage.

4 / 5

Completeness

Clearly answers both what ('Create GitHub issues using the gh CLI') and when ('Use when the user wants to create a new issue, report a bug...') with concrete trigger phrases appended. Explicitly matches the anchor-5 example structure.

5 / 5

Trigger Term Quality

Explicit trigger keywords ('create issue, new issue, file bug, report bug, feature request, github issue') are natural phrases users would say. Not a 5 because common variants like 'open an issue' or 'ticket' are missing; not a 3 because coverage goes well beyond a single generic keyword.

4 / 5

Distinctiveness Conflict Risk

Clear niche — GitHub issue creation via gh — with distinct triggers ('github issue', 'file bug') that are unlikely to fire for unrelated skills. All triggers are anchored to the GitHub context.

5 / 5

Total

18

/

20

Passed

Validation

81%

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

Validation — 13 / 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

relative_links

Relative link issues: 4 suspicious

Warning

Total

13

/

16

Passed

Repository

NVIDIA/OpenShell

Path

.agents/skills/create-github-issue/SKILL.md

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.