The blank post box is the worst part of running a Skool community. You know you should post. You do not know what. So you post something generic, it gets two likes and no comments, and the next day the box is blank again.
The fix is not more inspiration. It is a shorter list of decisions. Almost every good community post is doing one of five jobs, and almost every idea worth posting comes from something you already observed a member do.
How do I decide what a post is actually for?
Every good Skool post starts with a job rather than a topic, so before you write a word, pick which job the post is doing. This single step kills most blank-page paralysis, because "write something valuable" is an impossible brief and "welcome the six people who joined this week by name" is a five-minute task.
The five jobs:
- Welcome. New members are never more willing to reply than in their first few days. A welcome post that names people and asks them one easy question converts more lurkers than anything else you will publish.
- Recognise. Call out the people who commented, answered someone else's question, or hit a milestone. Recognition is the cheapest engagement mechanic there is and it compounds — recognised members post more.
- Teach one narrow thing. Not a course. One idea, one page, one thing someone can do this afternoon. Narrow beats comprehensive in a feed.
- Ask. A real question, not a rhetorical one. The test: could a member answer it in one sentence from their own experience? If they need to go and think for an hour, they will not reply.
- Mark the moment. Milestones, member counts, a big win someone had, the end of a cohort. These are the posts people screenshot.
If you rotate those five, you have a content calendar without ever calling it that.
Where do I get post ideas my members actually care about?
The post ideas that work come directly from what your own members did, because generic post ideas produce generic engagement.
Mine your own comment threads
The comments under your existing posts are the highest-signal idea source you own. Anywhere a member asked a follow-up question, you have a post. Anywhere three people asked the same thing, you have a post you should have written months ago.
A cheap habit: once a week, read only the comments from the past seven days and write down every question that was asked. That list is your next month.
Look at what your members read elsewhere
Your members are on Skool for more than your room. They are in other communities, reading other people's posts, and what pulls them there tells you what they care about right now. This is invisible from inside your own admin area — you can only see your own community from there — but it is the single richest source of topic signal available to a community owner.
Skoolgrades reads this through Attention Pull, which ranks external Skool rooms and posts by the share of your members' attention they capture rather than raw size. That distinction matters: a room that owns a slice of forty of your members is far more informative than one huge room that one member happens to be in. The cross-community view is the same data from the member side.
Be honest about the limit here: cross-community counts deliberately undercount. When you see "nine of your members are active in that room", treat it as a floor, not a total.
Watch the rooms, not just the members
Watchlist does the room-side version: you pick external Skool rooms where your people hang out, and it surfaces fresh and trending threads there. Half the value is finding somewhere to genuinely add value with a comment. The other half is seeing which framings of a topic are landing, which you can then write your own version of, in your own voice, for your own room.
One caveat worth stating plainly: these alerts are not real-time. Median lag from a post going up to it appearing in your list is measured in hours. That is fine for weekly idea sourcing and useless for being first to a thread.
How do I turn a topic into a post that gets comments?
A topic becomes a post that gets comments through structure, not inspiration, because having a topic is not the same as having a post. The gap between "members care about pricing" and a post that gets twenty comments is craft, and craft is mostly structure.
A structure that reliably works in a Skool feed:
- One-line hook. The first line is all most people see. Make it a claim or a question, not a preamble.
- Three to five bullets. Skimmable. Each one a complete thought.
- One question at the end. Specific, answerable in a sentence, and about them rather than about you.
- No call to action. The post is not a funnel. Asking people to book a call at the bottom of a community post is the fastest way to teach them to scroll past your posts.
The @mention move
Naming people in a post is the highest-leverage thing you can do and the most tedious. A shoutout that names the eight people who commented this week will outperform the same post with no names by a wide margin, because eight people now have a personal reason to open it.
Skoolgrades' Compose exists mostly for this. It has eight recipes — welcome, leaderboard shoutout, recognise commenters, milestone, fun, repost, clone a post that is working elsewhere, and freeform — and it hands you one-click copyable @mention tags for the right people, so the tedious part is the part that goes away.
How do I get more than one post out of a single idea?
One good idea should produce several posts, and most owners underuse theirs. You write the best thing you have written all quarter, it gets buried by the feed in three days, and that is that.
The Content Flywheel is built for exactly this problem: take one idea and turn it into a hero asset — a lesson, a podcast script, or a 1,500 to 3,000 word post — plus shorts, Skool posts, LinkedIn versions and a newsletter derivative. One decision, many artefacts. If repurposing is where you lose leverage, that is the fix.
And when you genuinely do not know which of your ideas is worth the effort, Content Gems ranks original post ideas across a judged external network and your own corpus, with a "why this?" tray explaining the reasoning and an audience list showing which of your members the idea is actually for. The audience list is the useful half — an idea that only speaks to three people is a DM, not a post.
How do I tell whether a post actually worked?
A Skool post worked if people replied to it, so judge it on comments rather than likes. Skoolgrades counts engagement as comments plus polls, not likes, and that is a deliberate choice: a like costs nothing and predicts nothing. A comment is a person choosing to spend thirty seconds in your room.
Three checks, a few days after posting:
| Check | What it tells you |
|---|---|
| Comments from people who rarely comment | The post reached past your regulars |
| Replies to each other, not just to you | The post created a conversation rather than an audience |
| Comment count against your own recent posts | Whether the format is working, independent of your community's size |
That last one is why comparing yourself to someone else's numbers is a waste of energy. Your baseline is your own previous posts. If you want a broader read, engagement rate is a more honest measure than raw counts.
So what should I post in my Skool community?
Post one of five jobs — welcome, recognise, teach one narrow thing, ask, or mark a moment — and pick the job before the topic. Take ideas from your comment threads and from what your members read elsewhere, not from a generic list. Write a hook, some bullets, and one answerable question. Name people. Then reuse the idea rather than letting it die in the feed.
Do that consistently for a month and the blank box stops being frightening, because you will have a backlog instead of a void.