gh-credit-harvest

Harvest one community PR into a release branch with authorship and credit preserved, verified green, and a warm thank-you.

Quality

77%

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-credit-harvest/SKILL.md

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 body is highly actionable with a well-sequenced, validated workflow and concrete commands. It is concise and well-structured, with only minor trimming and organization opportunities.

Dimension	Reasoning	Score
Conciseness	Largely lean with executable commands and minimal padding, though inline rationales like 'a main-based mergeable flag does not prove it lands cleanly' and the explanatory prose around trailers could be trimmed slightly.	4 / 5
Actionability	Fully executable, copy-paste-ready commands throughout (git fetch, gh pr view/diff/comment, git merge-tree, cherry-pick, cargo fmt/test) with placeholders, plus a grounded real example (PR #3221) covering a common case.	5 / 5
Workflow Clarity	A clear 7-step sequence with explicit validation checkpoints (merge-tree conflict check in step 3, 'only land green' in step 6), error-recovery guidance for conflicts in step 5, and a reinforcing 'Red flags / don't' checklist.	5 / 5
Progressive Disclosure	Well-organized into 'When to use', 'Workflow', and 'Red flags' sections with one-level references to real repo paths (.github/AUTHOR_MAP, auto-close workflow) and a sibling skill; minor gaps as the dense workflow and grounded example are inlined rather than split out.	4 / 5
	Total	18 / 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 states concrete, distinctive capabilities but omits an explicit 'when to use' trigger clause, which caps completeness. Adding a 'Use when...' clause would lift it from good to strong.

Suggestions

Add an explicit trigger clause, e.g. 'Use when Hunter approves landing ONE specific community PR into a release branch and you need to preserve authorship and credit.'

Include the natural synonym 'pull request' alongside 'PR' to broaden trigger-term coverage.

Clarify the 'when' by contrasting with the close-with-credit path already mentioned in the body.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'Harvest one community PR into a release branch', 'authorship and credit preserved', 'verified green', 'a warm thank-you' — covering the niche well with only minor gaps (e.g., the cherry-pick/trailer mechanism is omitted, but that is appropriate for a description).	4 / 5
Completeness	The 'what' is clearly stated, but there is no explicit 'Use when...' trigger clause, so per the guideline completeness is capped at 3 with 'when' only weakly implied.	3 / 5
Trigger Term Quality	Contains natural domain terms a user would plausibly say ('community PR', 'release branch', 'credit', 'thank-you') with good coverage, though a few common synonyms ('pull request', 'contributor') are absent.	4 / 5
Distinctiveness Conflict Risk	Carves a clear niche (credited harvest of one community PR into a named release branch) with minimal conflict risk, though it sits near related PR/git skills like the referenced gh-close-issues.	4 / 5
	Total	15 / 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-credit-harvest/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.