launch-window-planner

Use when the user asks to "pick a launch date", "plan the launch window", or "set the embargo and lift time"; produces a candidate-window comparison table (conflict / tailwind / risk per window) built from industry-event cycles and the competitor launch calendar, a launch-week vs rolling-release format call, store-review buffer padding (labeled Estimated), and an embargo window definition (lift moment + timezone) submitted to the launch registry as a candidate. Not for judging the cultural moment itself — use trend-spotter; not for launch-day execution — use launch-day-conductor. 发布择时/发布窗口/竞品日历/禁运期窗口/审核缓冲

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

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 highly actionable with a clear sequenced workflow and well-structured one-level-deep references. The main weakness is conciseness: the registry/candidates-only caveat and scope exclusions are restated many times across sections.

Suggestions

State the "submits candidates only / never writes memory/launch-registry/ directly" rule once in the Skill Contract and reference it, instead of restating it in the intro, Scope guard, Instructions step 9, Save Results, and Reference Materials.

Collapse the opening paragraph and the dedicated Scope guard section into one non-redundant scope statement, since both enumerate the same "does not judge cultural moment / run launch day / own tier / write registry / compute RAMP profile" exclusions.

Trim the repeated cross-skill handoff links (launch-registry, trend-spotter appear multiple times) to a single Reference Materials / Next Best Skill listing.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and it assumes Claude's competence, but the "submits candidates / never writes the registry directly" message and the scope exclusions are repeated across the intro, Scope guard, Skill Contract, Instructions step 9, Save Results, and Reference Materials — padding that could be tightened.	2 / 3
Actionability	Concrete, executable guidance throughout: named connectors (producthunt.py, hn.py, gdelt.py), exact paths (memory/events/launches.ndjson), a specific operation ("operation: propose" to registry-events.py), a defined table shape (2-4 windows, conflict/tailwind/risk columns), and a buffer rule (2-3 day margin, cite App Store Connect / Play Console docs).	3 / 3
Workflow Clarity	A clear 9-step numbered sequence is paired with an explicit "Done when" checklist and a Measured/User-provided/Estimated labeling discipline that acts as a per-cell verification checkpoint, matching the anchor for a clear sequence with checklists.	3 / 3
Progressive Disclosure	Well-organized sections (Quick Start, Skill Contract, Data Sources, Instructions, Reference Materials, Next Best Skill) with clearly signaled, one-level-deep references (ramp-benchmark.md, CONNECTORS.md, SECURITY.md, skill-contract.md, sibling SKILL.md files); no bundle files exist in this skill directory to verify against, so structure is scored as presented.	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, complete, and clearly distinguished from sibling skills via explicit negative scope. Its only weakness is mild verbosity from the trailing Chinese tag line that duplicates already-stated keywords.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "produces a candidate-window comparison table (conflict / tailwind / risk per window)", "a launch-week vs rolling-release format call", "store-review buffer padding", and "an embargo window definition (lift moment + timezone)" — matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers both what (the comparison table, format call, buffer, embargo definition) and when ("Use when the user asks to..."), with an explicit trigger clause, matching the top anchor.	3 / 3
Trigger Term Quality	Quotes natural phrases a user would actually say — "pick a launch date", "plan the launch window", "set the embargo and lift time" — giving good coverage of natural trigger terms rather than jargon.	3 / 3
Distinctiveness Conflict Risk	Clear niche (launch timing) with explicit negative scope — "Not for judging the cultural moment itself — use trend-spotter; not for launch-day execution — use launch-day-conductor" — making conflict with sibling skills unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

75%

Warnings & errors only

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

Criteria	Description	Result
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: 26 suspicious	Warning
referenced_paths_exist	Referenced path issues: 11 missing, 11 deeper-than-1-level	Warning

	Total	12 / 16 Passed

Repository: aaron-he-zhu/aaron-marketing-skills
Path: launch/research/launch-window-planner/SKILL.md
Commit: 4a77c48

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

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.