You can now leave reviews on the about page (only paying members which is a little annoying but that's Skool settings not mine) It would seem there is a review page, even if you may not be staying long or have gotten your fill out of the content, if I have helped in any way please leave a review by clicking on this link to help others understand what is in here! https://www.skool.com/cliefnotes/about

34 entries. Jake, Don, David on isolated piles, then a panel. This one was hard. A few of you built things that would have won a different competition, and you should hear which one. Every entry got feedback, link at bottom of post! 📋 What we actually judged The post asked for one folder a stranger can drop into a Claude project. identity.md, rules.md, examples.md, reference/, README.md. It reads something broken and says why. Not how to fix it. Four questions, from the post: 1. Does it diagnose? One cause. Not a list. Not a prescription. 2. Is the domain specific enough to be useful? 3. Does each file do one job? 4. Can a stranger figure it out? That is an outcome. Can a person who is not already in your head use this to see why something in their world broke. A lot of the field went further. Refusal paths. Verifiers. Blind runs. Preserved failures. Those are real, and they are extra. We did not pick a winner on the extra. We picked a winner on the ask. this does not mean extra is not better, in many cases I LOVED the solutions created. If the outcome had been different, the name on this post changes honestly 🥇 Winner: Colm Whelan — Inbox Autopsy https://github.com/RockfieldIT/inbox-autopsy A stranger holding a bounced invoice can drop the folder in and see why it bounced. That was the assignment. 🔄 Where someone else wins 🔧 If the outcome was "the instrument that can prove itself wrong" — Sergey Manevitch, Radix https://github.com/sergeymanevitch/Radix Why a machine failed in a plant that already has notifications, rounds, and historian trends. Fourteen cold runs. He left the breaks in his own claims standing. A plant engineer is holding something serious. 🧪 If the outcome was "every claim reproduced, including the one that failed" — Pemmy Broke, Visual Momentum https://github.com/hoodwanders/visual-momentum-diagnostician Why an AI explainer lost momentum. She published the run that broke her own doctrine, changed the rules, and the re-run abstained. That is the standard the rest of the field should steal from.

It’s live. Starting today, everyone in Clief Notes has access to the new Clief Notes AI. The easiest way to use it? Don’t overthink it. Ask it the question you would normally ask me. “Where should I start?” “What should I focus on next?” “Where did you talk about [topic]?” It’ll use what’s already inside Clief Notes to help answer you and point you toward the right lesson or resource when there’s something worth going deeper on. The goal isn’t to give you another AI tool to play with. It’s to make everything already inside this community easier to actually use. If you want Access to it Comment "READY" and we'll send you access to it!

Hey everybody! I hope you are doing well. I know I've been a little quiet the past few months, but I have some interesting news and wanted to share a little 'sauce,' if you will, that I came across while writing and publishing my new AI book on Amazon. By the way, I highly recommend that if you have ever wanted to write a book, you just do it!!! Here's my story: #1. I happened to come up with a new way to use AI (July 2025) and wanted to test whether anyone was even interested in learning it, so I posted my ideas on LinkedIn. #2. After about a month of posting almost every day, I had a good idea of what people were thinking and saying, and how to lay out the book (so I thought LOL), and I started writing. #3. I had the first version of about six chapters done and shared it with 10 people on LinkedIn who expressed interest, and 4 of them actually read it. #4. I took their feedback, revised some chapters, and wrote a couple more. #5. I then gave the book out again (V2) and connected with two people who had read the whole book and were willing to jump on a Zoom call with me. #6. As I watched the first person start using AI the way I thought it should be done, I realized she had built her 'AI Intelligence System' correctly but was still using it like a search engine, and I realized I was MISSING half the book. 🤣 #7. So I condensed the now 8 chapters down to 6 and then wrote the second half of the book, showing people how to use AI not like a search engine or an answer machine. (I call it briefing AI like a CEO.) #8. I gave that version of the book (V3) to about 100 people (A mentor of mine a couple of years ago mentioned that when you do write a book, try to get 100 people to read it before you publish it; that will give you the truth you need about whether it should be published) I received more feedback, made some tweaks, and, after writing the book 4 1/2 times, I went ahead and published it. And believe it or not, I hit best-seller status in two days. The 'secret' is to send your Amazon book link to everyone who read it and ask them to buy it at a low price the day after publishing.

Go comment and like the video on YouTube as well ! Lots of cool ideas in this one.