Activity
Mon
Wed
Fri
Sun
Jul
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
What is this?
Less
More

Memberships

Clief Notes

35.6k members • Free

New Era Sales - Chris Rigoudis

973 members • Free

The Live Event Studio

513 members • Free

Strong Confident Living

2.9k members • Free

AI Automation Society

387.6k members • Free

16 contributions to AI Automation Society
Took 2 days to finish day 1 but..
I am so happy with what claude and I built here, beyond just scraping I also made an Alex Hormozi advisor as a Markdown file so that Claude references him for my builds and vision going forward... I am also going to have it make me a @Nate Herk advisor 🤩
Took 2 days to finish day 1 but..
0 likes • 12h
@Keiler Purcell thank you!
0 likes • 12h
@Leonardo Colon Thank you!! 🙌
Building an "AI operating system" for a small team — and I keep hitting the same architecture question. Curious how others have solved it.
The setup: small office (think 3–4 people, mixed technical ability). One person (lets say me but its for client ) has the power-user seat — Claude Code, all the skills, the full context. The others need to feed information in and benefit from the skills, but they're not going to live in a terminal. Where I've landed so far — call it "one brain, many feeders": • A shared brain (Drive folder) holds context, intake, and output • I sit in "mission control" with the one Claude Code seat and run the skills • Everyone else just drops structured files into intake folders — no terminal, no setup • Claude validates, organizes, drafts, flags what's missing — a human does the final publish/send Two principles that keep proving themselves: 1. Force the data + its context to arrive together (one folder per item, a fill-in template beside each file). Orphaned data is what kills these pipelines. 2. Automate the 95%, keep a human on the last 5%. What I'm chewing on: • Is per-person seats actually better than one operator + feeders? When does it flip? • Where should the shared brain live — Drive, repo, DB, something else? • How do you get non-technical teammates to feed it *consistently*? If you've built something like this — what's your stack and what did you learn the hard way? Genuinely want to hear implementations, not just theory.
1 like • 12h
I haven't tried, but one thing that comes to mind is, give the google drive access to claude, and all data the feeders "feed" to google drive and claude always has access to google drive
Just published my first YouTube video — Claude Code Skills
Been in the AI automation space for over 6 months. Shipped real clients, built voice agents, Make.com workflows, Claude API integrations. Just never touched content creation until now. That changes today. My first video is live — 14 custom Claude Code Skills I built that run my entire business. No agents, just skills. Cleaner, faster, more reliable. Would love feedback from people who actually know this space. What would you improve?
2 likes • 15h
I not sure how to say this in any other way than to say I am very proud of you for doing this. this was incredible to watch, GREAT WORK!
1 like • 13h
@Khaled Sid mhamed
Pewdiepie AI - Odysseus
Anyone gonna try it? I mean. It's apparently free🤷🏼‍♂️
1 like • 13h
looking into this RIGHT NOW lol, love Pewdiepie
Who is building their own personal AI OS?
Who is building their own personal AI OS from the ground up? I would love to talk to you about your strategies and frameworks you are using. Im getting started with mine and plan to scale it to be a whole team running itself with an orchestrator.
0 likes • 13h
quick question, I was going through the 7 day challenge should just go straight for the AI OS build? looking for genuine advise on this
1-10 of 16
Elias Batkhurel
3
29points to level up
@ankhbayar-batkhurel-7535
Finding the path forward

Active 9h ago
Joined Nov 19, 2025
Powered by