@Sasha Washuk you're the best man

@Elias Batkhurel also i'm not sure how to answer your message more than you're great person 🤍

what's worked for me is building it on claude code with one root CLAUDE.md as the single source of truth, then everything else hangs off that, skills, memory, scheduled routines. the 3Ms framework (mindset, method, machine) is what i use to decide what to automate next instead of building random stuff. don't copy someone's exact structure tbh, start with the one doc and let it grow from your real workflow. what are you running it on rn?

welcome man. biggest tip is pick one workflow you already do and automate just that, don't try to learn everything at once. for connecting stuff make.com is the easiest to start with since it plugs into basically everything (gmail, sheets, slack, openai). once you outgrow it n8n gives you more control. what kinda tasks you trying to automate first?

not one master list that i've found, it's kinda scattered across the starter kit + resources tab. what i did was just build my own skills inventory doc and add each one as i installed it, way easier to actually use that way. happy to share how i structured mine if you want

they solve different problems tbh. Hermes is more of a single agent you point at one job, the claude OS is the whole desktop running on claude code where you talk to it and it actually touches your files, calendar, scripts etc. i run the claude one daily and it's way more "operator" than "tool". if you want one task automated start with Hermes, if you want a system that runs your day go claude OS