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 ./.agents/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.

A lean, well-sequenced shipping runbook with genuine validation checkpoints for an irreversible merge-to-main operation. Its main weakness is actionability: steps name what to do without the executable commands needed to do it.

Suggestions

Add the specific git commands for key steps (e.g. the signed-commit and protected-main merge invocation) so guidance is copy-paste ready rather than directive-only.

Add an explicit error-recovery branch for failed validation — what to do when pre-push parity fails or merged-commit CI goes red.

Group the flat numbered list under a couple of sub-headers (e.g. 'Pre-merge', 'Merge & monitor', 'Cleanup') to improve scannability.

Dimension	Reasoning	Score
Conciseness	Eight terse numbered steps plus a single caution sentence with no padding or restated common knowledge; every token earns its place.	5 / 5
Actionability	Steps are concrete directives (e.g. 'Create signed conventional commits only') but lack executable commands or specifics like git flags, leaving key execution details implicit.	3 / 5
Workflow Clarity	A clear 8-step sequence with validation checkpoints (re-run checks, monitor CI, inspect for conflict markers) plus a completion gate, but no explicit error-recovery feedback loop when validation fails.	4 / 5
Progressive Disclosure	Well-organized single-purpose skill under 50 lines with one clearly signaled inline doc reference; lacks sub-section headers that would push it to a 5.	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.

A strong, concise description that clearly states multiple concrete capabilities and provides explicit natural-language trigger conditions. It is distinct and well-scoped, with only minor room to broaden trigger synonyms.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'run pre-push parity, monitor merged-commit CI, and leave repositories clean' — comparable to the score-4 anchor with multiple specific actions and minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what ('Land completed Fallow work... monitor merged-commit CI... leave repositories clean') and when ('Use when asked to ship, merge, or move approved work to main') with concrete triggers.	5 / 5
Trigger Term Quality	'Use when asked to ship, merge, or move approved work to main' provides good natural trigger phrases, though synonyms like deploy/push are absent.	4 / 5
Distinctiveness Conflict Risk	Targets a distinct post-review shipping niche with specific triggers; minor overlap risk with generic merge/deploy skills.	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: .agents/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.