CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

An exceptionally actionable, well-gated ship workflow: every step has executable commands, explicit abort conditions, and feedback loops for error recovery, with heavy emphasis on repo-specific gotchas that Claude could not infer. The main improvement opportunities are trimming rationale that re-explains basic shell/git behavior and offloading the two large inline procedures (sync-fix rebuild, scrub patterns) to reference files.

Suggestions

Trim parentheticals that re-explain known shell/git semantics (e.g., 'a bare wait swallows child exit codes', 'plain git log is newest-first') — keep only the non-obvious repo-specific gotchas to push conciseness toward 5.

Move the step-2 sync-fix rebuild procedure and the 'What to Omit' scrub grep patterns into reference files (e.g., references/sync-fix.md, references/scrub.md), keeping a one-line trigger in SKILL.md, to reduce the always-loaded token cost.

Condense the long prose paragraph in step 6 warning against 'mship:generate' into a short bulleted do/don't list — the same information reads faster and is less likely to be skimmed past.

DimensionReasoningScore

Conciseness

The body is dense with zero padding — every step is operational ('A failing test aborts ship', 'Do not ship with any generator or audit failing'). However, several parentheticals explain shell/git semantics Claude already knows: 'a bare wait swallows child exit codes', 'plain git log is newest-first', 'git stash drop rejects a raw SHA'. These are minor over-explanations that could be trimmed, matching anchor 4. Not 3: the overwhelming majority of tokens carry repo-specific, non-obvious information (shared stash lists across worktrees, ENOENT-prone umbrella generator); not 5: some rationale paragraphs re-derive known git behavior.

4 / 5

Actionability

Fully executable, copy-paste-ready guidance throughout: exact commands with exit-code gating ('bun run lint || { echo "❌ lint failed — do not ship"; exit 1; }'), the stash-pinning bash block, scrub grep regexes, the verbatim PR template, and the exact 'gh pr create --base staging' invocation. Not 4: there are no gaps — even failure paths specify exactly what to run and what aborts ship.

5 / 5

Workflow Clarity

A 9-step sequence with explicit validation checkpoints and feedback loops at every risky point: re-verify 'git log --oneline origin/staging..HEAD' after rebase, 'abandon it and rebuild' on stray commits, 'fix the cause (never silence it) and re-run' after audit failures, and the final PR content check that loops back ('redo step 2's fix and git push --force-with-lease'). Destructive operations (history rewrite, force-push, branch deletion) all have validation, so the destructive-operation cap does not apply. Not 4: checkpoints are explicit, not merely present.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), and the body's cross-skill references ('/cleanup', '/test-audit', '/db-migrate') are clearly signaled and one level deep. The single file is well-sectioned (Your Task, Commit Message Format, What to Omit, PR Description Format, Important Notes) and navigable. Not 5: at ~186 lines, substantial standalone procedures — the step-2 sync-fix rebuild and the 'What to Omit' scrub patterns — are inlined rather than offloaded to reference files; not 3: organization is good, not merely present.

4 / 5

Total

18

/

20

Passed

Description

71%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 specific, well-scoped description for a one-shot ship command: it names concrete actions and the conditional safety gates. Its main weaknesses are the complete absence of explicit when-to-use trigger guidance (which caps completeness) and keyword coverage that leans on the 'PR' abbreviation without the natural 'pull request' phrasing or synonyms.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to ship, submit, or send changes to staging' — without one, completeness is capped at 3.

Include the spelled-out 'pull request' alongside 'PR' and add a synonym or two ('submit changes', 'publish branch') to broaden natural trigger coverage.

Briefly signal the hidden safety behavior (sync-checking for stray commits) so users searching for 'fix polluted branch' hints can discover the skill's scope.

DimensionReasoningScore

Specificity

Quotes: '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'. Multiple specific concrete actions (commit, push, open PR to staging, cleanup pass, conditional db-migrate safety review) with comprehensive coverage of the ship workflow. Not 4: unlike 'minor gaps in coverage', every core action plus the gating behavior is named.

5 / 5

Completeness

Quote: 'Commit, push, and open a PR to staging in one shot'. The 'what' is clearly and concretely stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance — 'when migrations changed' is conditional orchestration logic, not when-to-use guidance. Per the judging guidelines this caps completeness at 3. Not 4: the 'when' is not merely implicit-and-specific, it is absent.

3 / 5

Trigger Term Quality

Quotes: 'Commit, push, and open a PR to staging'. Good keyword coverage with natural terms users say (commit, push, PR, staging, ship), but the spelled-out 'pull request' phrase and common variants (e.g., 'submit', 'publish', 'deploy') are missing. Not 5: coverage is good but not comprehensive with synonyms.

4 / 5

Distinctiveness Conflict Risk

Quote: 'open a PR to staging in one shot — runs the cleanup pass and, when migrations changed, the db-migrate safety review first'. The PR-to-staging orchestration with its gates is a clear niche, but the leading 'commit, push' phrasing overlaps generic commit/PR skills. Mostly distinct with minor overlap risk, matching anchor 4 rather than 5's 'minimal conflict risk'.

4 / 5

Total

16

/

20

Passed

Validation

81%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 2 missing

Warning

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

13

/

16

Passed

Repository

simstudioai/sim

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.