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.

63

Quality

74%

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-treasure-hunt/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 concrete executable commands throughout a clearly sequenced workflow backed by validation and safety guardrails. Structure is clean and self-contained; the only mild weakness is light failure-recovery feedback loops and slight redundancy with the description.

DimensionReasoningScore

Conciseness

The body is lean and sectioned with no padding about concepts Claude already knows; the opening paragraph does restate the frontmatter description, a minor instance of redundancy that keeps it from a 5.

4 / 5

Actionability

Provides copy-paste-ready, fully executable commands (gh pr list/view/checks, git fetch, git merge-tree, git grep, gh api, cargo fmt/test) plus a concrete credit-trailer example covering the common cases.

5 / 5

Workflow Clarity

An explicit 8-step sequence includes validation checkpoints (merge-tree against the real landing branch, cargo fmt/test sanity-check) and a Red flags checklist; feedback loops for failure recovery are only lightly spelled out, so it sits at 4.

4 / 5

Progressive Disclosure

Clean, well-signaled section structure (When to use, Ranking, Workflow, Red flags, Output) with no nested references and all content appropriately inlined; at >50 lines with no deeper materials it is well-organized but stops short of the 'overview pointing to detailed files' ideal.

4 / 5

Total

17

/

20

Passed

Description

66%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 distinct, with strong natural trigger terms and a clear statement of what the skill does. Its main weakness is the missing explicit 'Use when...' clause, which caps completeness.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when triaging a crowded PR/issue queue before a cut to maximize value-over-risk wins.'

Surface the credit-handling and ranked-output deliverables in the description so the 'what' is more comprehensive.

Include a natural synonym like 'triage' to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain (issue/PR queue triage) and lists several concrete win types ('clean focused community PRs, already-implemented issues to close, safe quick-fixes'); minor gaps such as credit handling and ranked output are not surfaced.

4 / 5

Completeness

Has a clear 'what' but no explicit 'Use when...' or equivalent trigger clause, so per the rubric guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

Includes natural terms a user would say ('issue/PR queue', 'community PRs', 'quick-fixes'); a few common synonyms like 'triage' or 'review PRs' are missing, so it stops short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

The value-over-risk GitHub triage framing carves a clear, mostly distinct niche with low overlap risk, though the absence of explicit 'Use when' triggers leaves minor conflict potential.

4 / 5

Total

15

/

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.