CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

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

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 excellent content body: fully executable commands, a well-sequenced workflow with explicit validation and approval gates, and tight organization with no bundle-file overhead. The only weakness is minor redundancy between the intro, the frontmatter description, and the red-flags section.

Suggestions

Trim the opening paragraph, which restates the frontmatter description and duplicates two of the 'Red flags / don't' rules; the sections below already carry that content.

The 'When to use' section is the natural place for the trigger guidance missing from the description; cross-checking them would keep both consistent.

DimensionReasoningScore

Conciseness

The body is dense and command-first with essentially no explanation of concepts Claude already knows; however, the opening paragraph repeats the frontmatter description nearly verbatim and pre-states two rules ('never act on title or labels alone', approval gating) that the 'Red flags / don't' section restates. These minor trimmable redundancies fit anchor 4 rather than 5's 'every token earns its place'.

4 / 5

Actionability

Fully executable, copy-paste-ready commands throughout: exact 'gh pr list/view' invocations with --json field lists, a 'git merge-tree' conflict check, trailer formats with a gh api command for the noreply id, and a 'cargo fmt && cargo test' sanity check. Placeholders like <release-branch> are appropriately repo-specific, so the common cases are covered as anchor 5 requires.

5 / 5

Workflow Clarity

A clear 8-step sequence with explicit validation checkpoints: read-everything-decide-nothing pull, code+tests+comments+checks confirmation, merge-tree test against the real landing branch, trailer validation, and a local fmt/test sanity check before recommending. Risky outward actions (merge/close/tag/post) are explicitly gated on maintainer approval, and the merge-tree step includes an error-recovery rationale. This matches anchor 5, not 4, because validation is explicit and repeated rather than implied.

5 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), and none are needed: the skill is a single well-sectioned file (~100 lines) with no nested references and no inline content that clearly belongs in a separate file. References to .github/AUTHOR_MAP and auto-close-harvested.yml are repo artifacts, not skill bundle references. Per the simple-skill scoring note, well-organized sections with no need for external references score 5.

5 / 5

Total

19

/

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.

A fairly strong description with concrete, non-generic capabilities and good natural keywords, but it omits any explicit 'when to use' trigger guidance, capping completeness. Adding a trigger clause and common synonyms (pull request, triage, backlog) would lift it.

Suggestions

Append a trigger clause, e.g. 'Use when triaging a crowded PR/issue queue before a release or when you want to land the most contributor value with the least risk.'

Include natural synonyms users would say: 'pull requests', 'triage', 'backlog', 'release cut'.

Mention the concrete outputs (ranked hit list, close-with-evidence notes, credit plan) so the 'what' covers the full capability set.

DimensionReasoningScore

Specificity

Lists several concrete action targets ('clean focused community PRs, already-implemented issues to close, safe quick-fixes') rather than vague claims, but coverage has minor gaps (e.g., the ranked output and credit handling from the body are absent). It is not score 3 because more than 1-2 concrete actions are named; not 5 because the action set is not comprehensive.

4 / 5

Completeness

The 'what' is clear (hunt the queue for clean PRs, closable issues, quick-fixes) but there is no 'Use when...' or equivalent trigger clause, which the judging guidelines cap at 3. Not 2 because the 'what' is concrete, not vague.

3 / 5

Trigger Term Quality

Natural terms like 'issue/PR queue', 'community PRs', and 'quick-fixes' are present, but common variations users might say ('pull request' spelled out, 'triage', 'backlog', 'release cut') are missing. Good coverage with a few gaps fits anchor 4 better than 3 (which requires missing common variations broadly).

4 / 5

Distinctiveness Conflict Risk

The niche (pre-release queue triage for value-over-risk wins, NEW contributor credit) is mostly distinct from generic review/merge skills, with only minor overlap risk against general PR-review workflows. Not 5 because 'PRs' and 'issues' alone could pull it toward general code-review or issue-triage skills.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Hmbown/Codewhale

Path

docs/skills/gh-treasure-hunt/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.