What does this skill do, and when should you use it?
Community Launch Runner is the launch-mobilization skill for the Aaron Marketing Skills collection. It prepares platform-specific packages for Product Hunt, Show HN, subreddits, directories, and regional communities, then checks the plan against current rules and platform red lines. It uses WebFetch to verify official submission requirements at launch time and can route T-0 status proposals to the launch registry. It fits teams that need structured community-launch execution without automated vote manipulation or direct posting.
Reads launch stage, dates, embargo commitments, audience, region, target platforms, user-provided messaging, and channel assets; uses WebFetch to verify current platform rules and field specifications; produces a Product Hunt tagline, gallery list, first-comment skeleton, and reply ownership plan; creates a factual Show HN title and text; drafts subreddit posts with a self-promotion rules table; plans tiered directory waves and regional channel selection; checks for vote solicitation, voting rings, coordinated engagement, incentives, retry deletion, and embargo violations; and submits dated T-0 status lines as authorized proposals through registry-events.py.
- A product team needs a Product Hunt package with a tagline, gallery plan, maker-comment skeleton, and launch-day reply ownership.
- A developer is preparing a Show HN submission and needs a factual title and explanation of what was built and how it works.
- A marketer is planning subreddit distribution and needs each community's self-promotion, flair, format, and account-history requirements checked.
- A global or China-focused launch needs regional channel selection based on audience fit, including Jike, V2EX, sspai, or Juejin where appropriate.
- A launch owner wants a pre-T-0 red-line review to catch vote solicitation or other platform-policy problems.
How do you install this skill?
- This skill may lead to real community submissions; confirm each platform action, account eligibility, rule set, and timing. A proposal or plan must not be treated as authorization to publish externally.
- Product Hunt, Hacker News, Reddit, directory, and Chinese-community rules require live verification. If WebFetch or a platform is unavailable, stop and report the limitation rather than guessing.
- The skill declares version 18.0.0 while SECURITY.md lists 17.x as the supported line; confirm support and maintenance status before adoption.
- No skill-specific executed outputs, failure examples, or independent test evidence were supplied; human review remains necessary.
- Shell / CLI
- Network access
- Local filesystem
Python standard-library connector scripts
For Claude Code, run /plugin marketplace add aaron-he-zhu/aaron-marketing-skills, then /plugin install aaron-marketing@aaron. On Agent Skills-compatible hosts, run npx skills add aaron-he-zhu/aaron-marketing-skills. Alternatively, run git clone https://github.com/aaron-he-zhu/aaron-marketing-skills; the skill is at launch/mobilize/community-launch-runner/SKILL.md.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/aaron-he-zhu/aaron-marketing-skills.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/launch/mobilize/community-launch-runner" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
With the skill installed, try: Prepare a Product Hunt + Show HN submission package for [product]. Launch date: [date]. Audience: [who]. Another supported prompt is: Build the community launch plan for [product] — subreddits, directories, and Chinese channels. Region: [global / CN / both]. Supply the product, launch date, audience, region, target platforms, and recorded launch facts before execution.
What are this skill's strengths and limitations?
- Covers Product Hunt, Show HN, subreddit, directory, and regional community submissions.
- Produces concrete deliverables: platform fields, drafts, directory waves, rules tables, and T-0 status lines.
- Enforces explicit safeguards against vote solicitation, voting rings, coordinated engagement, and improper review incentives.
- Requires current-rule verification through official platform documentation and labels evidence types such as User-provided, Measured, Platform-reported, and Estimated.
- Distributed under Apache-2.0 and installable as part of the shared marketing-skills collection.
- It does not publish content, calculate the RAMP profile result, issue the go/no-go decision, or perform the T+30 telemetry read.
- It depends on launch facts, messaging, channel assets, audience, and regional inputs; missing accepted launch state becomes NEEDS_INPUT.
- Platform rules and field limits must be rechecked at submission time rather than taken from cached values.
- The supplied source does not document an independent test suite or successful live submissions for each supported platform.
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| Community Launch Runner this page | 56 · Use with care | ★ 3k | 12d ago | Apache-2.0 |
| RAMP Launch Readiness Auditor | 61 · Recommended | ★ 3k | 12d ago | Apache-2.0 |
| Launch Pricing & Packaging Planner | 61 · Recommended | ★ 3k | 12d ago | Apache-2.0 |
| Launch Retro Analyzer | 59 · Recommended | ★ 3k | 12d ago | Apache-2.0 |
| Launch Feedback Synthesizer | 56 · Use with care | ★ 3k | 12d ago | Apache-2.0 |
How did FollowSkills review this skill?
The files show least-privilege intent through WebFetch-only tooling, untrusted-content handling, anti-vote-manipulation rules, proposal-based registry writes, and confirmation before saving memory. However, the workflow still concerns community submissions, external platform data, and registry proposals without explicit per-action confirmation, rollback coverage, or a complete sensitive-data boundary, so 7 points are deducted.
Triggering, scope guards, Unknown/NEEDS_INPUT behavior, handoffs, and termination rules are reasonably consistent. Static review cannot reproduce the key registry, connector, script, and referenced-file paths supplied by the skill, and there is no committed skill-specific evidence of abnormal-input handling or diagnosable platform failures; the static ceiling therefore limits this to 8.
The audience, inputs, outputs, non-fit scenarios, channel selection logic, and Chinese-community coverage are clearly described. Nonetheless, core behavior depends on live platform rules, WebFetch, and potentially hard-to-reach overseas communities; geo-relevance is explicitly low and mainland-China reachability is not demonstrated, so 4 points are deducted.
The skill has structured frontmatter, Quick Starts, a contract, data sources, numbered instructions, save rules, references, versioning, and Apache-2.0 licensing. Maintenance ownership, changelog/update responsibility, and support path are not sufficiently specific; SECURITY.md lists 17.x as supported while the skill is 18.0.0, suggesting governance drift, and publisher identity is unverified, so 6 points are deducted.
The expected outputs are concrete and directly relevant: Product Hunt, Show HN, subreddit, directory-wave, regional-channel packages, red-line checks, status proposals, and handoff. However, completion depends on user-supplied launch facts and assets, live platform rules, and external protocol files; no verified skill-specific execution output is present, so static calibration limits this to 6.
Official-rule verification, verify-current labels, source naming, and separation of Measured, platform-reported, and Estimated claims provide partial traceability. The supplied material contains no independently reproducible execution record or corroborated evidence covering the skill's key paths, so this remains at 4 under the static ceiling.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →