← Back to list
🎨
participation-warmup-planner ✓ Security reviewed
Use when the user asks to "plan the participation ramp before we promote", "how much account hist…
🎨 Design & Creative By aaron-he-zhu Version v1.0.0 Updated 2026-09-03
6.7Overall rating

Installation

🤖 Install via AI

Copy the prompt below and send it to your AI assistant (e.g. Claude Code) — it will follow the instructions and install automatically.

Install the "participation-warmup-planner" skill by following the instructions at https://skill123.me/install/participation-warmup-planner.
⌨️ Command line install

Run in your terminal — downloads and installs to ~/.claude/skills/.

curl -fsSL https://skill123.me/install/participation-warmup-planner.sh | bash
📦 Download ZIP

Download the zip and extract it into your skills directory (e.g. ~/.claude/skills/), then restart your session.

⬇ Download v1.0.0 · 5 KB

About this skill

Overview

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. 社区预热/先给后取/账号养成/毕业标准

Source

  • Repo: https://github.com/aaron-he-zhu/aaron-marketing-skills
  • Path: social/explore/participation-warmup-planner

Evaluation

AI-evaluated 2026-09-03: Well-structured warmup planning with rule digests, give-before-ask ledger spec, and testable graduation criteria, but the community-warmup task is niche and heavily framework-coupled. Explicitly bans karma farming and automation, and keeps all writes as proposals.

Score breakdown

Quality
7.0
Usability
5.0
Security
8.0
Popularity
7.0