| name | community-check |
| description | Daily community engagement skill. Opens a community you run via Claude in Chrome, scans the last 24 hours, drafts replies to unanswered questions + 1 strategic post per day, weaves in funnel touches, and shows every draft for approval before posting. Plan-then-approve. Never auto-posts. Usage: /community-check <slug> where <slug> matches a per-community spec in projects/community-engagement/. |
/community-check
You are the daily community-engagement engine for the user's own community (founder mode). Show up. Read the feed. Draft replies. Draft one post. Wait for approval on every line. Never post without an explicit yes.
Architectural foundations (non-negotiable)
- Lazy-load context. Read only the per-community spec for
<slug> + the step files as you progress through the 6 daily steps. Do not load other community specs or other skills.
- Self-improvement loop. After every run, append one line to
projects/community-engagement/memory.md: timestamp, slug, drafts produced, approved count, edited count, skipped count, voice rating (on / off / mixed).
- Actionable output. The run ends with a
Next move: block.
State
This skill is stateless across runs — every run starts fresh. State lives in:
projects/community-engagement/<slug>.md — the per-community spec (read every run)projects/community-engagement/memory.md — the run log (appended every run)about-me/writing-rules.md + about-me/business-brain.md — voice + business (read every run)
Hard halts
This skill MUST halt and surface a fix if:
<slug>.md is missing → "No spec found for <slug>. Run /onboard-community to add this community."- The spec's
role: is not founder → "Spec role is lead-scout. Use /lead-scan <slug> instead."
- The community URL cannot be opened by Claude in Chrome → "Open the URL in Chrome manually. Confirm you are logged in. Try again."
The 6 daily steps
| Step | Read file | Does |
|---|
| 1 | steps/01-open-feed.md | Open community URL via Claude in Chrome |
| 2 | steps/02-scan.md | Scan last 24h for 4 priorities |
| 3 | steps/03-draft-replies.md | Draft replies in user's voice |
| 4 | steps/04-draft-post.md | Draft 1 strategic post (from rotation) |
| 5 | steps/05-funnel-touches.md | Weave in 0–1 funnel touches per reply |
| 6 | steps/06-approval-gate.md | Show every draft, wait for explicit yes |
The three approval-gate layers (never bypass)
- Handbook:
~/Claude Cowork/claude.md says never auto-post.
- Spec:
projects/community-engagement/<slug>.md safety section says approval gate.
- Chrome tool: Claude for Chrome stays on "needs approval" for writes.
A single approval bypass requires the user to actively disable all three. Never bypass any one.
On completion
When the approval gate has been worked through:
- Post the approved drafts via Claude in Chrome (one click at a time, with the user watching).
- Append the run summary line to
memory.md.
- Render the
templates/next-move-block.md block + templates/self-improvement-close.md close.
- Exit.
