ship

Commit, push, and open a PR to staging in one shot — runs the cleanup pass and, when migrations changed, the db-migrate safety review first

Quality

72%

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

77%

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

The body is highly actionable with a clearly sequenced, validated shipping workflow, but it is monolithic and verbose — inline justifications and templated reference material could be trimmed or moved to bundle files.

Suggestions

Tighten the inline rationale (e.g. the `grep … && echo` and polluted-branch explanations) to the essential gotcha without the surrounding argumentation.

Move the PR-description template and commit-message format into a referenced bundle file so the main body stays a lean overview.

Consider extracting the sync-check rebuild procedure into its own reference file, signaling it from the main step.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but heavily padded with inline justifications (e.g. the long "why not `grep … && echo`" and polluted-branch reasoning) that could be tightened without losing the gotcha value.	2 / 3
Actionability	Provides fully executable, copy-paste-ready bash (exact `bun run` audit lists, `gh pr create --base staging`, cherry-pick rebuild steps) — no pseudocode or vague direction.	3 / 3
Workflow Clarity	Steps 1–9 are explicitly sequenced with validation checkpoints (sync re-verify, Phase A/B abort-on-failure, final content check) and a feedback loop for error recovery (the rebuild procedure).	3 / 3
Progressive Disclosure	Well-organized into clear sections, but it is a ~150-line single file with no bundle references, and content like the PR-description template and commit-format reference could be split out rather than kept inline.	2 / 3
	Total	10 / 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 well-scoped to a distinct shipping workflow, but it lacks an explicit "Use when..." trigger clause and only covers a partial set of natural trigger terms.

Suggestions

Add an explicit "Use when..." clause, e.g. "Use when you want to commit, push, and open a PR to staging in one step."

Broaden trigger terms to include natural phrasings users actually say, such as "ship", "deploy", or "open a pull request".

Keep the project-specific jargon (db-migrate, cleanup pass) but pair it with the common terms so the trigger matches user intent.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Commit, push, and open a PR to staging" plus "runs the cleanup pass" and "the db-migrate safety review" — matching the multi-action anchor.	3 / 3
Completeness	Clearly states what the skill does, but the "when" is only implied — there is no explicit "Use when..." trigger clause, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Uses relevant natural terms (commit, push, PR, staging, migrations) but omits common variations a user might say (e.g. "ship", "deploy", "open a pull request") and leans on project-specific jargon (db-migrate, cleanup pass).	2 / 3
Distinctiveness Conflict Risk	The narrow niche — commit/push/PR to staging with mandatory cleanup and migration safety gates — is clearly distinct from general commit or PR skills and unlikely to trigger for the wrong skill.	3 / 3
	Total	10 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: simstudioai/sim
Path: .agents/skills/ship/SKILL.md
Commit: 6f514c1

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