CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

77%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 an exceptionally actionable, well-validated merge/runbook whose commands and error-recovery guidance are copy-paste ready. Its weaknesses are structural: it is a long, dense monolith whose serial-merge deep-dive and exit-code documentation belong in one-level-deep reference files.

Suggestions

Move the 'Serial merge of many pull requests' section and its stacked-branch/hunk-check detail into a reference file (e.g. references/serial-merge.md), keeping a short pointer plus the most common command in SKILL.md.

Split the per-script exit-code catalog (exit codes 1, 3, 4, 5 and their meanings) into a reference table and reference it from the relevant steps, since each script already documents its codes with --help.

Break the long multi-clause sentences in steps 1 and 6 into short bullet points for the failure paths (server-error retry, cancelled runs, flake vs. defect) to cut tokens without losing the guidance.

DimensionReasoningScore

Conciseness

The body contains no filler or explanations of concepts Claude already knows, but roughly 240 lines of dense run-on prose inline edge cases, exit-code catalogs, and failure paths that could be tightened or moved out. Per the guideline to penalize verbosity even when accurate, this fits 'mostly efficient but could be tightened' rather than 4.

3 / 5

Actionability

Fully executable, copy-paste-ready commands throughout ('node scripts/ship-rebase.mjs --pr <number> --if-needed --push', 'gh pr merge <number> --auto --squash --match-head-commit <reviewed sha> ...', 'gh run watch <run id> --exit-status'), with enumerated exit codes and concrete recovery commands covering the common cases. Matches the anchor-5 example.

5 / 5

Workflow Clarity

Ten clearly numbered steps plus a serial-merge sub-procedure, with explicit validation checkpoints and feedback loops for risky operations (pre-push checks, 'retry once with HK=0 git push', 'A second identical failure is a defect, not a flake', post-merge drift inspection in step 7). Destructive merge/rebase operations are well guarded, matching the anchor-5 pattern.

5 / 5

Progressive Disclosure

No bundle files exist and the skill is one monolithic document: the ~90-line 'Serial merge of many pull requests' section and the exit-code catalog are inlined rather than split into reference files. Structure is present (numbered steps, section header, internal cross-reference), so it sits at anchor 3 rather than 2, but content that should be separate is inline.

3 / 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 description: it names four concrete capabilities and gives an explicit 'Use when' trigger clause with natural terms. Its only weaknesses are mild — a couple of jargon-leaning actions and a few missing natural synonyms.

DimensionReasoningScore

Specificity

Lists four named actions ('Land completed Fallow work after review', 'run pre-push parity', 'monitor merged-commit CI', 'leave repositories clean'), matching the several-specific-actions anchor. Not 5 because 'pre-push parity' and 'leave repositories clean' are less concrete than the comprehensive anchor-5 example.

4 / 5

Completeness

Explicitly answers both 'what' (four concrete actions) and 'when' ('Use when asked to ship, merge, or move approved work to main') with concrete trigger phrases, mirroring the anchor-5 example structure. The 'when' clause is already explicit and specific, so 4 does not fit.

5 / 5

Trigger Term Quality

'Use when asked to ship, merge, or move approved work to main' supplies natural phrases users would say. A few natural synonyms ('land', 'publish', 'push to main') are missing, which keeps it below the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

Fallow-specific terms ('Fallow work', 'pre-push parity', 'merged-commit CI') carve a clear niche with distinct triggers. Minor overlap risk with generic merge/release skills keeps it below the minimal-conflict anchor 5.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 7 missing

Warning

Total

15

/

16

Passed

Repository

fallow-rs/fallow

Path

.agents/skills/ship/SKILL.md

Reviewed

Table of Contents

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.