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

68

Quality

83%

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

77%Weight 40%Scale 1-3

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

A strongly actionable, clearly sequenced multi-phase shipping workflow with solid validation checkpoints. Its main weaknesses are redundancy across the summary tables and a monolithic single-file structure with no progressive disclosure of detail into referenced files.

Suggestions

Collapse the Error Handling, Safety Measures, Red Flags, and Quick Reference tables — which restate the same prohibitions and steps — into a single concise table to reduce token cost.

Move the per-phase bash detail (e.g., the full archive/STATE-update scripts) into a referenced scripts/ file or a referenced doc, keeping SKILL.md as an overview that signals one-level-deep references.

Drop the trailing 'Bottom Line' and 'Integration with Other Skills' sections where the content duplicates the phase sequence already stated above.

DimensionReasoningScore

Conciseness

The body is mostly efficient actionable code and tables rather than concept explanations, but it is padded with overlapping summary tables (Error Handling, Safety Measures, Red Flags, Quick Reference, Bottom Line) that restate the same points, fitting the 'mostly efficient but could be tightened' anchor rather than the lean level.

2 / 3

Actionability

It provides concrete, executable bash throughout — directory checks, grep/sed/find pipelines, git tagging, archive copies — copy-paste ready and specific, matching the fully-executable anchor.

3 / 3

Workflow Clarity

The six phases are clearly sequenced with explicit validation checkpoints ('STOP. Do not proceed.', 'STOP if critical issues found') and feedback loops (audit-file verification with failure exit), matching the clear-sequence-with-explicit-validation anchor.

3 / 3

Progressive Disclosure

No bundle files exist and the skill is a single ~470-line SKILL.md with all detail inline and no signaled references; although sections are well organized, content that could be split out is monolithic, fitting the 'some structure but could be better organized' anchor and falling short of the well-signaled one-level-deep level.

2 / 3

Total

10

/

12

Passed

Description

90%Weight 40%Scale 1-3

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, well-formed third-person description that clearly states what the skill does and when to use it, with natural trigger terms. Its only weakness is that it names just two high-level actions rather than enumerating several concrete capabilities.

DimensionReasoningScore

Specificity

The description names the domain ('completed work for delivery') and two actions ('Package and finalize'), but does not list a comprehensive set of concrete actions, matching the 'Names domain and some actions, but not comprehensive' anchor rather than the multiple-specific-actions level.

2 / 3

Completeness

It explicitly answers both 'what' ('Package and finalize completed work for delivery') and 'when' via an explicit 'Use when a feature is done and ready to ship' trigger clause, satisfying the both-what-and-when anchor.

3 / 3

Trigger Term Quality

It surfaces natural phrases a user would actually say — 'done', 'ready to ship', 'deliver', 'finalize' — giving good coverage of common variations, matching the top anchor.

3 / 3

Distinctiveness Conflict Risk

The shipping/delivery niche with distinct triggers ('ship', 'ready to ship') is narrowly scoped and unlikely to fire for unrelated skills, matching the clear-niche anchor; it is not generic enough to fall to the overlap level.

3 / 3

Total

11

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

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.