Menu

Individual skill

community-engagement-playbook

0upvotes

Builds the student community system for a paid course - platform choice by where students already are, an introduce-yourself onboarding ritual, a weekly cadence of office hours, wins threads, and accountability checks, a hard creator-time budget, and scheduled testimonial-harvest moments. Use when a course creator says "my students aren't finishing the course", "should I use Circle or Slack or Discord", "how do I keep my community active without it eating my week", or "how do I get testimonials from students". Do NOT use for running the testimonial conversation itself - use testimonial-capture-interview instead.

skills/community-engagement-playbook/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 11, 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)
24
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Community Engagement Playbook

A course community exists for exactly two outputs: completion and testimonials. Students who feel seen finish, finished students get results, and results become the proof that sells the next cohort. The costly mistake is treating community as a feature to bolt on - an empty Slack nobody posts in signals a dead course louder than no community at all, and an unbudgeted community quietly consumes the creator's production time until the next launch slips.

This skill runs after launch-email-sequence hands over the buyers, operates against the completion target set by course-outline-architect, and feeds its testimonial harvest back to course-sales-page's proof section. That loop - community to testimonials to sales page - is what makes the second launch outperform the first.

Worked example throughout: Dana, who just closed the "Notion OS for Consultants" launch ($297) with roughly 120 students from her 8,000-subscriber list, budgeting 5 hours a week for community.

## Operating procedure

### Step 1: Collect the inputs

1. Student count and where the audience already hangs out (check where they replied from during the launch; ask 5 buyers directly if unknown).
2. The course's quick-win moment and module milestones from course-outline-architect.
Back to top