CtrlK
BlogDocsLog inGet started
Tessl Logo

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

72

Quality

92%

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

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

The body is a well-structured, actionable workflow with clear sequencing and validation, scoring at the top on actionability, workflow clarity, and progressive disclosure. Its only weakness is conciseness — repeated scope-guard statements and dense parentheticals could be trimmed without losing clarity.

Suggestions

Consolidate the launch-window-planner / scope-guard redirect so it appears once (e.g., in the Scope guard paragraph) rather than repeating in the intro, step 7, and Next Best Skill.

Trim dense parenthetical asides (e.g., the inline tier definitions and channel-intensity glosses) into a single compact reference table to reduce token load.

Move the cross-skill routing list into the existing Reference Materials section instead of restating handoff targets inside instruction steps.

DimensionReasoningScore

Conciseness

The body is information-dense but verbose: the scope-guard and launch-window-planner redirect recur in the intro, step 7 ('No calendar dates — the date choice belongs to launch-window-planner'), and Next Best Skill, and dense parentheticals pad many lines; it is mostly efficient but could be tightened, so it sits at the 'could be tightened' anchor rather than the lean top anchor.

2 / 3

Actionability

Concrete guidance throughout — specific deliverables, exact memory paths, an authorized 'operation: propose' request to 'registry-events.py', and a copy-ready rollback condition ('roll back if error rate exceeds the pre-launch baseline by the agreed multiple for 30+ minutes'); as an instruction-only skill this is fully actionable, so the absence of code is not penalized.

3 / 3

Workflow Clarity

An explicit 8-step sequence is paired with validation checkpoints (check the existing stage/date record in step 1, the Tier-1 spacing guardrail in step 2) and a 'Done when' completion checklist, matching the 'clear sequence with explicit validation steps' anchor.

3 / 3

Progressive Disclosure

No bundle files are present, but the body is organized into well-labeled sections (Quick Start, Skill Contract, Data Sources, Instructions, Save Results, Reference Materials, Next Best Skill) with one-level-deep references clearly signaled, satisfying the 'well-organized sections' route to the top anchor.

3 / 3

Total

11

/

12

Passed

Description

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

The description is specific, trigger-rich, and complete, with explicit 'Use when...' guidance and strong negative-scope routing that distinguishes it from sibling skills. It is an exemplar of the rubric's top anchors.

DimensionReasoningScore

Specificity

Lists multiple concrete outputs — 'tier decision', 'launch-type declaration', 'effort calibration matrix', 'D0/W1/M1 KPI targets', 'risk register', and 'T-8w to T+4w timeline skeleton' — matching the 'Lists multiple specific concrete actions' anchor.

3 / 3

Completeness

An explicit 'Use when the user asks to...' clause states when to invoke it, and the produced outputs state what it does, clearly answering both what and when; it is not the level below because the when-trigger is explicit, not implied.

3 / 3

Trigger Term Quality

Natural user phrasing is quoted directly — 'plan my launch tier', 'how big should this launch be', 'build a launch risk register with kill criteria' — giving good coverage of terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Negative scope ('Not for picking the launch date or window — use launch-window-planner; not for creator-channel launch campaigns — use campaign-planner') carves a clear niche and routes overlap away, making wrong-skill triggering unlikely.

3 / 3

Total

12

/

12

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.

Validation12 / 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
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.