CtrlK
BlogDocsLog inGet started
Tessl Logo

gh-treasure-hunt

Hunt the issue/PR queue for highest value-over-risk wins: clean focused community PRs, already-implemented issues to close, safe quick-fixes.

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

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, highly actionable workflow with concrete commands, explicit validation checkpoints, and approval gates for risky operations. It is well-organized and self-contained with no unnecessary padding.

DimensionReasoningScore

Conciseness

The body is lean and high-signal with concrete commands and no over-explanation of concepts Claude already knows; the brief intro adds the output/approval framing rather than padding, matching the score-3 lean-and-efficient anchor.

3 / 3

Actionability

Provides fully executable, copy-paste-ready commands (gh pr list/view/checks, git merge-tree, python3 trailer check, cargo fmt/test) with specific flags, matching the score-3 anchor and clearly above the pseudocode score-2 example.

3 / 3

Workflow Clarity

Eight explicitly sequenced steps include validation checkpoints (merge-tree against the real branch, trailer validation, cargo fmt/test sanity check) plus approval holds before any merge/close, satisfying the score-3 anchor and avoiding the missing-validation cap.

3 / 3

Progressive Disclosure

No bundle files exist and none are needed; the single self-contained file is organized into clear sections (When to use, Ranking, Workflow, Red flags, Output) with no nested references, consistent with well-organized single-file scoring.

3 / 3

Total

12

/

12

Passed

Description

67%

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 concrete and distinctive, naming several specific actions and carving out a clear niche. It loses points for missing an explicit "Use when..." trigger and for jargon-heavy phrasing that misses common user terms.

Suggestions

Add an explicit "Use when..." clause (e.g., "Use when triaging a crowded PR/issue queue before a release") to lift completeness to 3.

Swap or augment "value-over-risk wins" with natural user terms like "triage", "backlog", or "find easy wins" to improve trigger-term coverage.

Lead with the action in third-person imperative already used, but pair it with the explicit trigger to reduce conflict risk further.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "clean focused community PRs, already-implemented issues to close, safe quick-fixes" — matching the anchor for multiple specific concrete actions, not the score-2 single-domain example.

3 / 3

Completeness

Clearly states what the skill does, but lacks an explicit "Use when..." trigger clause; per the guideline a missing explicit trigger caps completeness at 2, and it does not reach the score-3 what-and-when anchor.

2 / 3

Trigger Term Quality

Includes relevant natural terms (PR, issue, queue, quick-fixes, close) but leans on skill-specific jargon ("value-over-risk wins") and omits common variations a user would say like "triage", "backlog", or "review"; closest to the score-2 anchor.

2 / 3

Distinctiveness Conflict Risk

The niche is clearly scoped to GitHub issue/PR queue triage with credit handling, with triggers unlikely to fire for unrelated skills, matching the score-3 distinct-niche anchor rather than the overlapping score-2 case.

3 / 3

Total

10

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

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.