CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-ship

Package and finalize completed work for delivery — use when a feature is done and ready to ship

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/skill-ship/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A highly actionable, well-sequenced shipping workflow with strong validation checkpoints and explicit stop conditions throughout. Its weaknesses are token efficiency and structure: four recap sections repeat the same process, and the monolithic single-file layout inlines a large audit script and reference material that belong in bundle files.

Suggestions

Move the ~60-line Phase 2 audit bash block into a scripts/ helper (e.g., scripts/run-ship-audit.sh) and invoke it with arguments from SKILL.md, cutting the body roughly in half and enabling progressive disclosure.

Collapse the overlapping recap sections ("Red Flags", "Safety Measures", "Quick Reference", "The Bottom Line") into a single short summary table, and drop the "When to Use" list that duplicates the frontmatter trigger field.

Replace the prose-only verification in Phase 2 Steps 3-4 with a concrete command that greps the validated delivery-*.md report for COMPLETE launcher status, closing the workflow's one explicit validation gap.

DimensionReasoningScore

Conciseness

The phase instructions are dense and functional with no explanation of concepts Claude already knows, but several sections are padded recaps: "When to Use" duplicates the frontmatter trigger, and "Red Flags", "Safety Measures", "Quick Reference", and "The Bottom Line" each restate the same process. Mostly efficient but with unnecessary repetition that could be tightened, matching anchor 3.

3 / 5

Actionability

Nearly all guidance is copy-paste-ready: exact bash for readiness checks, the audit dispatch, the lessons append, archival, and the git tag, plus concrete markdown output templates. Minor gaps keep it below fully executable — Phase 2 Step 4's "Read validation file and present" and Step 3's COMPLETE-status check give no concrete command, and the $USER_* lesson inputs are referenced without provenance.

4 / 5

Workflow Clarity

Six phases are clearly sequenced with explicit STOP conditions, ready-state validation, audit exit-status verification, a post-audit source-unchanged recheck, and an error-handling table for recovery. The audit-report verification in Phase 2 Steps 3-4 is described in prose rather than as an executable check, a minor validation gap that fits anchor 4 rather than the fully explicit anchor 5.

4 / 5

Progressive Disclosure

No references/, scripts/, or assets/ directories exist — everything lives in one 545-line SKILL.md. Section headers and tables provide reasonable internal structure, but content that clearly belongs in separate files is inlined, most notably the ~60-line audit bash block that should be a scripts/ helper, alongside the redundant recap tables.

3 / 5

Total

14

/

20

Passed

Description

78%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 concise, third-person description that clearly answers both what the skill does and when to use it, with a natural trigger clause. Its main weakness is specificity — the generic "package and finalize" phrasing hides the skill's distinctive multi-AI audit, lessons, and archival workflow and leaves some overlap risk with adjacent delivery skills.

DimensionReasoningScore

Specificity

"Package and finalize completed work for delivery" names the domain with two concrete actions (package, finalize), matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor. It omits the skill's actual capabilities (security audit, lessons capture, archival, checkpoint) that would justify a 4.

3 / 5

Completeness

It explicitly answers both questions: what ("Package and finalize completed work for delivery") and when ("use when a feature is done and ready to ship") with a concrete trigger phrase. This matches the anchor for clearly and explicitly answering both what AND when.

5 / 5

Trigger Term Quality

Natural phrases users would say are present — "done", "ready to ship", "ship", "delivery", "feature is done" — giving good keyword coverage. Common synonyms like "finalize", "wrap up", "release", or "deploy" are missing, keeping it below the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

The shipping/finalization niche is mostly distinct with ship/delivery/done triggers, but "finalize completed work" is broad enough to overlap with closely related delivery, deployment, or release skills. Minor overlap risk fits anchor 4 rather than the clear-niche anchor 5.

4 / 5

Total

16

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (557 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

nyldn/claude-octopus

Path

.claude/skills/skill-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.