community-launch-runner

name	community-launch-runner
slug	aaron-community-launch-runner
displayName	Community Launch Runner · 社区发布执行
summary	社区发布/PH-HN提交包/目录波次/平台红线
description	Use when the user asks to "launch on Product Hunt / Hacker News", "prepare community or directory launch submissions", or "plan the launch submission waves"; produces per-platform submission packages — a Product Hunt tagline / gallery / first-comment skeleton, a factual Show HN title and text, per-subreddit posts with a self-promotion rules table, tiered directory waves, and a regional channel matrix including Chinese communities — plus a platform red-line check (never solicit votes or organize voting rings) and T-0 submission-status lines for the launch registry. Not for paid amplification — use content-amplifier; not for creator channels — use campaign-planner; not for launch telemetry readouts — use launch-monitor; not for ongoing community presence or pre-launch karma-building outside the launch window — use participation-warmup-planner. 社区发布/PH提交包/Show HN/目录波次/平台红线/中文渠道
version	20.1.0
license	Apache-2.0
compatibility	Claude Code and compatible agent-skill hosts
homepage	https://github.com/aaron-he-zhu/aaron-marketing-skills
when_to_use	Use when executing the community and directory lane of a product launch: preparing a Product Hunt submission package, a Show HN post, subreddit posts under each community self-promotion rule, or tiered directory submission waves. Also when selecting regional channels by audience fit (including Chinese communities such as Jike, V2EX, sspai, Juejin) or checking a submission plan against platform red lines like vote solicitation. The execution layer for community channels — the go/no-go gate is launch-readiness-auditor, the telemetry read is launch-monitor.
argument-hint	<product / launch slug> [platforms] [region] [launch date]
allowed-tools	WebFetch
metadata	{"author":"aaron-he-zhu","version":"20.1.0","discipline":"launch","phase":"mobilize","geo-relevance":"low","hermes":{"tags":["marketing","launch","mobilize"],"category":"launch"},"openclaw":{"emoji":"🚀","homepage":"https://github.com/aaron-he-zhu/aaron-marketing-skills"}}

Community Launch Runner

Executes the community and directory lane of a launch — per-platform submission packages (Product Hunt, Show HN, subreddits, tiered directories, regional channels including Chinese communities) built under each platform's published rules. In the RAMP loop this is a Mobilize-phase execution skill: it feeds the M (Momentum) sub-items channel mix fits tier & use-case and platform-rule compliance per channel, and it is the execution surface the M1 veto (platform manipulation / policy) judges — launch-readiness-auditor scores that; this skill never computes the RAMP profile result. It works one lever — community submission execution — and hands off.

Scope guard: this skill prepares community/directory submissions only. It does not run paid amplification, creator campaigns, media relations, the launch-day runbook, telemetry, or canonical launch state. T-0 observations become authorized idempotent launch proposals through registry-events.py; launch-registry resolves them. Ongoing community presence/warmup belongs to the social discipline.

Quick Start

Prepare a Product Hunt + Show HN submission package for [product]. Launch date: [date]. Audience: [who].

Build the community launch plan for [product] — subreddits, directories, and Chinese channels. Region: [global / CN / both].

Check my submission drafts against each platform's rules before T-0 — here are the drafts and the channel list.

Skill Contract

Expected output: per-platform submission packages (Product Hunt tagline / gallery / first-comment skeleton, factual Show HN title + text, per-subreddit posts with a self-promotion rules table, tiered directory waves, regional-channel posts), a red-line check across the whole plan, T-0 submission-status lines routed to the registry proposal protocol, and the standard handoff summary.

• Reads: the launch dossier facts; the current frozen manifest version/hash and matching SHIP verdict; the message house and per-channel asset kit; target platforms, region, and audience; each platform's current official rules; and early launch-window telemetry.
• Writes: submission packages + a reusable summary to memory/launch/community-launch-runner/ (its WARM path, after permission); dated T-0 submission-status lines submitted as proposal events to memory/events/launches.ndjson via an authorized request to (the hot path — resolves each proposal individually in offset order; this skill never writes the dossier or calendar directly). It does not write HOT automatically.