Skool features: what's actually in the box (and what isn't)

Community feed — the front door

The feed is what members see first. It's a vertical scroll of posts in categories the owner defines.

What works: clean UI, fast load, supports text, image, video, and link previews. Members can pin posts, comment, like (called 'thanks'), and follow specific posters. Categories are a single layer — no sub-categories.

What doesn't: no scheduled posts natively, no post drafts visible to other admins, no bulk moderation tools beyond delete-and-ban. Owners running multiple admins often end up with posting collisions because there's no internal calendar.

The feed sorts by recent activity by default. Owners can pin a welcome post and a few category-specific announcements. Search exists but is basic — keyword match only, no filters.

For scheduled posts and a post-now button (useful for time-zone coordination), tools4skool adds a layer on top — owners draft once, schedule by category, and fire instantly without leaving the editor.

Start your own Skool community in 60 seconds.

14-day free trial — no card required. Most community owners decide whether Skool fits within the first week.

Start Skool free trial →

Classroom — the course tab

Skool's course builder is intentionally minimal. Each course is a stack of modules, each module a stack of lessons. Lessons hold video, text, images, and quizzes.

What works: drag-and-drop reordering, video upload (Skool hosts it via HLS), drip-by-day or unlock-by-leaderboard-points, basic completion tracking, certificates.

What doesn't: no SCORM, no Zapier-on-completion native, no per-cohort variants. If you want to gate one course behind another, you need clever leaderboard rules. Quizzes are bare — multiple choice and true/false only.

Video player: HLS-based, plays on desktop and mobile, supports 1.25x to 2x speed. Captions are upload-only, no auto-generation. Owners with longer videos sometimes complain about transcoding queue length on weekends.

Completion data lives inside the dashboard. Exporting to a CSV is supported on Pro tiers. Triggering automations off completion (welcome email, unlock content, tag member) requires either the API or an extension layer.

Calendar — for live calls

The calendar tab is a thin layer for posting upcoming events. Owners create an event, add a Zoom or Google Meet link, set a time, and members RSVP.

What works: timezone-aware display per member, RSVP count, automatic Google Calendar export per attendee, recurring events.

What doesn't: no native video — Skool punts entirely to Zoom. No reminder push notifications closer than 24 hours out. No post-event recording archive (you upload that to the classroom manually).

For coaching communities running 2–3 calls a week, the calendar is sufficient. For higher-volume event programming, owners often pair it with a separate scheduling tool (Calendly, Cal.com) for individual office hours.

Members directory and DMs

The members tab is a flat list of everyone in the community: avatar, bio, join date, leaderboard position. Click a profile to DM directly.

What works: visible to all members by default (owners can hide), searchable by name, sortable by recency or activity. Profile pages show recent posts and comments. DMs are 1:1 with image and link support.

What doesn't: no tags, no notes, no segmentation. It's a list, not a CRM. Owners who want to track 'paid in full vs trial,' 'high-engagement vs cold,' or 'pipeline stage' have to do it externally.

DMs themselves are clean but bare: no scheduled sends, no templates, no bulk send. Owners running structured onboarding sequences or churn-recovery DMs build that on top of Skool — tools4skool is the most common Chrome extension layer for exactly this. It adds DM sequences with multi-condition triggers (joined and viewed and didn't post type rules), image DMs, and a CRM pipeline that auto-tags members based on behaviour.

Leaderboard — the engagement engine

The leaderboard is Skool's signature. Members earn points for posts (3), comments (1), and 'thanks' received (1 each). Points roll up into ranks (Levels 1–9). Higher levels can unlock courses or hidden categories.

What works: actually drives behaviour. Members will post and comment to climb the board. The unlock-by-level mechanic gives owners a clean way to gate advanced content behind engagement.

What doesn't: gameable. A member can spam comments to climb. Owners moderate this manually — there's no native anti-abuse logic. Points decay is not configurable; once earned, points stay forever, which means long-term members dominate even if currently inactive.

Weekly and monthly leaderboards refresh and give newer members a shot at recognition. Most successful Skool communities use the weekly board as a social proof loop — top-3 members get DMed by the owner, screenshotted, posted back to the feed.

Chat — rooms and DMs

Chat is a recent addition. Owners can spin up channels (think Discord-light) for topics — general, wins, off-topic. Members chat in real time with image and link support.

What works: low-latency, decent mobile experience, push notifications hit instantly. Threading exists at a basic level. Searchable history.

What doesn't: no role-based permissions beyond admin/member. No reaction picker beyond a small set. No voice or video chat. No bot integrations. If you came from Discord, the lack of customisation will be jarring.

For communities that already have a strong feed culture, chat tends to underperform — most engagement stays in the feed. For high-tempo cohorts (live launches, weekly sprints), chat works well.

Payments and Stripe

Skool routes all member payments through Stripe Connect. Owners onboard a Stripe account, set the price, and Skool handles the checkout UI.

What works: one-click checkout for members (credit card, Apple Pay, Google Pay, sometimes ACH for US owners), auto-renewing subscriptions, cancel-from-billing-tab self-serve, owner payouts to bank in 2 business days.

Fee structure: 2.9% + $0.30 per Stripe transaction (this is Stripe's fee, passed through). Skool does not take an additional percentage — that's the platform fee in the Hobby/Pro plan. So total cost on a $100 charge is the platform plan plus $3.20 in Stripe fees.

What doesn't: no native discount codes (workaround is multiple price points). No upsells from inside Skool — for second purchases, owners punt to external checkout (Stripe Payment Links, ThriveCart). No free-trial-to-paid funnel native (owners build this with two communities and a manual nudge).

Refunds: at the owner's discretion. Skool won't enforce a cooldown.

What Skool intentionally doesn't have

These aren't bugs — they're product choices. Skool is designed to stay simple. The cost is that owners running real revenue hit the gaps and need bolt-ons.

• No DM automation. Welcome sequences, drip follow-ups, churn-recovery DMs — all manual.
• No CRM or member tags. The members list is flat. No segmentation.
• No churn detection. When someone cancels, you find out from the email. No early warning, no risk score.
• No comment-to-DM workflow. Hot commenters require manual handle-copy and message-write.
• No native email broadcast. Skool sends transactional emails only.
• No deep analytics. Member count, MRR, retention rate at the basic level. No cohort, no engagement heatmap.
• No bulk member export with metadata. Exports are basic — name and email. No tags, no last-active, no engagement score.

tools4skool is a Chrome extension that fills exactly this list — DM sequences with multi-condition triggers, image DMs, churn-saver firing within 60 seconds of cancellation, churn-risk scores per member, comment miner that pulls leads from threads, slash commands in DMs, scheduled posts and post-now, member CSV export with full metadata, Kanban-style pipeline. It piggybacks the existing skool.com session — no password handed over, no second login. Free plan covers 1 sequence and 20 DMs/day for testing.