CtrlK
BlogDocsLog inGet started
Tessl Logo

create-github-issue

Create GitHub issues using GitHub CLI with support for templates, labels, assignees, milestones, and draft issues. Use when the user asks to create a GitHub issue, file a bug report, submit a feature request, or open an issue in a GitHub repository.

72

Quality

88%

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

76%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 is actionable and well-structured with executable gh CLI commands and a clear multi-step workflow. Its main weakness is the absence of a verification/feedback checkpoint for an irreversible publish action, which caps workflow clarity.

Suggestions

Add a validation/verification checkpoint after issue creation (e.g., confirm the returned URL resolves, verify labels were applied with `gh issue view`, and report any mismatch) to satisfy the feedback-loop requirement for an irreversible outward-facing action.

Trim redundant emphatic directives ('CRITICAL', 'MANDATORY', 'No Exceptions', 'without exception', 'Single Source of Truth') that restate guidance already conveyed in the numbered steps.

De-duplicate the Guidelines and Notes sections against the workflow steps to remove repeated directives such as dynamic discovery and template adherence.

DimensionReasoningScore

Conciseness

Mostly lean with executable commands and bullet guidance and no conceptual over-explanation, but emphatic directives ('CRITICAL', 'MANDATORY', 'No Exceptions', 'without exception') are slightly redundant and could be trimmed, so it falls just below the lean-every-token-earns-its-place anchor.

4 / 5

Actionability

Provides copy-paste-ready commands (ls, cat, git status, gh issue create with flags) and concrete tool usage for body-file creation, covering the common case fully.

5 / 5

Workflow Clarity

A clear 7-step sequence is present, but issue creation is an outward-facing irreversible action with no validation/verification checkpoint (no confirmation that the issue was created or labels applied), so the destructive/batch-operation cap of 3 applies.

3 / 5

Progressive Disclosure

Well-organized into Workflow/Guidelines/Notes with no nested references and no inlined bulk that belongs elsewhere, though the Guidelines/Notes sections partially restate directives already given in the workflow steps, keeping it just short of a clean 5.

4 / 5

Total

16

/

20

Passed

Description

100%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 clear, specific, and complete: it states concrete capabilities and provides explicit, natural trigger phrases for when to invoke the skill. It uses third person and avoids fluff.

DimensionReasoningScore

Specificity

Names the domain plus multiple concrete capabilities ('templates, labels, assignees, milestones, and draft issues'), matching the comprehensive-coverage anchor rather than the minor-gaps anchor at 4.

5 / 5

Completeness

Explicitly states both what it does (create GitHub issues via the CLI with listed features) and when to use it via an explicit 'Use when...' clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user phrasings ('create a GitHub issue', 'file a bug report', 'submit a feature request', 'open an issue') with synonyms, matching the comprehensive natural-terms anchor.

5 / 5

Distinctiveness Conflict Risk

Targets a clear niche (GitHub issue creation via gh CLI) with distinct triggers, minimizing overlap with other skills.

5 / 5

Total

20

/

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
tailcallhq/forgecode
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.