CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

multi-platform-launch

Multi-platform product launches: Product Hunt, Hacker News, BetaList, AppSumo, waitlist, launch day, multi-channel rollout — pre-launch through post-launch.

Quality

69%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/multi-platform-launch/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 content is an unusually specific and actionable launch playbook with concrete timings, benchmarks, and checklists throughout, and a well-sequenced multi-week workflow. Its main weaknesses are its monolithic single-file structure that should be split into reference files, promotional padding, and the absence of mid-launch error-recovery feedback loops.

Suggestions

Split the platform deep dives (Product Hunt, Hacker News, AppSumo, waitlist playbook) into separate reference files under references/, keeping SKILL.md as a concise overview with clearly signaled one-level-deep links.

Remove or trim the promotional sections ('Synter MCP (paid media companion)' and the 'About this skill' footer) which consume tokens without aiding execution.

Add mid-launch contingency feedback loops, e.g., 'If PH rank falls below #10 by 10:00 AM PT, post a maker-comment update and activate the reserve supporter list.'

DimensionReasoningScore

Conciseness

The body is dense with specific operational data (timings, benchmarks, pricing) with little explanation of concepts Claude already knows, but contains clear padding: the 'Synter MCP (paid media companion)' section and 'About this skill' footer are promotional material unrelated to the task, and asides like 'Expect brutally honest feedback' add little, fitting anchor 3.

3 / 5

Actionability

Highly concrete and executable for an instruction-only skill: hour-by-hour Day 0 schedule ('12:01 AM PT: Product Hunt goes live'), specific title examples, deal structures ('$49-$79 one-time for Tier 1'), referral tiers, and intake questions. A few directives remain high-level ('Brief your launch day support crew with specific instructions'), fitting anchor 4 rather than 5.

4 / 5

Workflow Clarity

The Launch Sequence Framework provides a clear week-by-week sequence from Week -4 through Week +4 with a Day 0 hour-by-hour schedule, input gating before starting, phase checklists, and a 7-Day Post-Launch Review. However, there are no mid-execution error-recovery feedback loops (e.g., what to do if PH rank is falling at midday), fitting anchor 4 rather than 5.

4 / 5

Progressive Disclosure

A single monolithic ~615-line SKILL.md with no references/ or other bundle files; the platform deep dives (Product Hunt, Hacker News, AppSumo, waitlist) clearly belong in separate reference files. Internal headers make it navigable (above anchor 2), but content that should be separate is fully inline, matching anchor 3.

3 / 5

Total

14

/

20

Passed

Description

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

The description effectively names a distinctive niche with concrete platform triggers and natural keywords, but reads as a topic enumeration rather than a capability statement. It lacks both action verbs describing what the skill does and an explicit 'Use when...' trigger clause, which caps completeness.

Suggestions

Add an explicit trigger clause, e.g., 'Use when planning a product launch on Product Hunt, Hacker News, or other platforms, or when the user mentions launching, waitlists, or launch day.'

State the skill's actions with verbs, e.g., 'Plan, sequence, and execute multi-platform product launches across Product Hunt, Hacker News, BetaList, and AppSumo.'

Include natural synonyms such as 'Show HN', 'PH', and 'go-to-market' to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ('Multi-platform product launches') with concrete platform scope ('Product Hunt, Hacker News, BetaList, AppSumo') and phases ('pre-launch through post-launch'), but contains no verbs describing what the skill actually does (e.g., plan, sequence, execute), matching anchor 3 rather than 4 which expects several specific actions.

3 / 5

Completeness

The 'what' is present as a domain statement, but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the judging guidelines; 'pre-launch through post-launch' is temporal scope, not a trigger condition.

3 / 5

Trigger Term Quality

Includes natural phrases users would say when needing this skill ('product launch', 'Product Hunt', 'Hacker News', 'waitlist', 'launch day'), but misses common synonyms and variations like 'Show HN', 'PH', or 'go-to-market', fitting anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

Platform names ('Product Hunt, Hacker News, BetaList, AppSumo') stake out a clear niche with distinct triggers and minimal overlap risk, but broad terms like 'launch day' and 'multi-channel rollout' without a when-clause leave minor conflict risk with general marketing/GTM skills, fitting anchor 4 rather than 5.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (620 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

Synter-Media-AI/free-skills

Path

skills/multi-platform-launch/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.