gh-find-prs

Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./docs/skills/gh-find-prs/SKILL.md

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 executable commands and a well-sequenced triage workflow including a real mergeability validation step. It is concise and well-structured, with only minor room to tighten prose and consider splitting reference material.

Suggestions

Tighten the explanatory prose in steps 1 and 4 (e.g. the mergeStateStatus rationale) to push conciseness toward a 5.

Consider moving the CI job-name catalogue and disposition trailer formats into a short references file so SKILL.md stays a lean overview.

Add an explicit 'if merge-tree reports conflicts, re-probe after a fmt fix' micro-loop to strengthen the validation feedback path.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes Claude's competence, with purposeful domain-specific notes (CI job names, why mergeStateStatus lies) that earn their place; only minor explanatory prose could be trimmed.	4 / 5
Actionability	Fully executable, copy-paste-ready commands throughout (gh pr list/view/diff, git merge-tree, cargo fmt/clippy) covering the common triage cases with concrete syntax.	5 / 5
Workflow Clarity	A clear 7-step sequence with an explicit validation checkpoint (merge-tree clean test in step 5) and conflict routing to HARVEST/DEFER; falls just short of a 5 because validate→fix→retry feedback loops are limited by the read-only nature of the skill.	4 / 5
Progressive Disclosure	Well-organized into clear sections (When to use, Workflow, Red flags) with content appropriately inline; no external references are used, but the skill slightly exceeds the 50-line simple-skill threshold so the structure-only 5 does not fully apply.	4 / 5
	Total	17 / 20 Passed

Description

70%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 a precise niche and concrete triage actions. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which limits completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when a maintainer asks to triage the PR queue, sweep community PRs before a release cut, or needs a per-PR merge/harvest/defer/close call.'

Include a couple more natural trigger phrases users would say ('PR queue', 'what can we land') to broaden keyword coverage.

Optionally name the disposition outcomes (DIRECT-MERGE / HARVEST / DEFER / CLOSE) in the description to make the 'what' more comprehensive.

Dimension	Reasoning	Score
Specificity	Names the domain ('open Codewhale PRs') and several concrete actions — survey, triage for mergeability, and triage for disposition against the real landing branch — with only minor coverage gaps.	4 / 5
Completeness	The 'what' is clear (survey and triage PRs for mergeability/disposition) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Includes natural maintainer phrases ('PRs', 'triage', 'mergeability', 'landing branch') that a user would plausibly say, though a few common variations ('PR queue', 'what can we land') are absent from the description itself.	4 / 5
Distinctiveness Conflict Risk	The niche is sharply defined — Codewhale PR triage against the real landing branch — giving it distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

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-find-prs/SKILL.md
Commit: 21282f1

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.