CtrlK
BlogDocsLog inGet started
Tessl Logo

create-issue

Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.

68

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

100%

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

The content is concise, actionable, and clearly sequenced with a review/approval checkpoint before submission; as a compact single-file skill it is well organized with no progressive-disclosure issues.

DimensionReasoningScore

Conciseness

The body is lean and well-organized, assumes Claude's competence, and avoids explaining concepts Claude already knows; every section earns its place.

3 / 3

Actionability

Provides concrete executable commands (gh issue list/create), specific template and draft paths, and exact label names, making the guidance copy-paste ready.

3 / 3

Workflow Clarity

A clear 6-step sequence with an explicit human-approval checkpoint ("Do not submit until the user explicitly approves") and an iterate-on-feedback loop before the destructive submit step.

3 / 3

Progressive Disclosure

A single-file skill under 50 lines with no need for external references, organized into clearly labeled sections — meeting the simple-skill bar for a top score.

3 / 3

Total

12

/

12

Passed

Description

67%

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 and distinguishes the skill well, but it omits an explicit "Use when..." trigger clause and is missing several natural trigger-term variations users would actually say.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to create, file, or open a GitHub issue from a feature idea or bug report."

Broaden trigger terms to cover natural phrasings like "feature request", "report a bug", and "file an issue".

Keep the existing concrete actions (draft, submit, bilingual body, labels) as they already anchor the specificity well.

DimensionReasoningScore

Specificity

Names multiple concrete actions — "Draft and submit a GitHub issue", "bilingual body", "correct labels" — rather than vague language, matching the multi-action anchor.

3 / 3

Completeness

Clearly states what the skill does, but lacks any "Use when..." clause or equivalent explicit trigger guidance, so the when is only implied and completeness is capped at 2.

2 / 3

Trigger Term Quality

Includes relevant natural terms ("GitHub issue", "bug description", "idea") but misses common variations users would say such as "feature request", "report a bug", or "file an issue".

2 / 3

Distinctiveness Conflict Risk

The combination of GitHub issue creation with bilingual body and correct labels is a clear, distinct niche unlikely to trigger for the wrong skill.

3 / 3

Total

10

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
QwenLM/qwen-code
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.