ship

Commit and push the complete current-branch snapshot, open a ready PR, babysit it, merge when clean, then create a fresh branch. Use when the user asks to ship, publish, or hand off local changes. GitHub Actions auto-deploys beta and the docs site through the prebuilt publisher; other production promotion is manual.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

62%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 content is highly actionable with a clear, well-validated workflow, but it is held back by an inlined, verbose feedback-handoff section and the absence of any progressive-disclosure file structure that the length clearly warrants.

Suggestions

Extract the Latest-feedback handoff section into a references/ file (e.g. FEEDBACK-HANDOFF.md) and keep a concise summary with a single clearly-signaled link in SKILL.md.

Tighten the repeated disposition and eye-reaction rules into a compact checklist to reduce token cost while preserving the gating semantics.

Add a short one-line summary of /babysit-pr and /new-branch behavior at each delegation point so the reader need not always context-switch to the sibling skill.

Dimension	Reasoning	Score
Conciseness	Mostly efficient prose with concrete commands, but the Latest-feedback handoff section is heavily padded with repeated restatements of disposition rules and reaction-handling edge cases that could be condensed or moved to a reference.	3 / 5
Actionability	Provides concrete, executable commands (corepack pnpm ship:push, git fetch/rev-list, gh pr merge --squash --admin) and an explicit numbered procedure, with only minor gaps where behavior delegates to sibling skills without a one-line summary.	4 / 5
Workflow Clarity	A clearly sequenced 9-step flow with explicit validation checkpoints (fetch/rev-list stale-base check, 10-minute merge gate, babysit tick loop, post-merge branch rotation) and feedback loops for error recovery.	5 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets absent), and the document is a single ~290-line monolith with the large Latest-feedback handoff section inlined rather than split into a referenced file, making navigation harder.	2 / 5
	Total	14 / 20 Passed

Description

92%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: concrete multi-step actions, natural trigger terms, and explicit what/when guidance, with clear delineation from related shipping skills. The deployment-lane detail is mildly more than needed but does not undermine clarity.

Dimension	Reasoning	Score
Specificity	Names several concrete actions (commit/push, open ready PR, babysit, merge, new branch) plus a deployment-lane caveat; the GitHub-Actions auto-deploy detail adds specificity, though it slightly overreaches into deployment mechanics beyond the core action.	4 / 5
Completeness	Explicitly answers both what (commit/push/PR/babysit/merge/new-branch) and when ('Use when the user asks to ship, publish, or hand off local changes'), with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural triggers including 'ship', 'publish', and 'hand off local changes', which are exactly the phrases a user would say when needing this skill.	5 / 5
Distinctiveness Conflict Risk	The end-to-end ship/merge/branch-rotation niche is clearly distinct from sibling skills (/ship-now, /ship-and-monitor, /babysit-pr), and the manual-vs-auto deployment boundary reduces wrong-skill triggering.	5 / 5
	Total	19 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: BuilderIO/agent-native
Path: .agents/skills/ship/SKILL.md
Commit: bb282b1

Reviewed: ~20 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.