Leaderboards and Gems
Leaderboards make progress visible, but they should support the culture you want rather than define it. Use them to point members toward helpful contribution, learning, and the next useful action.
What it is
Inside a community, Skool leaderboards sit alongside points and levels. They help members see progress, custom level names, and course unlocks connected to those levels.
The Skool Games leaderboard is different. It ranks community revenue performance, not ordinary member contribution. Keep these two systems separate when you explain them.
Skool has not explained what gems do. Do not promise members that gems have a specific meaning or effect.
How a community leaderboard works
Members earn points when other people like their posts, comments, and replies. Those points move them through the levels described in Points And Levels.
The leaderboard can make that progress easier to see. It can also show course unlock context and your community's custom level names.
That makes the leaderboard useful for three things:
- Showing members that helpful participation is noticed.
- Making the next level or course unlock easier to understand.
- Giving you a chance to celebrate contribution that helps other people.
The rank itself is not the outcome. A healthy leaderboard points back to the behavior your community values.
How to use it well
Celebrate a member with enough context that others can learn from the contribution. Mention the useful question, answer, example, or progress that earned attention.
Use Post Format And Engagement to create conversations worth joining. Use Course Completion Drivers to connect level progress with meaningful learning.
If new members see a leaderboard during Member Onboarding, explain that it reflects activity inside this community. Their progress in another group does not carry over.
Keep an eye on Retention And Churn. A leaderboard that produces a short burst of activity but makes quieter members feel unwelcome is not helping the community.
Skool Games leaderboard
As of September 2026, the Skool Games run in quarterly cycles, and the leaderboard ranks communities by MRR Growth, the new monthly recurring revenue added during that quarter, with total MRR shown underneath as a secondary figure. Only the first $100 per month, or $1,200 per year, of each member's price counts, annual subscriptions are divided by 12, one-time course sales do not count, and charges from rejoining members are excluded. Skool Games Rules has the current details.
These are Games revenue rules. They do not explain how ordinary member points or levels work.
The Games landing page mentions leaderboards and rewards, but it does not provide the detailed rules, so check the current rules before you explain them to members.
Best practice
- Explain what earns points before asking members to care about rank.
- Celebrate useful contribution, not raw posting volume.
- Show which course unlocks are connected to levels.
- Use custom level names that fit the identity of your group.
- Give new members a low-pressure way to participate.
- Keep community leaderboards separate from Skool Games revenue rankings.
- Other creators describe weekly and all-time leaderboard tabs; Skool has not confirmed the details, so look at your own group before you explain them to members.
- Mention gems only as unknown until an official Skool source explains them.
- Review whether the visible winners reflect the behavior you want repeated.
Pitfalls
- Like trading and empty comments turn progress into noise.
- Public rank can discourage members when it becomes a measure of personal worth.
- Ordinary points do not explain Skool Games revenue performance.
- Games total MRR does not explain ordinary member contribution.
- One-time course sales are not recurring revenue, so they should not be presented as Games MRR.
- Refunds and cancellations lower the MRR the Games leaderboard sees.
- A third-party product update is not the same as an official Skool rule.
- Gems should not be presented as a documented platform feature without an official source.