CtrlK
BlogDocsLog inGet started
Tessl Logo

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. 发布择时/发布窗口/竞品日历/禁运期窗口/审核缓冲

64

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./launch/research/launch-window-planner/SKILL.md
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.

A well-structured, actionable instruction skill with a clear sequenced workflow and explicit completion criteria. Its main weakness is repeated guardrail language (registry-write prohibitions restated many times) that inflates token cost without adding new information.

Suggestions

State the 'never writes memory/launch-registry directly — candidates only' rule once in the Skill Contract and reference it rather than restating it in the intro, Scope guard, Instructions step 9, and Save Results.

Consolidate the duplicate scope-boundary content between the opening paragraph and the dedicated 'Scope guard' section into a single location.

Add an explicit validate-and-retry note for the case where a connector returns conflicting competitor dates, to strengthen the feedback loop for the riskiest data step.

DimensionReasoningScore

Conciseness

The body is information-dense and avoids explaining concepts Claude already knows, but the registry-write prohibition ('never writes memory/launch-registry directly') and the 'proposal not record' framing are repeated ~5 times across the intro, Scope guard, Skill Contract, Instructions, and Save Results sections, which could be tightened.

3 / 5

Actionability

Concrete, executable guidance throughout — named connectors (producthunt.py, hn.py, gdelt.py), specific memory paths, a 2-4 window / 3-column comparison table spec, and a submit-via-registry-events.py step — with only minor gaps (Quick Start uses [product]/[quarter] placeholders).

4 / 5

Workflow Clarity

A clearly sequenced 9-step process is paired with an explicit 'Done when' completion checklist serving as a validation gate; the skill only proposes writes (delegating formalization to launch-registry), so the destructive/batch cap does not apply, though no validate→fix→retry loop is spelled out.

4 / 5

Progressive Disclosure

Well-organized sections (Quick Start, Skill Contract, Data Sources, Instructions, Save Results, Reference Materials, Next Best Skill) with one-level-deep, clearly signaled references; no bundle files exist in this skill, and inline cross-references throughout make navigation slightly busy rather than a clean 5.

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 that clearly states both what the skill produces and when to invoke it, with concrete trigger phrases and explicit boundary guidance against adjacent skills. Trigger-term coverage is good but could add a few more natural synonyms.

Suggestions

Add one or two more natural synonyms such as 'schedule the launch' or 'when should we launch' to broaden trigger-term coverage.

The trailing CJK keyword string duplicates information already conveyed in English; consider trimming it to reduce token overhead.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'produces a candidate-window comparison table (conflict / tailwind / risk per window)', 'launch-week vs rolling-release format call', 'store-review buffer padding', 'embargo window definition (lift moment + timezone)' — with comprehensive coverage of the skill's outputs.

5 / 5

Completeness

Explicitly answers both what (comparison table, format call, buffer padding, embargo definition) and when ('Use when the user asks to...') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Three natural trigger phrases users would say ('pick a launch date', 'plan the launch window', 'set the embargo and lift time') give good coverage, but common synonyms like 'schedule the launch' or 'when should we launch' are missing, so it is not fully comprehensive.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (launch timing) and explicitly distinguishes itself from trend-spotter and launch-day-conductor via 'Not for...' clauses, minimizing conflict 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.

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