Jamie Lambe Benjamin Burt Jonathan George I couldn't find you in the search member! Happy to reconnect or if anyone know's their @ handle that would be appreciated.

I've been building an Operational Second Brain for over three months, and I use it every day. It's one big ICM container that holds all my work. It has no L2 at the root, and inside it live the classic ICM processes I run. What it does: 📋 manages projects and tasks 📚 holds all my knowledge, organized by department 💾 manages memory and brain profile 👥 tracks the people I work with and the roles they hold in each project 🧩 It's also an ICM expert. I put in everything I learned studying here, so when the system evolves, it evolves according to ICM methodology and with ICM processes. 🛡️ Integrity control mechanisms are planned. The goal is a proper harness on the agent's behavior, so that as the system grows the structure doesn't degrade and stays ICM. 📏 On size: ICM says keep things small, and this is a big container. I think I managed to adapt it so it stays efficient. After three months of daily use it works really well for me. 🔄 When I notice the agent's behavior degrading, I run commands that make it reread its behavior rules, and it goes back to the expected behavior pretty well. Determinism in agents is impossible, but with the right harness I'm finding you can get controlled behavior. And the actual work and outputs come from classic ICM workspaces anyway. ⚠️ The one real problem I see is the root AGENTS.md. It has grown to about 900 lines, roughly 25k tokens. It's read once, at session start, and that's what makes the system behave the way I expect. I'm working on shrinking it. It's the part that goes most against ICM 🫣 Have you built or used systems like this? How would you handle it, and what do you think?

## UPDATE ## Hey All made some updates to the extension, full changelog below but biggest thing is it's now in the Chrome webstore as an unlisted extension! To install for firefox should be a 1 click install below, and for Chrome follow the link to the web store: Firefox: https://github.com/rocleemusic/skool-view-dist/releases/download/v0.3.2/skool-view-0.3.2.xpi Chrome: https://chromewebstore.google.com/detail/skool-view/cffkfollpgckdnelbincojldcmhihfgm?authuser=0&hl=en BONUS: Edge users can install extensions from the Chrome Web Store (just for you @Jake Van Clief ) so you should be able to install it as well, just need to enable it because of permissions (see below). Note on the Chrome extension: It may be disabled by default because of permissions issues so you might need to enable it by going into your extension settings, but after giving it permission it should be good to go. Chrome signing / validation also takes longer so it may be on version 0.3.1 but after it passes review should auto-update to 0.3.2 Also special thanks to @M. M. who forked and added some features that I wrapped in to this release. Things I'm hoping to add: Real links to the posts, currently it caches the data. Search functionality, and export post as .md. ## ORIGINAL POST ## Browsing on Skool can be a bit overwhelming with it's UI (my eyes need a dark theme) and the great volume of stuff on CliefNotes makes jumping in daunting, especially if you're away for more than a day, so I wanted something that made browsing feel effortless and easier to navigate and see things and keep posts around that I wanted to dig into a bit more. So I built a browser extension that gives me a faster, cleaner view over the same Skool feed, posts, and comments.

This community is large and it moves fast. That's the good part and it's also the problem: valuable posts get buried, the same questions get re-asked instead of found, and spammers show up wherever there's an audience. These guidelines are what keeps the room worth showing up to. Read them once. You won't need them again, because most of this is what you'd do anyway. New here? Start with Jake's welcome post and the Foundation course. This post is about how we behave, not where to begin. 1. Build in public. Post the thing while it's half working. A half-finished build is more useful to everyone else than the polished writeup you'll never get around to, and you'll get corrected before you've spent a week going the wrong way. 2. Teach what you learn. The day you figure something out is the day you're best at explaining it, because you still remember exactly what confused you. A month later you've forgotten the hard part and your explanation gets worse. If you cracked something this week, that's a post. Nobody has to earn the right to ask a question here, but this place only works because people come back and answer them once they can. 3. Ask good questions. Specific beats polite. "How should I structure this?" gets three vague answers. "I have a 40 file client folder, the model keeps loading the wrong context file, here's my CLAUDE.md" gets a real one. Say what you tried, what happened, and what you expected instead. A more in depth guide: https://dontasktoask.com The flip side of this: "Anyone here?", "Help please", and one line questions with no context may get removed. Not to be harsh, but because nobody can answer them. 4. Give credit. If you built on someone's skill, template, folder structure or comment, tag them. It costs you nothing and it's the reason people keep publishing their work here instead of keeping it. A lot of the best material in this community started as somebody's reply on somebody else's post.

I started this community in March. For months I've been reading your questions. Where do I start? What's a skill? How do I get this working on my own files? What even is an agent? So I rebuilt Foundations to answer all of it, in 11 new lessons full animated, voiced and structured to answer as many as I could. They are not just AI slop either, I spent Hours on every video, every concept.I deleted and redid lessons over and over until they finally worked, and what you see is what survived. I have been adding and spending hours upon hours adding more resources and working with others to provide value here since March. And I want to keep doing that. Now usually course creators lock up their entire community behind a pay wall at this point...I thought about it honestly. We would probably make more money if I put more behind a paywall. However, decided not only am I going to keep it free, but I'm also lowering my prices for premium as well. From $27 to $11 a month, everyone told me was a bad idea, that it was too low of a price for the hours we are putting in but I have faith in one thing, YOU. Its only a bad idea if people don't support, work together and make this worth it. I want to make info more accessible. This community has let me hire people, pay people, and build things I never could have built alone. I've got a team whose families count on this company, and a baby on the way, so I've been thinking hard about how this place keeps growing. More free lessons, more of my time, more people to help run it. I pay the instructors in my live programs $150 an hour, our mods are working hard and were working for free before I started paying and every free video here takes me hours to make. If enough of you chip in a little, all of that keeps going for everyone. So that's the ask. $11 a month, about 37 cents a day.