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.

70

Quality

86%

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

72%Weight 40%Scale 1-3

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

The content is highly actionable with executable commands and a clear step sequence, but it is slightly padded by redundant Guidelines/Notes and lacks a validation checkpoint before the irreversible issue-creation step. Progressive disclosure is fine given the self-contained structure.

Suggestions

Add an explicit verification checkpoint before 'gh issue create' — e.g., confirm all required template fields are populated and that chosen labels exist in .github/labels.json — to satisfy the feedback-loop expectation for outward-facing operations.

Trim the 'Guidelines' and 'Notes' sections by removing restatements of the discovery and template-adherence rules already covered in the workflow steps to reduce redundancy.

DimensionReasoningScore

Conciseness

Mostly efficient with executable command snippets and no concept explanations, but the 'Guidelines' and 'Notes' sections restate points already covered in the workflow (e.g., 'Dynamic Discovery' and 'Single Source of Truth' repeat the discovery step), adding mild padding.

2 / 3

Actionability

Provides copy-paste-ready commands throughout — 'ls .github/ISSUE_TEMPLATE/', 'git log --oneline -10', 'gh issue list --search', and a full 'gh issue create' invocation with flags and optional parameters — with concrete field-mapping guidance.

3 / 3

Workflow Clarity

The seven steps are clearly sequenced, but the irreversible outward-facing 'gh issue create' step has no validation checkpoint (e.g., verifying labels exist in .github/labels.json or confirming the body is complete) before submission, which caps clarity at 2 for a destructive/outward operation.

2 / 3

Progressive Disclosure

No bundle files exist, so the skill is self-contained; its sections are clearly organized with headers and there is no nested-reference problem, which satisfies the simple-skill allowance for a well-organized single-file skill.

3 / 3

Total

10

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 specific, action-oriented, and pairs a clear capability list with explicit, natural-language triggers. It cleanly answers both what the skill does and when to use it without padding.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities beyond the core action — 'templates, labels, assignees, milestones, and draft issues' — matching the anchor that names several specific actions rather than just a domain.

3 / 3

Completeness

Explicitly states what it does (issue creation with the listed features) and provides an explicit 'Use when...' clause with multiple triggers, satisfying both the 'what' and 'when' requirements.

3 / 3

Trigger Term Quality

Phrases like 'create a GitHub issue', 'file a bug report', 'submit a feature request', and 'open an issue' are natural things a user would say, giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Scoped narrowly to GitHub issue creation via the gh CLI with distinct triggers, making it 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
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.