Individual skill
participation-warmup-planner
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. 社区预热/先给后取/账号养成/毕业标准
social/explore/participation-warmup-planner/SKILL.md
Source commit 8be02f1f0b18253bd5f2b85f858278f042637b9a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 3,127
- Repository last updated
- Nov 10, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- geo Repository topic
- seo Repository topic
- agent-skills Repository topic
- content-optimization Repository topic
- generative-engine-optimization Repository topic
- marketing Repository topic
- influencer-marketing Repository topic
- paid-advertising Repository topic
- roas Repository topic
- email-marketing Repository topic
- design Derived category
Declared tags are partial or unavailable.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 14,598 bytes
Read excerpt
# 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](../../../protocol/channel-registry/SKILL.md) 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](../../../references/echo-benchmark.md). It picks up the phased-entry handoff from [audience-mapper](../../../influencer/scout/audience-mapper/SKILL.md) niche mode and builds the account history [community-launch-runner](../../../launch/mobilize/community-launch-runner/SKILL.md) 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](../../../launch/mobilize/community-launch-runner/SKILL.md)), decide which channels to run ([channel-portfolio-planner](../channel-portfolio-planner/SKILL.md)), 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](../../../protocol/channel-registry/SKILL.md) is the sole writer), or score the ECHO profile result / judge the E dimension ([social-quality-auditor](../../host/social-quality-auditor/SKILL.md) 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.
```
```
Our 小红书 account is 3 weeks old with 12 posts (screenshot attached). Build the warming → active graduation checklist and tell me what is still missing.