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

75%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./launch-skills/skills/launch-distribution/SKILL.md

Quality

Content

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a comprehensive and well-structured distribution guide with genuinely useful tactical advice for product launches. Its main weaknesses are verbosity (motivational/philosophical content that doesn't add actionable value for Claude), lack of executable templates or concrete output formats, and missing validation steps in the workflow. The content reads more like a human-facing marketing playbook than a lean AI skill file.

Suggestions

Cut the philosophy section and 'building the distribution engine' section — these are motivational, not instructional. Fold any unique tactical points into the relevant channel sections.

Add concrete templates: a sample distribution checklist in markdown, a UTM parameter naming convention, and example post copy for each channel so Claude can generate platform-specific drafts.

Add validation checkpoints to the distribution sequence: e.g., 'Verify UTM links resolve correctly before posting,' 'Confirm HN submission isn't flagged after 30 minutes,' 'Check #amplify channel engagement at noon.'

Consider splitting per-channel playbooks (Twitter, Reddit, LinkedIn, HN) into separate referenced files to reduce the main skill's token footprint, keeping only a summary table in SKILL.md.

Dimension	Reasoning	Score
Conciseness	The skill is well-written but verbose for an AI skill file. It explains general marketing concepts Claude likely already knows (e.g., 'Great messaging and assets are wasted without distribution,' 'The best distribution is a habit, not a heroic effort'). Many sections could be tightened significantly — the philosophy section, cultural framing of #amplify, and 'building the distribution engine' section are motivational rather than instructional.	2 / 3
Actionability	The skill provides concrete tactical advice (timing windows, specific subreddit size ranges, 'Tuesday or Wednesday at 12 AM PST' for Product Hunt) but lacks truly executable artifacts — no templates, no UTM parameter examples, no sample posts, no checklist format Claude could directly output. Guidance is specific but descriptive rather than copy-paste ready.	2 / 3
Workflow Clarity	The 'Distribution sequence' section provides a clear time-sequenced workflow for launch day, which is good. However, there are no validation checkpoints — no step to verify posts went live, no checkpoint to confirm UTM tracking is working, no decision gates (e.g., 'if HN post gets flagged, do X'). The post-launch retro is listed but lacks a concrete template or checklist format.	2 / 3
Progressive Disclosure	The skill references several companion skills (launch-strategy, launch-tweet, launch-email, launch-blog-post, launch-video, launch-metrics) which is good structure, but none of these are provided in the bundle. The main file itself is quite long (~200+ lines) with substantial inline content that could be split into per-channel playbook files. The companion skills section at the end is well-organized but the references are unverifiable.	2 / 3
	Total	8 / 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.

This is a strong skill description that excels across all dimensions. It provides specific concrete actions, includes natural trigger phrases users would actually say, explicitly addresses both what the skill does and when to use it, and carves out a distinct niche around product launch distribution. The description uses appropriate third-person voice and avoids vague language or buzzwords.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'create a distribution plan', 'figure out where to post a launch', 'build a press list', 'set up internal amplification', 'coordinate multi-channel promotion', 'channel strategy', 'post-launch retro', and 'building a repeatable distribution engine'. These are concrete, actionable capabilities.	3 / 3
Completeness	Clearly answers both 'what' (plan and execute multi-channel distribution for product launches, channel strategy, press lists, internal amplification, post-launch retro) and 'when' with explicit triggers ('Use this skill whenever someone asks to...', 'Also trigger for...'). The 'when' clause is detailed and explicit.	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms users would say: 'where should we post this', 'how do we get the word out', 'promoting or distributing a product announcement', 'distribution plan', 'press list', 'multi-channel promotion'. Also names specific platforms (X/Twitter, Reddit, LinkedIn, Hacker News) which users would naturally mention.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche: product launch distribution across specific social media channels. The combination of product launches + multi-channel distribution + named platforms (Twitter, Reddit, LinkedIn, HN) makes it highly distinctive and unlikely to conflict with general marketing or social media skills.	3 / 3
	Total	12 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: amplitude/builder-skills
Commit: 221ffaa

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