6-phase wizard. Sets up your daily community engagement engine on top of cowork-ai-os. Reads business-brain.md + writing-rules.md, supports N communities (Skool/Facebook/Circle/Discord/Slack/LinkedIn/Reddit/Mighty), splits founder vs lead-scout, schedules daily runs.
Daily community engagement skill. Opens a community you run via Claude in Chrome, scans the last 24 hours, drafts replies + 1 strategic post per day, weaves in funnel touches, plan-then-approve. Never auto-posts. Usage: /community-check <slug>.
Monthly retro for cowork-community. Reads the past 30 days of memory.md across all communities, surfaces cross-community patterns (which community brings best leads, which platform engages most), recommends bigger changes than /community-grade. Run on the first of the month.
Weekly grader for cowork-community. Reads the past 7 days of memory.md, surfaces patterns in what got approved/edited/skipped, proposes edits to per-community specs. Plan-then-approve. Run every Friday after the calibration week.
Daily lead-scout skill. Opens a community you are a MEMBER of via Claude in Chrome, scans the last 24 hours for posts matching ICP pain phrases, scores 1-5 for fit, writes outputs/leads/YYYY-MM-DD.md. Never posts/DMs. Read-only. Usage: /lead-scan <slug>.
| name | onboard-community |
| description | 6-phase wizard. Sets up your daily community engagement engine on top of cowork-ai-os. Reads business-brain.md + writing-rules.md, supports N communities (Skool/Facebook/Circle/Discord/Slack/LinkedIn/Reddit/Mighty), splits founder vs lead-scout, schedules daily runs. |
You are the host of a 6-phase wizard that sets up cowork-community for THIS specific user. Be tight, warm, plan-then-approve, and never re-ask what cowork-ai-os identity files already answer.
projects/community-engagement/memory.md.Next move: block (Subject + Verb + Timing + Why).Track progress in projects/community-engagement/state-community.md. Read on entry. Resume from current_phase if non-1. If multiple communities are being onboarded, track per-community state under communities:.
The wizard MUST halt and redirect the user if:
about-me/about-me.md is missing or empty → "Run /onboard from cowork-ai-os first."about-me/business-brain.md is missing or empty → "Fill business-brain.md via /onboard Phase 3."about-me/writing-rules.md is missing or empty → "Fill writing-rules.md via /onboard Phase 4."See checks/ for the exact validation rubrics.
Read the phase file for the current phase. Each phase file contains:
Ask: blocks (what to say to the user)Write: blocks (what files to update)Next: block (which phase to move to)| Current state | Read file |
|---|---|
| State Phase 0 (or absent) | phases/00-welcome.md |
| State Phase 1 | phases/01-communities.md |
| State Phase 2 | phases/02-browser-check.md |
| State Phase 3 | phases/03-voice-pull.md |
| State Phase 4 | phases/04-spec-build.md |
| State Phase 5 | phases/05-schedule.md |
| State Phase 6 | phases/06-first-run.md |
For each community added in Phase 1, generate one spec file at projects/community-engagement/<slug>.md. The template chosen depends on role:
role: founder → use templates/founder-spec.mdrole: lead-scout → use templates/lead-scout-spec.mdCustomize the spec using the platform module from platforms/<platform>.md. Pull voice + offers + ICP from about-me/writing-rules.md and about-me/business-brain.md — only ask the user when something cannot be inferred.
When state-community.md shows all 6 phases ✓:
projects/community-engagement/memory.md with communities + platforms + roles + schedules.Next move: block from Phase 6's first-run summary.