Last month I was speaking with a friend who works for an engineering firm in Australia about ai, and all the cool things we can do with it these days, and he mentioned that he was trying to push to get a monthly newsletter out to their team to inform them of upcoming professional development courses and workshops. Of course it takes a lot of time to manually search the relevant websites, and put together a newsletter, etc. so no one has done it. I asked a few more questions about the tools they use, and then went and built out a small, structured ICM folder system, with the exact same blueprint that we have been learning in here and using for the competition building. I then made a loom video showing how it worked, and then emailed it to him along with the fully company branded email that it output. It was near the end of financial year at the time, so they were a bit busy, and he said he'd get back to me. Today, 1 month later, he came back and accepted my quote of $600, which includes 2 rounds of revision. To get the draft up and tested, it took me probably about 4 hours, and then there will be another few hrs in finalising it (with the revisions). In reality I probably undersold myself, but this is a side project at the moment (I run a cafe, not an ai consulting business...yet!), and I was excited to have the opportunity at a real client to test against. Let me be clear, I'm not selling a fancy Ai loaded website or app or anything... It is literally 5 folders, with a top level claude.md file, instructing claude co-work (or claude ai or code - or any other Ai tool that can follow structured instructions with a renaming of the claude.md file) on exactly what to do. This is exactly what Jake has been teaching here, and it will stand the test of time. As Anthropic updates their interface, and Open Ai starts to take over claude or another better tool comes along, this ICM folder system will continue to do its thing. It may need some tweaks along the way, but it's not going to need it's whole codebase updated or anything, because it's all plain language, english instructions.

my Live Health Stream is a real-time telemetry dashboard designed to monitor the "cognitive load" and operational stability of autonomous AI agents across different sessions and models (e.g., Gemini 3.1 Pro, Claude Sonnet 4.6). I am using both AntiGravity and Claude Code. They write to my obsidian vault, and my dashboard is a HTML/CSS version of that data along with python scripts that aggregate my json data for metrics I want to measure. Tool Error Rate % (Red Line) - What it is: The frequency at which the agent is failing to execute its tools properly (e.g., syntax errors, bad file paths). - How it’s calculated: (Failed Tool Calls / Total Tool Calls in the session) * 100. Notice on the graph how the red line spikes almost immediately after the green saturation line peaks. Context Saturation % (Green Line) - What it is: A measure of how "full" the agent's brain is getting. - How it’s calculated: (Total Input Tokens / Model's Maximum Context Window) * 100. If this hits 100%, the agent starts forgetting earlier instructions (context eviction). Lessons Learned (Yellow Bars) - What it is: The number of times an agent gets caught in a recursive failure loop (trying the exact same failed action over and over). - How it’s calculated: Programmatically tracked by analyzing the execution log for identical, sequential failed tool calls within a single session. I have a "Lessons Learned" log that I have my agents read on boot, and then if they **** up they have to record a lesson there, and update the .json file for that session where i build this graph from. Input/Output Tokens (Blue/Purple bars) Since this is not exposed I have to do an estimate: "input_tokens": input_bytes // 4, "output_tokens": output_bytes // 4, One of my core philosophies is No Vanity Metrics, and another is Things that are Measured Improve, and Ultimately, The Most Important Things Cannot Be Measured.

Three months in this community and I kept losing things. Someone would post a tool in Show Your Work. I'd think "I'll come back to that." Then it was buried under 40 more posts and I couldn't find it again. @David Vogel and others have built some great workarounds to highlight posts and info, but I wanted to put together something that helps me find those tools I'll otherwise flag and forget. So I scanned both categories and built an index. 72 tools. 7 categories. Standalone HTML file: open it in any browser, no login, no server, no account. What it does: - Real-time search by name, author, or keyword - Filter by category (Memory, ICM, Writing, Design, Media, Workflow, External) - Every card links to the original post and the GitHub or site - "Leave Review" generates a formatted reply you paste into the original post - "Submit a Tool" generates a post template for Resources & Finds What's in it: Memory: PMM, Cortex, Session Memory Layer, Codebase Memory MCP, and a non-technical PMM folder template for people without a dev background. ICM: Brofessor, ICM-Builder, Foundations Tutor, CoworkOS, IBE Workflow, Shipyard, Creator Orchestrator Template, PAFA, and more. Writing: Critical Editor, Council of 5, LinkedIn Content Wizard. Design: tastecheck, Weirdness Engine, Open Design, art-direct, Shade_. Media: to-md, TypeWhisper, YouTube Extraction Pipeline, Pushing Talk_. Workflow: ARI-OS, Astrid, SkillOpt, Nightwatch, Porter, The Maintainer, Subscription Auditor, and more. External: Miessler's PAI, Hermes Agent, Zuki, Signal Harmonics, GiTeam, and others. GitHub (open for contributions): https://github.com/FiSimply/clief-notes-index The README has instructions for adding via PR or the Submit button. Anything I missed, drop it in the comments & I'll add it. If there's a better way to accomplish this inside the Skool site, please comment. My way is not "the way" and I'm always open to alternatives.

🎯 WE READ ALL OF YOUR RESPONSES. HERE'S WHAT'S NEXT (AND A BIG ASK) A couple weeks ago we asked you what you wanted Clief Notes to become. You showed up. You wrote real, thoughtful answers, some of you wrote essays. We read every single one. Twice. So before anything else: thank you. This post is us answering you. 💬 YOU TOLD US. HERE'S WHAT WE'RE BUILDING. You said you want a clearer path from learning ICM to actually getting paid for it. → It's coming. A real learning-to-earning track, plus a talent platform we're building to connect you with people who want to hire what you can do. Heads up: the talent platform will be Premium and VIP only, one more reason to lock in below. You said competitions without feedback don't help you grow. → Fixed. Going forward, every single entrant gets tailored feedback on their build, not just the winner. We're moving to two competitions a month so we can do it right. And both monthly winners get a 30-minute call with me. You said the best builds get buried in the feed. → We're building a tagged library so you can actually find "ICM setups for solo operators" or "small team, non-coder" instead of scrolling for an hour. You said you couldn't map all the pieces, Skool, Discord, the Lyceum, ICM, what each tier unlocks. → A single orientation page is on the way. One place that breaks all of it down so nobody's lost. You said you want to connect with each other. → We hear you. Meetups, pairing, and a recorded "After Tea" hangout are on the table. South Florida alone has over 1,000 of you. Let's use that. You said we've felt spread thin. → The most honest one. You're right. We're bringing on real help to run the day-to-day so the community gets consistency, and so Matt and I can keep building the things above instead of dropping balls. You called it, and we're fixing it. 📍 QUICK NOTE ON ICM: a few of you asked for "ICM with Copilot" or "ICM with n8n, Sheets, GoHighLevel." Good news, ICM already works with any model and feeds straight into the tools you're using. It's the structure underneath all of them, not a separate thing you have to relearn per tool. If that's not landing for you, that's on us to make clearer, and we will.

Afternoon Tea, 2:00pm EST, 30 minutes for premium members: https://forms.gle/KySPdt9Dz4iJP3kdA High Tea, 3:00pm EST, a full hour for VIP members: https://forms.gle/wAJHrCv7sJYXgono6 Bring real questions and we'll answer them live. Submit them so we hit the ground running!