gh-credit-harvest

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

Quality

75%

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

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.

The body is a tight, fully executable workflow with explicit validation checkpoints and a recovery path for conflicts, well-organized into clear sections with no unnecessary padding. It is a strong, action-oriented skill body.

Dimension	Reasoning	Score
Conciseness	The body is lean and command-driven with no padding about concepts Claude already knows; inline comments ('# author to preserve', '# empty/clean = no conflict') earn their place, with only minor narrative framing that could be trimmed, fitting the 'efficient; minor instances' anchor.	4 / 5
Actionability	Fully executable, copy-paste-ready bash commands with clear placeholders (<release-branch>, <N>, <sha>, <handle>) plus a concrete grounded example (PR #3221) cover the common cherry-pick and conflict cases, matching the top anchor.	5 / 5
Workflow Clarity	A clearly sequenced 7-step workflow with explicit validation (step 6: cargo fmt/test, check-coauthor-trailers.py, 'only land green') and a conflict-recovery feedback loop (step 5) for this destructive landing operation, satisfying the explicit-validation anchor.	5 / 5
Progressive Disclosure	With no bundle files and a compact body organized into clear 'When to use', 'Workflow', and 'Red flags / don't' sections, the skill qualifies for the under-50-lines well-organized exception, so progressive disclosure scores 5 without external references.	5 / 5
	Total	19 / 20 Passed

Description

58%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 action-oriented with a clear distinct niche, but it omits an explicit 'Use when...' trigger clause, capping completeness and limiting trigger-term quality. Adding a concrete trigger phrase would lift the two lowest dimensions.

Suggestions

Append an explicit 'Use when...' trigger clause naming the natural phrases a user would say, e.g. 'Use when you have approval to land one community PR into a release branch and need to preserve its authorship and credit.'

Add common trigger synonyms/variations users might actually say (e.g. 'cherry-pick a community contribution', 'credit a contributor', 'land an external PR') to broaden keyword coverage.

Tighten distinctiveness by contrasting with the sibling workflow in the description itself, e.g. 'Harvest (not just close) one community PR…' to reduce overlap with close-with-credit.

Dimension	Reasoning	Score
Specificity	Names the domain (community PR into a release branch) and several concrete actions — preserve authorship, preserve credit, verify green, post a thank-you — with only minor coverage gaps, fitting the 'lists several specific actions' anchor.	4 / 5
Completeness	The description clearly answers 'what' (harvest one PR with authorship/credit preserved, verified green, thank-you) but contains no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	'community PR', 'release branch', 'authorship', 'credit', and 'thank-you' are relevant keywords, but natural trigger phrases a user would actually say (and common variations) are thin; it stops short of comprehensive coverage.	3 / 5
Distinctiveness Conflict Risk	The credit-harvest niche is mostly distinct with minimal conflict risk, though it overlaps slightly with the related close-with-credit/gh-close-issues workflow mentioned in the body, keeping it just below a clear-niche 5.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: Hmbown/CodeWhale
Path: docs/skills/gh-credit-harvest/SKILL.md
Commit: 8ae401b

Reviewed: 1 day 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.