I was testing whether Catknows can read a community’s leaderboard. This appears to be separate from the member list rather than simply a `most_points` sort. The leaderboard page shows several pieces of information that `list_members` does not: - 7-day leaderboard - 30-day leaderboard - All-time leaderboard - Rank, member and points within each time period - The logged-in member’s own all-time rank - Current level - Points required to reach the next level - The community’s level structure from Level 1 through Level 9 - Custom level names set by the community owner, where applicable, such as “Guppy”, “Sardine” or “Big Tuna” - Percentage of members currently at each level So the same member can have a different position on the 7-day, 30-day and all-time leaderboards, while the level structure is another separate piece of community-specific data. Skool exposes all of this at: /[community]/-/leaderboards Would it be possible to add a dedicated Catknows leaderboard function that reads this page/data directly?

I have read a couple of comments in some communities about their search for Skool extension capable of scheduling posts. Is this something Catknows already capable of ? or @Niklas Schröer ... is this something in development ? 🙏🪶🕯️🏮✨💫❤️🚀

Tonight, 19:30 Berlin time (CEST) — that's 1:30 PM ET / 10:30 AM PT — the weekly 🗞️ catknwes. call is on. And this one's special. Quick answer for anyone landing here for the first time: catknows is a free, open-source tool that connects your Skool community to the AI you already use — ChatGPT, Claude and more. Skool has no official API and no real analytics dashboard. catknows fixes that. You just ask in plain English: "Who joined this week and hasn't posted yet?" · "Which post got the most comments?" · "Summarize my unread DMs." Tonight we'll talk about three things: 😼 What catknows can do RIGHT NOW — members, posts, comments, DMs, admin metrics, even the Discovery leaderboard 🐾 How I use it myself, LIVE — real workflows on real communities, no slides 🚀 What's NEXT — because the data layer is just the door. Behind it: endless possibilities for how you see, understand and serve your people. Make the invisible visible. People, not pipelines. Before we go live, some love for the hoomans who made this the best week this community ever had: @Des Cooke joined and was posting straight from Claude within minutes. @Mercedes Aspland put catknows to work on her 2,600-member community and wrote the review of the week. @Iyaraa Iam asked the questions that became our best thread so far — public vs. private communities, go read it — and @Mindy Molein dropped the answer of the week in it. @Dan Schaad ran a full diagnostic and keeps making the cat smarter with every bug report. And to everyone who jumped in this week: @Keith Berg @Rositsa Aleksandrova @Elfina Luk @Deleted @Éva Raposa @Ben B. @Joseph Isosaki @Kaseem Bradley — you're the reason this exists.

Hi, I'm Des. I'll do an introduction post at some other time. I just wanted to do a post directly from Claude to highlight the fact that I am up and running in a matter of minutes, once I got my head around how the MCP connects to Claude.

@Niklas Schröer I am wondering if you have been exploring things and figure out any patterns, signs or indication to do with communities in Public vs Private mode? Pros : Cons Indexing : Members holding back Anything that might compare the 2 modes ? Any data on that at all of if the Cat might be curious and dig up some gems !? 😸🪏💎🔥🌱🎯🚀💛