gh-credit-harvest

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

Quality

83%

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

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is concise, fully actionable, and organized as a clear numbered workflow with explicit validation checkpoints and a recovery path for conflicts — a strong, self-contained skill body.

Dimension	Reasoning	Score
Conciseness	The body is lean: tight inline comments (e.g. "# author to preserve", "# empty/clean = no conflict") and no padding or explanation of concepts Claude already knows; every section earns its tokens.	3 / 3
Actionability	Each step ships executable commands with placeholders (git fetch/cherry-pick, gh pr view/diff/comment, cargo test -p), plus a grounded real example, making guidance copy-paste ready.	3 / 3
Workflow Clarity	A clearly sequenced 7-step workflow with explicit validation checkpoints (merge-tree mergeability check, cargo test "only land green", check-coauthor-trailers.py) and a conflict-resolution feedback loop for a destructive landing operation.	3 / 3
Progressive Disclosure	Well-organized into When-to-use / Workflow / Red-flags sections with no need for external bundle files; repo paths like .github/AUTHOR_MAP are contextual, not skill-bundle references.	3 / 3
	Total	12 / 12 Passed

Description

67%

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 distinctive, with concrete actions and a clear niche, but it omits an explicit "Use when..." trigger and leans on the skill-specific verb "Harvest" rather than natural user phrasing.

Suggestions

Add an explicit trigger clause, e.g. "Use when landing a single approved community PR into a release branch while preserving the original author."

Soften the jargon verb or pair "Harvest" with natural terms like "land" or "merge" to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Harvest one community PR into a release branch with authorship and credit preserved, verified green, and a warm thank-you" lists several concrete actions (harvest, preserve authorship/credit, verify green, thank) rather than vague language.	3 / 3
Completeness	It clearly states what the skill does, but lacks an explicit "Use when..." trigger clause; per the rubric a missing trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	"community PR", "release branch", and "credit" are relevant terms a user might say, but "Harvest" is skill-specific jargon and common variations (e.g. "merge PR", "land PR", "contribution") are absent.	2 / 3
Distinctiveness Conflict Risk	The niche — landing a single community PR with preserved credit and a thank-you — is distinctive and unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 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: f018d3e

Reviewed: about 13 hours 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.