CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

77

Quality

96%

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

100%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 skill: concise, fully actionable with concrete commands and templates, a clearly sequenced workflow with validation checkpoints, and clean single-file organization.

DimensionReasoningScore

Conciseness

Lean throughout; assumes Claude's competence, provides only what isn't already known (house patterns, live label/milestone sets), and every section earns its place with no padding or basic-concept explanation.

5 / 5

Actionability

Fully executable guidance — concrete `gh` commands, a title pattern with a worked example, and a sectioned body template with falsifiable acceptance-criteria checkboxes that are copy-paste ready.

5 / 5

Workflow Clarity

Clear numbered sequence with explicit verification checkpoints (confirm the claim from source, check for duplicates) and falsifiable acceptance criteria; the only write is issue creation, with explicit guardrails against merging, closing, tagging, or releasing.

5 / 5

Progressive Disclosure

Single well-organized SKILL.md under ~90 lines with no external bundle files; sections are clearly headed (When to use, Workflow, Red flags, Output) and all content sits at one navigable level.

5 / 5

Total

20

/

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 strong, specific description that answers what and when with concrete actions and a clear trigger. Trigger term coverage is the only soft spot, lacking some common synonyms users might naturally say.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'repro, acceptance criteria, labels, and milestone' — turning a bug/idea into an actionable issue, giving comprehensive coverage of the filing workflow.

5 / 5

Completeness

Explicitly answers both what it does (turn a bug or idea into a well-formed issue with repro, criteria, labels, milestone) and when to use it via the clear 'Use when filing a new Codewhale GitHub issue' trigger.

5 / 5

Trigger Term Quality

Natural terms like 'bug', 'idea', and 'filing a new GitHub issue' are present, but coverage of common synonyms a user might say (e.g. 'report', 'ticket', 'feature request') is somewhat thin.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — filing new Codewhale GitHub issues — with distinct triggers and minimal overlap risk against general gh or coding skills.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Hmbown/Codewhale
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.