launch-distribution

Plan and execute multi-channel distribution for product launches across X/Twitter, Reddit, LinkedIn, Hacker News, and other platforms. Use this skill whenever someone asks to create a distribution plan, figure out where to post a launch, build a press list, set up internal amplification, or coordinate multi-channel promotion. Also trigger for "where should we post this," "how do we get the word out," or any request about promoting or distributing a product announcement. Covers channel strategy (with deep playbooks for Twitter, Reddit, and LinkedIn), post-launch retro, and building a repeatable distribution engine.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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 launch-day workflow and retro feedback loop, but it is somewhat verbose and keeps all detail inline with no progressive disclosure to reference files. Tightening prose and splitting the deep channel playbooks into reference files would raise the weaker dimensions.

Suggestions

Trim editorial throat-clearing (e.g., 'Great messaging and assets are wasted without distribution' and 'The best distribution is a habit, not a heroic effort') to assume Claude's intelligence and improve conciseness.

Move the per-channel deep playbooks (X/Twitter, Reddit, LinkedIn) into reference files under references/ and link to them from SKILL.md so the body stays a lean overview, improving progressive disclosure.

Consider condensing the 'Distribution philosophy' and 'Building the distribution engine' sections into tighter bullet lists.

Dimension	Reasoning	Score
Conciseness	Mostly efficient platform-specific guidance, but includes editorial padding Claude does not need ('Great messaging and assets are wasted without distribution,' 'The best distribution is a habit, not a heroic effort') and could be tightened in places.	2 / 3
Actionability	Provides concrete, specific guidance throughout: 'Have 5-10 people... ready to retweet within the first hour,' 'Identify 2-4 subreddits,' 'Tuesday or Wednesday at 12 AM PST,' and a timed launch-day sequence — copy-ready strategic instructions.	3 / 3
Workflow Clarity	The 'Distribution sequence' section gives a clear timed checklist (early morning, mid-morning, late morning, throughout the day) and the post-launch retro serves as an explicit feedback loop for refining the next launch.	3 / 3
Progressive Disclosure	No bundle files exist in references/scripts/assets, and the ~150-line body keeps all channel playbooks inline rather than splitting them into one-level-deep reference files; section headers aid navigation but content that could be separate is not offloaded.	2 / 3
	Total	10 / 12 Passed

Description

100%

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, explicitly covering both capabilities and use conditions in third person with a clear 'Use when' clause. It is among the strongest examples in the rubric.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions and channels: 'create a distribution plan, figure out where to post a launch, build a press list, set up internal amplification, or coordinate multi-channel promotion' across named platforms (X/Twitter, Reddit, LinkedIn, Hacker News).	3 / 3
Completeness	Clearly answers what (plan/execute multi-channel distribution, channel strategy, retro, distribution engine) and when via an explicit 'Use this skill whenever...' clause plus an 'Also trigger for...' list.	3 / 3
Trigger Term Quality	Covers natural phrasings users would say: 'where should we post this,' 'how do we get the word out,' 'distribution plan,' 'press list,' and 'Product Hunt,' with good variation.	3 / 3
Distinctiveness Conflict Risk	Occupies a distinct distribution niche with triggers like 'where to post,' 'press list,' and 'internal amplification' that are unlikely to fire for the companion launch-* skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: amplitude/builder-skills
Commit: 22b0634

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