Someone packed 100 numbered tips for running Hermes into a single graphic. It's the kind of image you screenshot, lose in your camera roll, and relearn the hard way a month later. That's the same leak I used to accept with client docs locked in a PDF: knowledge sitting in a format nobody can search. So I transcribed it. The author is @witcher, posting as @HERMESWATCHER. Every tip is a failure mode he actually hit running the thing all day. I run Hermes too. I didn't write these. My contribution is the OCR work and one warning about the numbering, because the first question everyone asks about this graphic gets answered wrong. The classroom resource has three parts: - All 100 tips, word for word. Sorted into 9 categories: messaging, projects, models and cost, memory, tools, safety, skills, automation, maintenance. Nothing rewritten, nothing dropped. - A read on the numbers. The instinct is that #01 means "most important tip." That instinct is wrong. The numbers are publication order, and the post shows the evidence. If you want a ranking, count tips per category. Seventeen of them are about models and cost. Frequency is the ranking. That's where the author thinks the payoff is. - Full credit at the bottom. Every tip is @witcher's work. I transcribed the graphic and wrote the numbering read, and I kept his wording exact. If you run Hermes, or you're weighing whether a personal agent platform is worth your time, this is the cheapest field guide you'll find. It's the collected failure modes of one person who ran it all day, in text you can actually search. Read it here: https://www.skool.com/cliefnotes/classroom/c7f102c7?md=3792316e817c415ba543307a11206535 When you're done, drop the one tip you're already living and the one you're stealing this week. I want the boring version that survived a month.

https://www.loom.com/share/e545ffb7b80b4112a126aa28df97e80e

A rainy day, an ICM folder, and the first PC game I ever played back in the ’90s. Production costs less than what I could sell it for on the App Store.😁 #hyperfocus

Still playing around with Claude mods and a lot of you liked the last one: https://www.skool.com/cliefnotes/heres-a-free-claude-plugin-to-help-you-see-where-your-context-is-going?p=f1f7d304 So here's a new one I'm using currently! https://github.com/donroy26/claude-watchdog Calling it Claude-watchdog. Basically it creates a menu where you can pin sessions you want to follow but aren't actively working in and it will show you if the session is waiting on you and give you a quick haiku powered summary of what's going on as the session progresses. Just like last time, works in terminal or the desktop app! Let me know if you like it! It's great to be able to pull information about your workflows together so easily now and display them exactly how it makes sense to you.

We just crossed 50,000 members 🎉. Today. Not a projection. Not a “coming soon” slide. That number broke because Jake showed up with ICM and actually shipped it into a room that doesn’t treat people like leads. The welcome here isn’t a drip sequence. It’s people answering questions, sharing the folder, and sticking around after the first win. Most communities rent attention. This one compounds it. Jake’s ICM didn’t land in a vacuum - it landed in a stack that already preferred transparent workflows over vendor theater. Members didn’t just buy. They stayed, tested, and pulled the next person in. From empty chairs to a milestone that pays people back. Stop chasing the next shiny cohort. Start owning the room that keeps grinding after the launch email dies. If you’re in, say what you got out of it. If you’re watching, the door’s still open.