CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

81%

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

67%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 presents a clear, well-sequenced 9-step planning workflow with concrete artifacts, source labeling, and good handoff/termination hygiene. Its weaknesses are repetition of the registry-proposal and scope-guard rules across four sections, and references to connector scripts and docs that are not actually present in the skill bundle.

Suggestions

State the registry-proposal rule once (e.g., in the Skill Contract's Writes bullet) and have the intro, Instruction 9, and Save Results refer to it instead of restating it, cutting the repeated "never writes memory/launch-registry/ directly" clauses.

Show the exact invocation for one connector (e.g., a sample `python scripts/connectors/hn.py ...` call) and the shape of the `operation: propose` request to registry-events.py, so the submit step is executable without reading CONNECTORS.md.

Either include the referenced connector scripts and reference docs (ramp-benchmark.md, CONNECTORS.md) in the skill bundle or trim the links to only those that ship, so the Reference Materials section matches the actual bundle.

DimensionReasoningScore

Conciseness

The body is domain-specific rather than padding with known concepts, but the registry-proposal rule is restated in the intro, the Writes bullet, Instruction 9, and Save Results, and "It works one lever ... and hands off" appears twice in adjacent paragraphs. This matches anchor 3 (mostly efficient but could be tightened) rather than anchor 4, where over-explanation would be only minor.

3 / 5

Actionability

Guidance is mostly executable: named connector scripts (scripts/connectors/producthunt.py, hn.py, gdelt.py), concrete write paths (memory/launch/launch-window-planner/YYYY-MM-DD-<topic>.md), a specified 2-4 window × conflict/tailwind/risk table, and a stated 2-3 day review margin labeled Estimated. Minor gaps: the actual invocation syntax for the connectors and for the registry-events.py `operation: propose` request is never shown.

4 / 5

Workflow Clarity

A clear 9-step sequence (inventory constraints → scan events → map competitors → build table → pad latency → handle lore → choose format → define embargo → submit) with per-step source labeling and an explicit "Done when" checklist as a completion checkpoint. It falls short of anchor 5 because there are no feedback/error-recovery loops, though the skill involves no destructive or batch operations that would require them.

4 / 5

Progressive Disclosure

The body is well-sectioned with a clearly signaled, one-level-deep Reference Materials section and a Next Best Skill routing block. However, the bundle contains no scripts/, references/, or assets/ directories, so the referenced connectors, CONNECTORS.md, and ../../../references/*.md files cannot be found in the skill, leaving the content split partially unverifiable — minor organization gaps consistent with anchor 4 rather than a fully verified anchor-5 split.

4 / 5

Total

15

/

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.

A strong description: concrete outputs, explicit quoted triggers for both what and when, and explicit out-of-scope routing to neighboring skills. The only weakness is modest synonym coverage of natural trigger phrasings.

DimensionReasoningScore

Specificity

The description 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 (labeled Estimated)", and "an embargo window definition (lift moment + timezone) submitted to the launch registry" — giving comprehensive coverage of the skill's outputs. Not anchor 4: there are no meaningful gaps in the action list.

5 / 5

Completeness

It explicitly answers both questions: an explicit "Use when..." clause with concrete quoted trigger phrases, and a clear what (comparison table, format call, buffer padding, embargo definition submitted to the registry). This matches anchor 5's pattern of concrete what + explicit when.

5 / 5

Trigger Term Quality

It quotes natural phrases users would say — "pick a launch date", "plan the launch window", "set the embargo and lift time" — and adds Chinese synonyms (发布择时/发布窗口), but misses common variations like "when should we launch", "release date", or "launch timing". Matches anchor 4 (good coverage, a few natural terms missing) rather than anchor 5's full synonym set.

4 / 5

Distinctiveness Conflict Risk

A clear timing niche with explicit negative boundaries — "Not for judging the cultural moment itself — use trend-spotter; not for launch-day execution — use launch-day-conductor" — routing adjacent intents away, so conflict risk is minimal.

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

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.