Every "50 content ideas for your community" list has the same problem. The ideas are fine. They are just not your ideas, so they land in your room like a stranger's opinion, and your members can tell.
Ideas that work in a Skool community almost always come from something a member actually did or said. This article is about the six places that signal lives, in rough order of how much it costs you to check.
Where do I actually find Skool content ideas?
Skool content ideas come from six sources you already own: your own comment threads, the answers you keep repeating in DMs, what your members read elsewhere on Skool, your own posts that already worked, the framings landing in rooms near yours, and a ranked idea list when you are stuck.
1. Your own comment threads
This is the highest-signal, lowest-effort source you own, and almost nobody works it systematically.
Every follow-up question a member asked under one of your posts is a post you have not written. Every time two people asked roughly the same thing, you have a post you should have written months ago.
The habit takes fifteen minutes:
- Once a week, read only the comments from the last seven days. Skip the posts.
- Write down every question, verbatim, in the member's own words.
- Note which member asked it.
You now have a list of topics with proof of demand attached, phrased in the language your audience uses. Step three matters more than it looks — when you write the post, you can @mention the person who asked, and they will show up.
2. The thing you keep explaining in DMs
If you have said the same paragraph in four different DM threads this month, that is a post. It is the clearest possible demand signal: people asked you privately, one at a time, because they did not know it was a common question.
Turning it into a public post does two things. It stops you retyping it, and it tells the twenty people who were too shy to ask that they were not the only one.
Worth saying plainly here, because there is confusion about it: Skoolgrades does do DM messaging. You build a list, it drafts one message either verbatim to everyone or personalised per member, you review and approve every draft, and you send them from the extension panel one click at a time. Nothing auto-sends. But for idea sourcing, the useful bit is simply noticing which conversations you keep having.
3. What your members read elsewhere on Skool
Your members are not only in your room. They are in other Skool communities, and where they spend attention is a live map of what your audience cares about right now — drawn from exactly the people you serve rather than from a generic trends article.
You cannot see this from inside your own admin area, which by design reports on your own community. Skoolgrades reads it through Attention Pull, which ranks external Skool rooms and posts by the share of your members' attention they capture. Ranking by share rather than by size matters: a room that owns a real slice of thirty of your members tells you something, a giant general community that one member joined does not.
Two honest caveats:
- Cross-community counts deliberately undercount. "Fourteen members active there" is a floor, not a total.
- Watchlist — the room-level view that surfaces fresh and trending threads in rooms you follow — is not real-time. Median lag from post to alert is measured in hours. Fine for weekly idea sourcing; useless for being first to a thread.
Used weekly, this is the source that keeps you from writing about what mattered last year.
4. Posts of yours that already worked
The single most underused idea source is your own back catalogue.
If a post got real engagement six months ago, most of your current members never saw it. Communities turn over. A post that worked is not spent — it is proven, and it can be re-run, expanded, updated, or argued with.
Three moves on an old post that worked:
- Re-run it with a new opening line and the current context. Compose has a repost recipe for exactly this.
- Go one level deeper. If the post was "three ways to do X", write the full version of way number two.
- Update it. "I said this in January. Here is what changed."
Judge which posts worked on comments, not likes. Skoolgrades counts engagement as comments plus polls, not likes, because a like costs the reader nothing and predicts nothing.
5. What is working in rooms near yours
Not to copy — copying reads as copying. To see which framings of a topic are landing.
Two owners can write about the same thing and get wildly different results based purely on the angle. Watching threads in rooms your members inhabit shows you which angle currently has heat, which you can then take and write your own honest version of.
The rule that keeps this ethical and effective: take the question, not the answer. If a thread elsewhere shows that people are anxious about a topic, your post is your own answer to that anxiety, from your own experience.
6. A ranked idea list, when you are genuinely stuck
Sometimes the well is dry and you need a starting point rather than a blank box.
Skoolgrades' Content Gems ranks original post ideas across a judged external network and your own corpus. Two parts make it more useful than a generic list:
- A "why this?" tray showing the reasoning behind the rank, so you can disagree with it rather than take it on faith.
- An audience list of the members the idea actually speaks to. This is the half people underuse — if an idea's audience is four people, it is a DM, not a post.
Gems is included on every Skoolgrades plan: three a week on Grow ($19/mo), unlimited on Pro ($99/mo).
How do I choose which idea is worth writing?
Choosing which idea to write comes down to four filters — did a real member ask for it, can someone reply from their own experience, does it still make sense to a new joiner, and is the audience bigger than a handful — because having twelve ideas is a different problem from having none, and arguably a worse one:
| Question | If no |
|---|---|
| Did a real member ask for this? | Downgrade it |
| Can a member reply from their own experience in one sentence? | Add a question they can answer |
| Would this still be interesting to someone who joined last week? | Save it for the regulars, not the feed |
| Is the audience for this more than a handful of people? | Send it as a DM instead |
The last row is the one that saves the most time. Not every good idea is a post.
How do I get more than one post out of one idea?
Getting more than one post out of an idea means building a hero asset first and deriving everything else from it, instead of burning your best idea on a single post the feed buries in three days.
The Content Flywheel exists for this: one idea becomes a hero asset — a lesson, a podcast script, or a 1,500 to 3,000 word post — plus shorts, Skool posts, a LinkedIn version and a newsletter derivative. One decision, many artefacts. If you have five real ideas a quarter rather than fifty, this is how five is enough. There is a fuller walkthrough in how to repurpose one Skool post.
How do I turn an idea into a finished post?
Turning an idea into a finished post is what Compose does, drafting from eight recipes: welcome, leaderboard shoutout, recognise commenters, milestone, fun, repost, clone a post that is working elsewhere, and freeform. Each comes with one-click copyable @mention tags, which is the tedious part of a recognition post removed.
Nothing is auto-posted. You review the draft, edit it into your own voice, and publish it in Skool yourself. That is deliberate.
So what is the short version?
The short version of sourcing Skool content is to stop looking for ideas and start collecting evidence. Fifteen minutes a week reading your own comments will out-produce any idea list you can find. Add what your members read elsewhere, the questions you keep answering in DMs, and your own posts that already worked, and you will have more ideas than posting slots.
Then filter hard — a lot of good ideas are DMs — and reuse the survivors instead of spending each one once. Pair this with what to post and when to post it.