CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

launch-tier-planner

Use when the user asks to "plan my launch tier", "how big should this launch be", or "build a launch risk register with kill criteria"; produces a tier decision (Tier 1 flagship all-channel / Tier 2 targeted / Tier 3 changelog-level), a launch-type declaration (new-product / feature / relaunch / partnership with co-marketing split), an effort calibration matrix (tier to channel intensity and asset scope), D0/W1/M1 KPI targets (labeled Estimated), a risk register (likelihood x blast-radius, owners, mitigations, kill criteria / rollback thresholds), and a T-8w to T+4w timeline skeleton. Not for picking the launch date or window — use launch-window-planner; not for creator-channel launch campaigns — use campaign-planner. 发布分级/发布类型/风险登记册/kill criteria

Quality

88%

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

78%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 well-structured, information-dense instruction skill: the workflow is clearly sequenced with a completion checklist, guidance is concrete with exact paths and checkable example criteria, and detail is properly deferred to annotated external references. The main costs are repetition of the registry/handoff mechanics across sections and the absence of executable syntax for the registry-events.py proposal and filled examples of the matrix and risk register.

Suggestions

State the registry-proposal mechanic once (e.g., in the Skill Contract's Writes bullet) and reference it from step 8 and Save Results instead of repeating the full 'operation: propose / never writes directly' wording three times.

Show the exact registry-events.py invocation — command line and ndjson payload shape — since the skill instructs an 'authorized operation: propose request' in three places without ever giving the syntax.

Add one filled example row for the effort calibration matrix (tier → channel intensity / asset scope) and one for the risk register (likelihood × blast-radius, owner, mitigation, kill criterion) so the output shape is copy-paste concrete.

DimensionReasoningScore

Conciseness

The body is dense and domain-specific with no explanations of concepts Claude already knows, but it repeats itself: the registry-proposal mechanic ("operation: propose request to registry-events.py … never written directly") appears in Writes, step 8, and Save Results; the RAMP R sub-items are restated in the intro and Reference Materials; and the launch-window-planner handoff is made in four separate places. That is minor trimmable redundancy (anchor 4) rather than the every-token-earns-its-place leanness of anchor 5.

4 / 5

Actionability

Guidance is concrete — the three-question tier test with named tiers, the exact save path (memory/launch/launch-tier-planner/YYYY-MM-DD-<launch-name>-tier-plan.md), a checkable example kill criterion ("roll back if error rate exceeds the pre-launch baseline by the agreed multiple for 30+ minutes"), and the KPI phrasing rule ("vs your own trailing signup rate", not "a good launch gets N signups"). However, registry-events.py is invoked by name three times with no command or payload syntax, and neither the effort calibration matrix nor a risk-register row gets a filled example, leaving minor gaps (anchor 4).

4 / 5

Workflow Clarity

Eight well-sequenced steps run from scope confirmation through registry submission, backed by a "Done when" completion checklist, a pre-flight check that the plan does not contradict the existing registry record (step 1), and an explicit conflict rule ("recommend the lower tier and say why"). Writes are gated on user confirmation and the skill is neither destructive nor batch, so no cap applies — but there is no explicit verification or feedback loop after the registry proposal is submitted (e.g., what to do if it is rejected), which keeps this at anchor 4 rather than 5.

4 / 5

Progressive Disclosure

The body is a clear overview that appropriately splits detail into one-level-deep, purpose-annotated references — RAMP framework, connectors, security policy, save template, and handoff format all live in separate files (ramp-benchmark.md, CONNECTORS.md, SECURITY.md, skill-contract.md), each linked with a description of what it provides. No bundle files ship inside this skill, sections are well organized, and the Reference Materials and Next Best Skill lists make navigation easy, matching the anchor-5 structure.

5 / 5

Total

17

/

20

Passed

Description

100%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 exemplary description: concrete enumerated outputs, verbatim natural trigger phrases, explicit when/what coverage, and explicit disambiguation against named sibling skills. The only blemish is that the trailing bilingual keyword string (发布分级/发布类型/风险登记册/kill criteria) duplicates the summary field's content as a tag dump, but it adds trigger synonyms rather than vague fluff.

DimensionReasoningScore

Specificity

The description enumerates every concrete output — "tier decision (Tier 1 flagship all-channel / Tier 2 targeted / Tier 3 changelog-level)", "launch-type declaration (new-product / feature / relaunch / partnership with co-marketing split)", "effort calibration matrix", "D0/W1/M1 KPI targets", "risk register (likelihood x blast-radius, owners, mitigations, kill criteria / rollback thresholds)", and a "T-8w to T+4w timeline skeleton" — with parenthetical detail on each. This is comprehensive coverage of specific actions, above anchor 4's 'minor gaps in coverage'.

5 / 5

Completeness

Both halves are explicit: "Use when the user asks to…" with three concrete trigger phrases answers 'when' maximally, and the "produces…" list answers 'what' in full, matching the anchor-5 example shape. It even adds explicit negative scope ("Not for picking the launch date or window").

5 / 5

Trigger Term Quality

It quotes verbatim natural user phrases — "plan my launch tier", "how big should this launch be", "build a launch risk register with kill criteria" — and supplements them with domain synonyms (kill criteria, rollback thresholds, launch tier) plus bilingual terms (发布分级/风险登记册). Coverage of natural trigger terms, including synonyms, is comprehensive rather than merely good.

5 / 5

Distinctiveness Conflict Risk

The niche (launch sizing/tiering) is distinct and the description actively routes conflicts away: "Not for picking the launch date or window — use launch-window-planner; not for creator-channel launch campaigns — use campaign-planner." Named-sibling exclusions give it minimal conflict risk.

5 / 5

Total

20

/

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: 28 suspicious

Warning

referenced_paths_exist

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

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

launch/research/launch-tier-planner/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.