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

78%

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

81%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 highly actionable with strong validation gates and feedback loops for a risky shipping workflow, though it leans verbose in its explanatory prose and keeps all material in one long file.

Suggestions

Tighten the explanatory prose in step 2 and the Phase A/B rationale to concrete imperatives, trimming the 'why this can go wrong' narratives.

Consider moving the PR Description Format template and Commit Message Format into a reference file linked one level deep to reduce SKILL.md length.

Collapse the repeated 'do not ship / exit 1' rationale comments in the bash blocks to a single shared note.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and repo-specific, but step 2 and the Phase A/B prose carry lengthy explanations of why drift happens that could be tightened without losing the actionable guidance.	3 / 5
Actionability	Provides copy-paste-ready bash blocks, exact git and gh commands, and explicit per-job exit-code gating that covers the common shipping cases fully.	5 / 5
Workflow Clarity	A destructive/batch workflow with explicit validation checkpoints (sync check, post-rebase re-verify, Phase A status gating, Phase B lint+audit gating, final commit-content comparison) and feedback loops for error recovery.	5 / 5
Progressive Disclosure	Single well-sectioned file with clear navigation and no nested references, but at 159 lines it inlines the PR/commit templates that could be split out, leaving minor organization gaps.	4 / 5
	Total	17 / 20 Passed

Description

75%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 is specific and distinct, naming concrete shipping actions plus conditional safety gates, but it lacks an explicit 'Use when...' trigger clause, which caps completeness.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when the user wants to ship code to staging via a PR') to lift completeness above 3.

Include natural synonyms like 'pull request' alongside 'PR' to broaden trigger-term coverage.

Surface the staging target earlier so the trigger context is immediate.

Dimension	Reasoning	Score
Specificity	Lists five concrete actions — 'Commit, push, and open a PR to staging', 'runs the cleanup pass', 'the db-migrate safety review' — giving comprehensive coverage rather than minor gaps.	5 / 5
Completeness	The 'what' is clear, but there is no 'Use when...' trigger clause; 'when migrations changed' is a sub-step condition, not overall skill trigger guidance, so completeness caps at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Natural user-facing terms like 'commit', 'push', 'PR', 'staging', and 'in one shot' are present, but 'cleanup pass' and 'db-migrate safety review' are skill-internal jargon and a few natural synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche — a ship-to-staging pipeline with cleanup and migration-safety gates — with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	17 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 missing	Warning
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	13 / 16 Passed

Repository: simstudioai/sim
Path: .agents/skills/ship/SKILL.md
Commit: 417ae20

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.