CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-ship

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

59

Quality

68%

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 ./skills/skill-ship/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%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 a strong, actionable multi-phase workflow with excellent validation checkpoints and feedback loops. Its main weakness is redundancy from multiple summary tables restating the same steps, and the absence of any bundle files to split detail out of the main file.

Suggestions

Collapse Quick Reference, Safety Measures, Red Flags, and The Bottom Line into a single concise summary to reduce redundancy.

Move the longer bash archiving/audit blocks into a scripts/ bundle file referenced from the main body to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly efficient concrete bash, but restates the same process several times across Quick Reference, Safety Measures, Red Flags, and The Bottom Line tables, adding padding that could be trimmed.

3 / 5

Actionability

Provides concrete, copy-paste-ready bash for each phase (checking .octo, grepping STATE.md, invoking orchestrate.sh, mkdir/cp archiving, sed/git tag), with only minor templated placeholders in heredocs leaving small gaps.

4 / 5

Workflow Clarity

A clearly sequenced six-phase process with explicit STOP validation checkpoints, audit-result verification, and feedback loops (audit failed -> resolve -> retry), plus an error-handling table for recovery.

5 / 5

Progressive Disclosure

Well-organized with clear phase headers and navigational tables, and external tool paths are signaled; however it is a single large monolithic file with no bundle files to offload detail, leaving minor organization gaps for a >50-line skill.

4 / 5

Total

16

/

20

Passed

Description

62%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 third-person, concise, and answers both what and when with a natural trigger phrase. It is held back by limited action specificity and a thin set of trigger-term variations rather than a comprehensive trigger list.

Suggestions

Add 1-2 more concrete actions (e.g., 'run a Multi-AI security audit, capture lessons, archive state') to raise specificity.

Broaden the trigger clause with synonyms users actually say, e.g. 'use when the user says ship, finalize, deliver, or mark as done'.

DimensionReasoningScore

Specificity

Names the delivery domain with two concrete verbs ("Package and finalize completed work for delivery"), but stops at 1-2 high-level actions rather than enumerating several specific shipping steps.

3 / 5

Completeness

Both "what" (package and finalize completed work for delivery) and an explicit "when" ("use when a feature is done and ready to ship") are present, though the trigger clause covers essentially one scenario rather than a concrete set of phrases.

4 / 5

Trigger Term Quality

Includes natural phrases a user would say ("feature is done", "ready to ship"), but misses common variations like "finalize", "deliver", "complete the project", so coverage is partial.

3 / 5

Distinctiveness Conflict Risk

The shipping/finalization niche with a "ready to ship" trigger is mostly distinct from build/review skills, with only minor overlap risk against general delivery or deploy skills.

4 / 5

Total

14

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
nyldn/claude-octopus
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.