CtrlK
BlogDocsLog inGet started
Tessl Logo

gh-compile-issues

Triage N GitHub issues into a coverage matrix: fetch each, check current code, classify already-done/quick-fix/design/defer with cited evidence.

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

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

The content is a strong, actionable triage workflow: executable commands, a concrete classification rubric, explicit validation gates, and red-flag guardrails. Minor conciseness gains and the lack of progressive disclosure via bundle files are the only weak points.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence, with concrete bash/code blocks rather than concept explanation, but includes a few minor over-explanatory sentences (e.g. restating the untrusted-data caveat in both intro and red flags) that could be trimmed.

4 / 5

Actionability

Provides fully executable, copy-paste-ready gh/git commands covering the common cases (issue list, issue view, git grep, merge-tree verification) plus the exact classification rubric and table format, leaving no execution gap.

5 / 5

Workflow Clarity

Steps are explicitly sequenced (1-7) with concrete validation checkpoints — the cargo fmt/test gate and the merge-tree-against-real-branch verification for PR-tied issues — plus red-flag guardrails, satisfying the explicit-feedback-loop requirement for this batch triage skill.

5 / 5

Progressive Disclosure

The skill is well-organized with clear section headers (Inputs, Workflow, When to use, Output) and stays appropriately self-contained as a single overview file, but the parallel-agent fan-out detail and credit rules are inlined where a one-level-deep reference could keep the core leaner; no bundle files exist to offload detail.

4 / 5

Total

18

/

20

Passed

Description

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

The description is specific, distinctive, and free of fluff, concretely naming the triage-to-coverage-matrix action with evidence-based classification. Its main weakness is the missing explicit "Use when..." trigger clause, which caps completeness and slightly limits natural trigger-term coverage.

Suggestions

Add an explicit 'Use when...' clause naming the trigger scenarios, e.g. 'Use when a maintainer hands you a batch of GitHub issues or a milestone and wants a coverage matrix before acting.'

Include natural synonyms users would say, such as 'triage', 'milestone', or 'issue backlog', to broaden trigger-term coverage.

State the output action explicitly ('produces a coverage report / matrix') so the full what is named alongside the input actions.

DimensionReasoningScore

Specificity

Names several concrete actions — "fetch each", "check current code", "classify already-done/quick-fix/design/defer", "with cited evidence" — but omits the coverage-matrix output action explicitly, leaving a minor coverage gap rather than a comprehensive list.

4 / 5

Completeness

The what is clearly stated (triage issues into a coverage matrix with classification and evidence), and the when is implied by the triage framing, but there is no explicit "Use when..." trigger clause, so per the judging guideline the when is present but only weakly implied.

4 / 5

Trigger Term Quality

Includes natural trigger terms a maintainer would say ("GitHub issues", "coverage matrix", "quick-fix", "defer") but lacks common synonyms like "triage" or "milestone" and the explicit "Use when..." phrasing, so a few natural terms are missing.

4 / 5

Distinctiveness Conflict Risk

The niche is highly specific — triaging GitHub issues into a coverage matrix with cited evidence — with clear, distinct triggers and minimal overlap risk against general code or doc skills.

5 / 5

Total

17

/

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.