CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

launch-day-conductor

Use when the user asks to "run my launch day", "build a launch day runbook / war room", or "decide CONTINUE or ROLLBACK after the push"; produces a pre-conditions gate check (launch-readiness-auditor SHIP verdict + the authoritative date in launch-registry — missing either stops the skill), a dated hour-blocked runbook with owners (morning irreversible pushes, daytime monitoring loop, evening consolidation), a forced observation-window verdict after every irreversible action against pre-declared kill criteria, a P0-P3 incident ladder with rollback playbooks, and T-0 status lines for the registry proposal protocol. Not for channel submission content and platform rules — use community-launch-runner; not for media replies — use press-media-relations. 发布日runbook/作战室/观察窗/回滚裁决/发布日指挥

Quality

84%

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

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.

A disciplined process skill: an eight-step launch-day workflow with hard gates, per-action receipt and verdict semantics, and explicit open-join consolidation rules. Its weaknesses are systematic repetition of the registry-proposal caveat and reliance on jargon and external files whose formats (proposal event lines, kill-criterion declarations) are never exemplified.

Suggestions

State the 'propose via registry-events.py, never canonical writes' rule once (e.g. in the Skill Contract Writes bullet) and reference it from the other sections instead of repeating the full clause five times.

Add one concrete example of a registry proposal event line and one example observation-window block (duration + kill criterion + resulting verdict) so steps 4 and 6 are copy-paste executable.

Collapse the repeated cross-skill links (launch-readiness-auditor, launch-monitor, launch-registry each linked 4-5 times) into the Reference Materials section and link each sibling once inline at first mention.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows and is information-dense, but the 'authorized operation: propose request to registry-events.py — never canonical registry files' caveat is repeated across five separate sections (Scope guard, Writes, instruction 6, Save Results, Reference Materials), and sibling-skill links (launch-readiness-auditor, launch-monitor, launch-registry) each appear four to five times. That is systematic redundancy that could be consolidated, matching the mostly-efficient-but-could-be-tightened anchor rather than minor over-explanation.

3 / 5

Actionability

For an instruction-only skill the guidance is largely executable: an exact runbook column list, the receipt enum 'succeeded | partial | failed | unknown', the save path pattern 'memory/launch/launch-day-conductor/YYYY-MM-DD-<product-or-launch>.md', and an explicit NEEDS_INPUT stop. Minor gaps remain — no example registry proposal event line for registry-events.py and no example observation-window duration or kill-criterion format — so it is mostly-executable rather than copy-paste ready.

4 / 5

Workflow Clarity

The eight instructions form a clearly ordered sequence with explicit validation checkpoints and feedback loops: a hard pre-conditions gate ('Missing either, a FIX/BLOCK verdict, or any hash mismatch → stop with NEEDS_INPUT'), a forced CONTINUE-or-ROLLBACK verdict per irreversible action against pre-declared criteria, and open-lane joins at consolidation ('Missing or partial | unknown receipts keep that lane and the overall join OPEN'). This matches the explicit-validation-and-feedback-loops anchor.

5 / 5

Progressive Disclosure

The ~75-line body is well sectioned with an annotated Reference Materials list of one-level-deep links, and dense material (connectors, RAMP details, action-control semantics) is delegated to those files. However every link points outside the skill directory into a parent repo (no bundle files exist here to verify), and the long Scope guard and Data Sources paragraphs plus the multi-repeat handoff sections leave minor organization gaps, placing it at good-structure rather than cleanly-split.

4 / 5

Total

16

/

20

Passed

Description

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

An unusually strong description: explicit third-person trigger phrases, a comprehensive and concrete list of outputs, and explicit conflict-avoidance boundaries against sibling skills. Its only weakness is heavy internal jargon (T-0, registry proposal protocol, observation-window verdict) that narrows the natural-vocabulary surface a lay user might produce.

Suggestions

Add one or two lay-user phrasings (e.g. 'go/no-go decision', 'what to do on release day') alongside the jargon-heavy terms.

Trim the dense parenthetical inside the gate-check clause ('launch-readiness-auditor SHIP verdict + the authoritative date in launch-registry — missing either stops the skill') so the trigger list reads faster.

DimensionReasoningScore

Specificity

The description enumerates five distinct concrete deliverables — 'a pre-conditions gate check', 'a dated hour-blocked runbook with owners', 'a forced observation-window verdict', 'a P0-P3 incident ladder with rollback playbooks', and 'T-0 status lines' — covering the skill's full output surface. This matches the comprehensive-coverage anchor; it is not 4 because there are no meaningful gaps in the action list.

5 / 5

Completeness

Both halves are explicit: 'Use when the user asks to …' gives concrete trigger phrases, and 'produces a pre-conditions gate check … runbook … verdict … incident ladder … status lines' states exactly what it does. It even adds negative triggers ('Not for channel submission content'), exceeding the both-what-and-when anchor rather than sitting at the could-be-more-specific level below.

5 / 5

Trigger Term Quality

It quotes natural user phrases ('run my launch day', 'build a launch day runbook / war room', 'decide CONTINUE or ROLLBACK after the push') and adds bilingual keywords (发布日runbook/作战室/回滚裁决). Jargon-heavy constructions like 'T-0 status lines' and 'registry proposal protocol' and missing common variants like 'go/no-go' keep it below the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (conducting launch day itself between the T-1 gate and T-0 monitoring) and explicitly de-scopes the nearest neighbors ('Not for channel submission content and platform rules — use community-launch-runner; not for media replies — use press-media-relations'). This is the clear-niche-with-distinct-triggers anchor, not merely minor overlap risk.

5 / 5

Total

19

/

20

Passed

Validation

75%

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

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 32 suspicious

Warning

referenced_paths_exist

Referenced path issues: 4 missing, 4 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

launch/mobilize/launch-day-conductor/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.