Activity
Mon
Wed
Fri
Sun
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
What is this?
Less
More
Owned by Niklas
Your Skool data, in Claude, ChatGPT & any AI tool. Two ways in: free & open source on your machine, or hosted with zero setup. 🐈
Skooligans
622 members • Free
JOIN SKOOL
206 members • Free
4 contributions to JOIN SKOOL
🔥
1d •
I have some news!
Last hours I went though our complete library and found more and more communities that were closed or just well.. dead. I redesigned the Library into 1 Classroom, which is soooooooo much nicer 😅 1️⃣ Go see if your community is still there 2️⃣ If yes? Great! Keep reading! 3️⃣ The ones that are still in the Library can now promote! 4️⃣ I will start promoting/running ads towards your communities I'll explain: As a thank you for hanging around, the founding Library members are welcome to promote their community every weekend. Choose your weekend day, it doesn't matter, 1 post per weekend 🙌 Please make it something nice, no one wants to read an about page again and again 😅 It's time to start collab and get you guys out there. If you took the effort to read this post, CONGRATS you know you can promote now 😁
2 likes • 1d
@Jeff Baer Sounds good 💥
2 likes • 1d
@Mindy Molein there is something I’d like to promote aswell 🤔
🔥
2d •
💸 The money is hiding in your comments by Brian O'Neill
Brian O'Neill made this great video that I wanted to share with you. "How to Use Claude AI to Find What Your Audience Will Pay For"
2 likes • 2d
that's very ncie to have!! thanks for sharing :)
🔥
4d •
Do you have your socials linked?
I wonder if all of you have your socials linked to your Skool profile? I still haven't done this 🫣, need to do this asap! If you have other socials that you want to share, please put them in the comments under. let's get to know and support each other 😊
1 like • 4d
I have a good one ☺️ https://catknows.app
🔥
8d •
🐾 Stop paying somebody to read your own Skool data ✌️
You built the community - the members, posts, DMs, all of it. So why do Skoot, Skooly, Panda & SkoolKit charge you monthly rent just to look at it? Rude. So we fixed it. 🌉 The bridge between Skool and every AI tool. Skool has no public API. Catknows is the free, open-source client for its private one. Log in with your skool account and pull your members, posts, comments, likes, DMs & more into Claude, ChatGPT, Notion, a vault, raw JSON or what ever you want it to connect with. Now you can finally talk to your own data. "Who's about to churn?" "Draft this week's post." Your community, in the AI you already use. 💰 $0. Forever. Open source. Runs on your machine, with your login - your data never leaves your house. It's the foundation; you build on top. 🐈 Three steps: connect your Skool → plug into your AI → talk to your data. You're a co-builder here, not a customer. 👉 github.com/nklsschroeer707/catknows Served by catknows. You're welcome. ᓚᘏᗢ
4 likes • 8d
You can just copy this prompt and use catknows - you're welcome ♥ CatKnows — Fully Autonomous Installation Prompt You are responsible for installing and setting up CatKnows on this computer so that the user can start working with it immediately. Repository: https://github.com/nklsschroeer707/catknows Your job is NOT to explain how to install CatKnows. Your job is to actually perform the installation and setup yourself using the tools, terminal, shell, filesystem, and other capabilities available to you. PRIMARY GOAL Take this computer from its current state to a completely working CatKnows installation. When you are finished, CatKnows must be installed, configured, tested, and ready for the user to use. IMPORTANT BEHAVIOR Work autonomously. Do NOT give the user step-by-step instructions if you can perform those steps yourself. Do NOT stop after cloning the repository. Do NOT stop after installing dependencies. Do NOT assume something works just because a command completed successfully. Continue until you have verified that CatKnows actually starts and works. Do NOT send progress updates to the user. Do NOT ask unnecessary questions. Investigate problems yourself first. If something fails: 1. Read the error. 2. Diagnose the cause. 3. Inspect the project files and documentation. 4. Search the repository for relevant configuration. 5. Try the appropriate fix. 6. Run the command again. 7. Continue until the problem is resolved. Only contact the user before completion if there is a genuine blocker that requires human action, such as: - entering a password - approving an operating-system permission - logging into an external service - providing an API key or secret that cannot be generated locally - making a decision that cannot safely be inferred Otherwise, keep working. STEP 1 — INSPECT THE COMPUTER Determine the current operating system and environment. Identify whether the machine uses: - Windows - macOS - Linux - WSL - another relevant environment
1-4 of 4
