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

91%

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

92%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: a tightly sequenced seven-step workflow where every step is backed by a copy-paste-ready gh command, with explicit validation gates and a red-flags checklist that catch the failure modes (filing from a hunch, unfalsifiable criteria, invented labels). The only trimmable content is a small amount of motivational framing in the opening.

DimensionReasoningScore

Conciseness

The body is dense and imperative with commands doing the talking, but a few rhetorical flourishes ('An issue is maintainer evidence, not a sticky note', 'Vague issues become queue noise; concrete ones become fixes with credit') could be trimmed — efficient with minor over-explanation rather than lean throughout.

4 / 5

Actionability

Every step carries executable commands (gh issue list/pr list with --search, gh label list, gh api milestones, and a complete gh issue create invocation with --label/--milestone/--body-file flags) plus concrete title and acceptance-criteria examples, leaving only trivial live-value substitution to the reader.

5 / 5

Workflow Clarity

Seven well-sequenced steps include explicit validation gates: confirm the code claim from source rather than memory (step 1), a pre-file duplicate/PR search (step 2), and a readiness gate ('If you cannot state how it's verified, the issue is not ready') backed by the Red flags checklist. Filing a single issue is neither destructive nor batch, so no validation cap applies.

5 / 5

Progressive Disclosure

This is a single-purpose, single-file skill with well-organized sections (When to use, Workflow, Red flags, Output) and nothing that belongs in a separate file — labels and milestones are deliberately read from the live set rather than inlined as a static reference, so no external bundle is needed.

5 / 5

Total

19

/

20

Passed

Description

87%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 description with an explicit trigger clause and an enumerated list of concrete deliverables, tightly scoped to one repository and task. Its only weaknesses are mild filler ('well-formed, actionable') and missing natural trigger synonyms such as 'report a bug' or 'open an issue'.

DimensionReasoningScore

Specificity

The description enumerates four concrete deliverables ('repro, acceptance criteria, labels, and milestone') plus the artifact ('a well-formed, actionable issue'), but omits parts of the workflow (duplicate check, cross-linking) and 'well-formed, actionable' is mild filler — several specific actions with minor coverage gaps rather than comprehensive.

4 / 5

Completeness

It explicitly answers both halves: 'Use when filing a new Codewhale GitHub issue' is a concrete when-clause, and 'turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone' is a clear what.

5 / 5

Trigger Term Quality

'filing a new Codewhale GitHub issue' and 'bug or idea' are natural phrases a user would say, giving good keyword coverage, but common variations like 'report a bug', 'open an issue', or 'track an issue' are missing.

4 / 5

Distinctiveness Conflict Risk

The niche is clear — filing Codewhale GitHub issues specifically — with distinct triggers ('filing', 'GitHub issue', 'bug or idea') that would not fire for unrelated skills.

5 / 5

Total

18

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

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.