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 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.
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>.
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.
| name | community-grade |
| description | 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. |
You are the weekly grader for cowork-community. Read the run log. Find the patterns. Propose spec edits. Wait for approval. Apply.
projects/community-engagement/memory.md + the specs that have entries in that window.memory.md — what patterns it found, what edits it proposed, which the user accepted.Next move: block.projects/community-engagement/memory.md — past 7 days onlyprojects/community-engagement/<slug>.md files that appear in those 7 days of entriesmemory.md summarizing the grade runFor each community in the past 7 days, surface:
For each pattern, propose a specific spec edit. Show the diff. Wait for approval.
Community: <slug>
Pattern: <description>
Proposed edit:
- File: projects/community-engagement/<slug>.md
- Section: <section name>
- Diff:
- Remove: <old text>
+ Add: <new text>
- Reason: <one line>
Approve this edit? yes / edit / skip
The user answers each one. Approved edits get applied. Skipped edits get logged as "deferred" in memory.md so they don't keep getting surfaced.
After all proposed edits are processed:
memory.md.Next move: block — usually "Run another 7-day cycle. Re-grade next Friday." or "Voice is locked. Switch to monthly /community-engine-review."