CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

launch

Shipyard's governed delivery pipeline — converge the mission, synthesize a durable spec, decompose vertical-slice tickets with blocking edges, run the frontier in parallel via team, close with verification, and report with a full decision log. Two entry gates — the yard gate (drydock audit) and the fog gate (an effort whose destination is unclear is routed to /ask-navigator before this pipeline starts). Humans own the checkpoints where there is no unique answer or the error cost is severe; agents continuously run everything repeatable and acceptable-by-evidence.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/launch/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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 an impressively rigorous orchestration document — every phase, gate, and failure path is specified with concrete commands, templates, and validation checkpoints. Its weaknesses are token economy (rhetorical prose and restated external contracts) and structure (a single monolithic file where several detailed contracts belong in references).

Suggestions

Move the restated drydock document-language contract and the detailed C4/Team interaction mechanics into references/ files, keeping only the decision rule and a pointer inline.

Trim rhetorical flourishes ('a new name for a rejected idea is not a new idea', nautical metaphors) to declarative rules — roughly a third of the prose could compress without losing guidance.

Add one compact worked example each of a frontier question round and a ticket with blockedBy edges, to make the abstract protocol terms concrete.

DimensionReasoningScore

Conciseness

The body packs rules densely, but recurring rhetorical flourishes ('signing what was understood, not what was said, is how misreads become load-bearing') and restated external contracts (the full drydock document-language resolution order) are over-explanation that could be tightened or referenced. Mostly efficient, with noticeable trimming opportunities throughout.

3 / 5

Actionability

Concrete anchors are frequent: the executable audit command 'node scripts/shipyard-audit.mjs [repoRoot]' with exit-code semantics, the spec section template, the lesson-to-slot table, exact status enums, and file paths. Minor gaps: no worked example of a frontier question, a ticket, or a completion report to anchor the abstract protocol terms.

4 / 5

Workflow Clarity

Phases 0-5 are explicitly sequenced with validation checkpoints throughout: the blocking yard audit with exit-0/exit-1 consumption, C2/C3 approval stops, the two-axis review gate with repair rule, the three-strike failure halt, and closeout verification plus the sediment checklist. Error-recovery paths (C4 exit and re-entry, session death, fog gate) are explicitly specified.

5 / 5

Progressive Disclosure

Sections are well-organized by phase and cross-skill references are clearly signaled one level deep, but this is a ~180-line monolithic file with no bundle files: detailed contracts (document-language resolution rules, C4/Team mechanics, the sediment slot table) are inlined where reference files belong, and the file itself is long enough to need splitting.

3 / 5

Total

15

/

20

Passed

Description

67%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 highly specific and clearly delineates a distinct niche, but it is written in dense ecosystem jargon and lacks any explicit 'use when' trigger guidance, so a user (or the model) has no natural entry phrases to invoke it by. It describes comprehensively what the pipeline does while leaving when to start it implicit.

Suggestions

Add an explicit trigger clause such as 'Use when the user asks to deliver, plan and implement, or ship a change end-to-end from a mission brief' with natural phrasings users would actually say.

Reduce private jargon in the opening (yard gate, fog gate, shipyard) or pair each term with a plain-language gloss so the description is self-contained for a reader outside the ecosystem.

The closing sentence about human/agent ownership is governance philosophy, not invocation guidance — replace or shorten it in favor of when-to-use information.

DimensionReasoningScore

Specificity

Lists six concrete pipeline actions — 'converge the mission, synthesize a durable spec, decompose vertical-slice tickets with blocking edges, run the frontier in parallel via team, close with verification, and report with a full decision log' — comprehensive coverage of its domain.

5 / 5

Completeness

The 'what' is clearly stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance — the fog-gate sentence only describes when NOT to run (routing to /ask-navigator). Per the judging guideline, missing explicit trigger guidance caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords exist (delivery pipeline, spec, tickets, verification, mission brief) but the natural phrases a user would actually say ('ship this change', 'plan and implement a feature') are missing, and entry terms like 'yard gate', 'fog gate', and 'drydock' are private ecosystem jargon. Missing common variations and synonyms.

3 / 5

Distinctiveness Conflict Risk

Clear niche — a governed delivery pipeline with two named entry gates — and it explicitly hands off neighboring cases (unclear destination routed to the navigator), so conflict risk with other skills is minimal.

5 / 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

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

Yeachan-Heo/oh-my-claudecode

Path

skills/launch/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.