CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gh-file-issue

Use when filing a new Codewhale GitHub issue: turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone.

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary instruction-only skill body: concrete commands at every step, explicit validation checkpoints, and disciplined scope control (file-only writes, no inventing labels/milestones). The single minor improvement is offloading the label/milestone taxonomy or issue body template to a reference file to slim the main SKILL.md.

DimensionReasoningScore

Conciseness

The body is lean and dense with original guidance — house title pattern, live label/milestone rules, sectioned body template, and explicit non-goals — with no padding explaining concepts Claude already knows. Every line conveys a Codewhale-specific rule or command.

5 / 5

Actionability

Every workflow step ships executable commands (git rev-parse, grep, gh issue/pr/label list, gh api milestones, and a fully flagged gh issue create invocation), plus a concrete body-section template with example acceptance-criteria checkboxes and a worked example title. Fully copy-paste ready apart from intentionally live values.

5 / 5

Workflow Clarity

Seven explicitly sequenced steps with built-in validation checkpoints: evidence confirmed from source before writing (step 1), duplicate check before filing (step 2), and live-set verification of labels/milestones (step 5), plus a red-flags section covering failure modes and scope limits for the single write operation.

5 / 5

Progressive Disclosure

Well-organized single-file structure (When to use / Workflow / Red flags / Output) with no bundle files, and nothing that clearly demands splitting. However, at ~95 lines it exceeds the under-50-line simple-skill exception, and inline content like the label taxonomy and body-section template could live in a reference file, so it sits just below the top anchor.

4 / 5

Total

19

/

20

Passed

Description

92%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 tight, high-quality description: it states what the skill produces in full concrete detail and gives an explicit 'Use when' trigger scoped to the Codewhale repo. The only improvement space is broader synonym coverage for trigger phrasing.

DimensionReasoningScore

Specificity

The description enumerates the complete concrete output of the skill — 'turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone' — naming every artifact the skill produces with no evident gaps, matching the comprehensive-coverage anchor rather than the 'minor gaps' anchor.

5 / 5

Completeness

Explicitly answers both: what ('turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone') and when ('Use when filing a new Codewhale GitHub issue'), with concrete trigger phrasing — a direct match for the top anchor.

5 / 5

Trigger Term Quality

Natural terms present: 'filing', 'GitHub issue', 'bug or idea', 'repro', 'labels', 'milestone'. A few common user phrasings are missing (e.g., 'report a bug', 'open/create an issue'), so it sits between the good-coverage and comprehensive-synonym anchors, noticeably above the midpoint.

4 / 5

Distinctiveness Conflict Risk

Scoped to a clear niche (filing issues on Codewhale's GitHub repo) with distinct triggers ('Codewhale GitHub issue', 'repro', 'milestone'); minimal realistic overlap with adjacent skills like general git or release workflows.

5 / 5

Total

19

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Hmbown/Codewhale

Path

docs/skills/gh-file-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.