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.

62

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./docs/skills/gh-compile-issues/SKILL.md
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 highly actionable with executable commands, a clearly sequenced workflow, and explicit validation checkpoints; it is concise and well-structured, with only minor repo-specific hardcoding that slightly reduces conciseness.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no basic-concept explanations), with only minor instances of repo-specific padding such as the hardcoded 'v0.8.62' milestone and branch names that could be parameterized.

4 / 5

Actionability

Fully executable, copy-paste-ready commands throughout ('gh issue list', 'gh issue view', 'git grep -nI', 'git fetch origin pull/N/head', 'cargo fmt --all -- --check', 'cargo test --workspace') covering the common triage cases.

5 / 5

Workflow Clarity

Steps 1-7 are clearly sequenced with explicit validation checkpoints (step 7's cargo fmt/test and git merge-tree against the real landing branch) and a 'Red flags / don't' checklist; the skill is explicitly read-only so the destructive/batch cap does not apply.

5 / 5

Progressive Disclosure

Well-organized single-file structure (Inputs, Workflow, When to use, Credit, Red flags, Output) with no nested references and appropriately self-contained procedural guidance; no bundle files exist, so minor gaps are organizational only.

4 / 5

Total

18

/

20

Passed

Description

58%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 and clearly distinct, naming concrete triage actions and output, but it omits an explicit 'when to use' trigger clause, which limits completeness and natural trigger-term coverage.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers (e.g. 'Use when a maintainer hands you a batch of GitHub issues or a milestone to triage').

Include common synonyms users might say, such as 'bug triage', 'issue review', or 'milestone audit', to broaden trigger-term coverage.

Keep the concrete action list but pair it with the trigger phrase to lift completeness from a clear 'what' alone to both 'what' and 'when'.

DimensionReasoningScore

Specificity

Lists several concrete actions ('fetch each, check current code, classify already-done/quick-fix/design/defer with cited evidence') plus the coverage-matrix output, with only minor coverage gaps.

4 / 5

Completeness

The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

'GitHub issues' and 'coverage matrix' are relevant keywords, but common natural variations like 'bug triage' or 'issue review' are missing and the phrasing leans jargon-heavy.

3 / 5

Distinctiveness Conflict Risk

The niche (triaging GitHub issues into a coverage matrix with dispositions) is specific and mostly distinct, with only minor overlap risk against general code-review skills.

4 / 5

Total

14

/

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.