| name | participation-warmup-planner |
| slug | aaron-participation-warmup-planner |
| displayName | Participation Warmup Planner · 参与预热计划 |
| summary | 社区参与预热/先给后取台账/规则摘要/warming毕业标准 |
| description | Use when the user asks to "plan the participation ramp before we promote", "how much account history or karma do we need in this community", or "design entry incentives and member lifecycle for our own Discord"; produces the per-community pre-promotion warming plan — account-history/tenure expectations (Estimated, named sources), a give-before-ask ledger spec, a per-community etiquette + rule digest with last-verified dates, and the warming → active graduation criteria that channel-registry requires as state-transition evidence — plus the owned-community variant (entry paths + member lifecycle for your own Discord/Slack/forum/企业微信私域). Not for launch-day submissions or T-0 threads — use community-launch-runner. 社区预热/先给后取/账号养成/毕业标准 |
| 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 channels are chosen but not yet promoted in: designing the authentic-participation ramp per community (account-history expectations, give-before-ask ledger spec, etiquette and rule digest with last-verified dates), setting the warming → active graduation criteria the channel registry records as transition evidence, or designing entry incentives and member lifecycle for an owned Discord/Slack/forum/企业微信 space. Picks up the phased-entry handoff from audience-mapper niche mode and builds the account standing community-launch-runner presumes at T-0. Not the launch-day submission plan itself. |
| argument-hint | <community list or owned space> [target promotion window] [existing account history] |
| metadata | {"author":"aaron-he-zhu","version":"20.1.0","discipline":"social","phase":"explore","geo-relevance":"low","hermes":{"tags":["marketing","social","explore"],"category":"social"},"openclaw":{"emoji":"📣","homepage":"https://github.com/aaron-he-zhu/aaron-marketing-skills"}} |
Participation Warmup Planner
Designs the pre-promotion ramp that makes a brand a member before it is a marketer — per-community account-history expectations, a give-before-ask ledger spec, an etiquette + rule digest with last-verified dates, and the warming → active graduation criteria that channel-registry requires as state-transition evidence. It is the fourth move of the ECHO Explore phase and feeds four ECHO E sub-items directly: participation-before-promotion (E2), give:ask ledger maintained (E3), owned-space entry and member-lifecycle health (E6), and the cross-community rule-conflict check (E10) — see echo-benchmark.md. It picks up the phased-entry handoff from audience-mapper niche mode and builds the account history community-launch-runner presumes exists at T-0.
Scope guard: this skill produces the warming plan document only. It does not run launch-day submissions or T-0 threads (that is community-launch-runner), decide which channels to run (channel-portfolio-planner), write memory/channels/ records (graduation criteria and cadence facts go to memory/events/channels.ndjson via an authorized operation: propose request to registry-events.py; channel-registry is the sole writer), or score the ECHO profile result / judge the E dimension (social-quality-auditor does that against the registry record). Nothing in the plan is automated participation: every give, reply, and post is executed by a human — karma farming, engagement pods, and scripted replies trip the ECHO H1 veto at the gate and are never planned here.
Quick Start
Plan the participation warmup for r/selfhosted, Hacker News, and our niche Discourse forum — we want to promote the beta in 8 weeks.
