On this page
Create a post, exact steps
From the desktop browser:
- Open the community you want to post in
- At the top of the Community feed, click the box that says What is on your mind
- A larger editor opens
- Type a title in the top field (optional but recommended, posts with titles get more clicks)
- Type the body in the larger field below
- Pick a category from the dropdown (most important step, see next section)
- Add attachments if needed (image, video, link, or poll)
- Click Post
That is the entire flow. The post appears at the top of the feed immediately and gets sorted by Skool's algorithm based on engagement.
On mobile:
- Open the Skool app
- Tap Community in the bottom nav
- Tap the floating plus button or the New post bar at the top
- Same fields, smaller screen
- Tap Post to publish
Stop doing this by hand. Automate it in 2 minutes.
Welcome DMs, churn-saver, pipeline, member exports. Free plan forever, paid tiers from $29/mo.
Categories and why they matter more than you think
Most owners set up two or three default categories and never think about it again. That is a mistake. Categories drive three things: filtering, notification settings, and Skool's algorithm.
Every member can filter the feed by category. Power users do this. If you post in the wrong category, the people who would care about your post never see it. If your community has an Accountability category and you post your weekly check-in in the General category, the people who follow Accountability miss it.
Members can also set per-category notifications. They might want every Live Call post emailed to them but never want Off-Topic posts. If you mis-categorize, you either spam people or miss the ones who care.
Skool's feed ranking also factors in category. A post tagged Wins that gets 50 reactions in an hour will outperform an Off-Topic post with the same engagement.
Recommended category structure for most communities:
- Start Here (read-only or pinned posts, onboarding)
- Wins (member outcomes, social proof)
- Questions (help requests, member-to-member)
- Lessons (owner long-form content)
- Live Calls (recordings and recaps)
- Accountability (weekly check-ins)
- Off-Topic (the trust-builder, casual)
Fewer categories than that and the feed feels generic. More than that and members never know which to use.
- 1Open the community feed
Log in at skool.com, click your community in the sidebar, you land on the Community tab by default.
- 2Click the new post box
At the top of the feed, click What is on your mind. The full editor opens.
- 3Write title and body
Title is optional but adds 30 to 50 percent more clicks. Body supports Markdown-lite formatting (bold, italic, lists, headings, code).
- 4Pick the right category
Use the dropdown. Wrong category buries the post. Match the category to the post type (Wins, Questions, Lessons, Off-Topic, etc).
- 5Add attachments if relevant
Images, video, link, or poll. Polls drive the highest reply rate. Carousels outperform single images. Videos auto-play muted in the feed.
- 6Hit Post and watch the first hour
Reply to every comment in the first hour. Skool's algorithm weighs early engagement heavily, so replies in the first 60 minutes drive long-tail visibility.
- 7Pin or feature if appropriate
Owners can pin to top of feed or to category from the three-dot menu. Use for Start Here posts, live call announcements, or launch posts. One pin per category.
Formatting tricks the editor does support
Skool's post editor supports a stripped-down Markdown set. It does not advertise this clearly but most of it works.
- Bold: wrap in asterisks like this
- Italic: wrap in underscores like _this_
- Monospace: wrap in backticks like
this - Headings: use # for h1, ## for h2, ### for h3
- Bullet lists: start a line with a dash
- Numbered lists: start a line with 1.
- Links: paste a URL, Skool auto-detects and creates a preview card
- Blockquote: start a line with >
- Code block: wrap in triple backticks
- Line breaks: two enters for a paragraph break, single enter for line break
What does not work:
- Tables. No native rendering. Use a screenshot instead.
- Inline images mid-paragraph. Images attach below the text.
- Color highlights. Editor is monochrome.
- Strikethrough. Not supported.
- Custom fonts. Not supported.
Link previews are aggressive. If you paste a URL it will try to embed a preview card with the title, description, and thumbnail of the linked page. Sometimes this clutters the post. To suppress, wrap the URL in standard Markdown link syntax: text here. Skool then renders it as a plain link, no preview card.
Attachments, polls, and links
Four attachment types at the bottom of the editor:
Image. JPG, PNG, GIF, WEBP up to roughly 25 MB. Multiple images per post (carousel). Carousels outperform single images for engagement. Aspect ratio 16:9 or 1:1 looks best in the feed.
Video. MP4 up to roughly 500 MB. Skool transcodes, gives you native inline player. Auto-plays muted in the feed. Most engaging post type if your audience tolerates video.
Link. Paste a URL, Skool fetches a preview card. Useful for sharing external content. Be sparing, communities can feel like a link dump fast.
Poll. Up to 10 options, members vote once, results show after voting. Polls get the highest reply count of any post type because voting and commenting feel adjacent. Use polls for genuine questions, not pseudo-engagement bait.
You can attach multiple types in one post (image plus link plus poll), but the editor only allows one type per post in some builds. If the buttons grey out, click Post first, edit the post, attach the second type, save.
Maximum post length is roughly 25,000 characters, which is dramatically more than you should ever use in a single community post. Posts above 1,500 words get scroll-past treatment from members. Break long content into multiple posts or move to the Classroom.
Post types that actually get engagement
After enough hours staring at Skool feeds, the patterns become obvious. The post types that consistently get replies, ranked:
1. Polls with a real question. Asking which workflow members prefer, or which option they would pick. Voting is low-friction, comments follow. Easily 2 to 3x reply rate vs text-only. 2. Personal stories with a lesson. Owner shares a specific moment from their week, ends with a question. Vulnerability plus question equals replies. 3. Wins from members. A member posts their result, owner amplifies in the feed with a tagged shoutout. Tags pull other members in. 4. Direct questions with a deadline. What is your top priority this week, drop it below by Friday. Specificity plus deadline. 5. Behind-the-scenes posts. Screenshots of work in progress, half-finished projects, lessons learned the hard way. 6. Resource shares with a specific recommendation. Read this article and tell me what you would do differently. Not just a link drop.
Post types that consistently underperform:
- Long announcements with no question at the end
- Resource dumps without context
- Re-purposed Twitter threads pasted in raw
- Sales pitches for the owner's offer (more than once a week feels gross)
- Generic motivational quotes
The rule: every post should give members a clear reason to comment. If you cannot answer what is the comment I want, do not post yet.
When to post for the most engagement
Skool's feed is recency-weighted but not strictly chronological. A great post from 6 hours ago can outrank a mediocre post from 1 hour ago. Still, when you post matters because it determines how many members see it in the first hour.
Post timing rules:
- Post when most of your members are awake. For US-heavy communities, weekdays 8am to 11am ET. For Indian audiences, evenings 7pm to 10pm IST. For UK and EU, 9am to 12pm local. Check your member CSV for timezone proxies if mixed.
- Avoid posting weekend mornings. Engagement drops 30 to 50 percent. Save big content for weekday mornings.
- Do not post twice within 2 hours. Your second post pushes the first down before it has had time to gather replies.
- Owners should post 3 to 5 times a week, not daily. Daily posting from the owner trains members to scroll past. Three high-effort posts a week from the owner plus member-generated content is the right mix.
Skool has no native scheduled posting. The workarounds: draft posts in a Google Doc or Notion and paste at the right time, or use a Chrome extension that adds scheduled posting to Skool. tools4skool.com adds scheduled posts to the community feed as one of its features, which is useful if you produce content in batches and want to drip it across the week.
Owner-only post features
Community owners and admins have a few options regular members do not.
Pin a post. Click the three-dot menu on any post, click Pin to top of feed. Pinned posts always appear above the regular feed. Limit one pinned post per category usually, more is overload. Use for the Start Here post, the current week's live call, or a launch announcement.
Pin to category. Some communities allow pinning per-category, so you can have one pin in Wins and another in Questions. Check Settings, Categories to enable.
Lock a post. Stops new comments without deleting the post. Useful for archived discussions or controversial threads. Three-dot menu, Lock comments.
Feature a post. Some Skool builds allow featuring a post on the About page so non-members see it. Useful for social proof, like a banner testimonial.
Tag members. Type @ followed by a member's name. They get a notification. Be careful, mass tagging is the fastest way to lose member trust. Tag only when relevant.
Mark as announcement. In some categories, owner posts can be marked as announcements which trigger email notifications to all members regardless of their per-category settings. Use sparingly, like once a month max.
Edit and delete. Owners can edit or delete any post in the community, not just their own. Use this sparingly. Deleting a member's post without warning is a fast way to lose them. If a post breaks rules, message the member first.
Stop leaving DMs, churn, and revenue on the table.
tools4skool plugs the holes Skool ships with. Free plan forever, paid tiers from $29/mo.
Frequently asked
Keep reading
Ready when you are.
Drop your email — we'll loop you in the day access opens.