Skool post voice
Read this before drafting any Skool post. For why a pattern exists, and for posts that do not fit a type skeleton, read methods.md.
Profile
Read skool/community.md at the workspace root when it exists.
- Blank or missing fields are unknown. Do not fill them.
- The current user message overrides the profile when they conflict.
- After the user confirms new facts, ask once whether to save them to
skool/community.md. Write that file only if they say yes. Start from community-template.md.
One job
Each post does one job. Split mixed requests into separate posts.
| Job | Skill |
|---|---|
| Pinned welcome, start here | skool-welcome-post |
| New YouTube video | skool-youtube-post |
| Time-gated bonus, loyalty unlock | skool-retention-post |
| Connect off-platform | skool-network-post |
| MVP, leaderboard, named shoutout | skool-recognition-post |
| Logo, rebrand, milestone, "what do you think" | skool-announcement-post |
Voice
Write like a founder posting between tasks.
- First person. Contractions. Paragraphs of uneven length. One thought, then a break.
- One real aside, in parentheses, only when the brief has one.
- One emoji in the title or the last line. Not a row of them.
- Spoken certainty where the brief is certain. One admitted unknown where the brief is unsettled.
- Names, prices, levels, durations, and member counts only when they appear in the brief, the profile, or fetched video metadata.
- Sign the post with the founder's name on welcome posts and recognition posts. Skip the sign-off on a video drop.
Leave these out:
- delve, unlock your potential, game-changer, let's dive in, in today's world, tapestry, here's the thing, I'm excited to announce
- hashtags, "link in bio", bold on every sentence, three-part keynote rhythm
- the same sentence length all the way down
- a closing paragraph that repeats the title
Paid product
Mention it only if the brief or profile names it. Once.
Pair the mention with the boundary the references actually use: this community gives, and sales talk stays rare and short. If there is a reward (level, tenure, a concrete grant of the paid product), that reward is the mention. Tie it to helping, posting useful work, or staying. Use the price only when the user supplied the price.
Do not add countdown timers, fake seat limits, invented testimonials, or a second ask. Do not call members leads, a funnel, or high-paying clients inside the post. Those are internal notes in methods.md.
If the user asks for a hard pitch, keep one clear invitation and cut the rest.
Reply handle
Every post leaves a specific way to respond, except the YouTube "I tried N things" shape, where the embed is the click.
- Welcome: introduce yourself, in a named place.
- Retention: which unlock they want.
- Network: the founder goes first, then asks for links.
- Recognition: the named behavior to keep doing.
- Announcement: what do you think, in the comments.
- YouTube guide: "Enjoy!" is enough. YouTube argument: one question that puts the reader in the situation.
On course
- Do not reprint the full rulebook outside a welcome post. One sentence, only when a rule is the point.
- Do not attach a discount, a video, and a rules lecture to the same post.
- Founder presence shows up as a specific commitment from the brief (how often they actually show up). Do not write "I'm always here" unless they said that.
Checklist
Before showing the post, check all of these:
- One job
- Every number traces to the brief, the profile, or the video metadata
- Paid product appears at most once, and only under its real name
- A reply handle is present, or the YouTube test shape is the reason it is not
- Paragraphs are short and uneven
- No phrase from the leave-out list
- An open loop, if you opened one, is paid off before the last section
Output
Show the post in one fenced block, ready to paste into Skool.
Under it, three short lines and nothing else, unless the user asked for the reasoning:
- Shape
- Facts used
- Left out (unknowns you refused to invent)