ship

Land completed Fallow work after review, run pre-push parity, monitor merged-commit CI, and leave repositories clean. Use when asked to ship, merge, or move approved work to main.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/ship/SKILL.md

Quality

Content

75%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, well-sequenced shipping checklist with explicit verification steps and a completion guard. Its main weakness is actionability: several steps defer the concrete commands and recovery actions to external docs without stating them.

Suggestions

Add the concrete command(s) or a one-line example for the protected-main merge and CI monitoring steps, or state the recovery action when CI fails or conflict drift is detected.

Surface the docs/development/quality-gates.md reference more explicitly (e.g., a short 'References' line) so the one-level-deep pointer is clearly navigable.

Specify which required checks to re-run, or name the check target, so step 2 is executable without opening the external file.

Dimension	Reasoning	Score
Conciseness	The ~20-line numbered checklist is lean and assumes Claude's competence with no padded explanation or restated concepts, matching the 'lean and efficient; every token earns its place' anchor.	5 / 5
Actionability	Steps give concrete intent ('Re-run the required checks from docs/development/quality-gates.md', 'Create signed conventional commits only') but defer actual commands and specifics to external docs/workflows, leaving key execution details incomplete as in the 'some concrete guidance but incomplete' anchor.	3 / 5
Workflow Clarity	Eight steps are clearly sequenced with verification checkpoints (monitor CI in step 6, inspect for conflict markers and generated drift in step 7, plus the closing guard), but error-recovery feedback for CI failure or detected drift is only implied, fitting 'clear sequence with most checkpoints present; minor validation gaps'.	4 / 5
Progressive Disclosure	The single short file is well-organized as a numbered list and references one external doc one level deep, but the quality-gates reference is inline within a step rather than clearly signaled as a separate navigable target, matching 'good structure; references mostly clear; minor organization gaps'.	4 / 5
	Total	16 / 20 Passed

Description

83%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 cleanly states both capability and trigger conditions in third person with concrete actions and natural trigger terms. It is strong overall, with only minor room to broaden trigger synonyms and deepen action specificity.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('run pre-push parity, monitor merged-commit CI, and leave repositories clean') but each stays at a high level without exhaustive coverage, matching the 'several specific actions; minor gaps' anchor rather than the comprehensive 5.	4 / 5
Completeness	Explicitly answers both what ('Land completed Fallow work... run pre-push parity, monitor merged-commit CI, and leave repositories clean') and when ('Use when asked to ship, merge, or move approved work to main') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Natural trigger phrases 'ship, merge, or move approved work to main' map well to what a user would say, but coverage is somewhat narrow with a few common variants missing, fitting the 'good keyword coverage; a few natural terms missing' anchor.	4 / 5
Distinctiveness Conflict Risk	The shipping-to-protected-main niche is mostly distinct with clear triggers, but 'merge'/'move work to main' could overlap with adjacent commit or review skills, fitting 'mostly distinct; minor overlap risk' rather than the minimal-conflict 5.	4 / 5
	Total	17 / 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: fallow-rs/fallow
Path: .claude/skills/ship/SKILL.md
Commit: 7e1e075

Reviewed: 3 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.