User
Write something
๐Ÿ”’ Q&A w/ Nate is happening in 3 days
Pinned
๐Ÿš€New Video: I Tested 3 Ways to Deploy Claude Agents (Here's When to Use Each)
If you've built skills and agents in Claude Code, the next step is getting them to actually run while you sleep. In this video I break down three simple ways to deploy your Claude Code automations, from the dead-simple /loop command to scheduled tasks and Claude routines, all the way to pushing your skills to Modal or Trigger.dev. You'll walk away knowing exactly which method fits which type of automation and how to pick the right one based on where it runs and how agentic it needs to be.
Pinned
ANNOUNCING: What's working in AI in 2026 (real projects, real revenue)
Quick news. We're doing our first virtual event, and the rule is simple: every person on stage has to show their actual work. The actual projects they're selling. The actual outreach they're using to land clients. The actual numbers behind it. No theory. No tutorials. Just what's working in 2026, taught by the people doing it. Waitlist's open. Get on it before tickets go live: -> What's working in AI in 2026 (real projects, real revenue) PS: Annual members of AIS+ get in for free. We will be announcing discounts for monthly members. If youโ€™ve been thinking about joining AIS+, itโ€™s a good time.
Pinned
๐Ÿ† Weekly Wins Recap | May 9 โ€“ May 15
From โ‚ฌ17K agentic systems and $35K builds to AI leadership roles, first workflows, and launched products - this week inside AIS+ showed what happens when consistent reps finally start compounding. ๐Ÿš€ Standout Wins of the Week inside AIS+ ๐Ÿ‘‰ Malek Kilani closed his first โ‚ฌ17K agentic AI build for a sales coaching company using enterprise presales experience as the unfair advantage. ๐Ÿ‘‰ @Michael Elliott shipped a $35K certification platform with 100+ API endpoints, Stripe integrations, AWS infrastructure, and recurring monthly revenue attached. ๐Ÿ‘‰ @Ailin Werner landed a Head of AI role after 8 months out of work by building publicly, sharing demos, and consistently showing her work online. ๐Ÿ‘‰ Ismail Islam officially launched TradePulse โ€” a full AI-powered trading intelligence platform combining dashboards, Telegram automation, and economic analysis workflows. ๐Ÿ‘‰ @Cagri Sarigoz launched HeyNews on Product Hunt after 12 months of iteration and more than 600 AI-assisted newsletter issues. โธป ๐ŸŽฅ Super Win Spotlight | @Ailin Werner Ailinโ€™s LinkedIn Ailin joined AIS+ after losing her job and deciding to fully commit to AI automation. At first, she was learning step-by-step through ChatGPT, debugging workflows manually, and spending countless hours figuring things out alone. Then she joined AIS+ planning to stay for just one month. That quickly changed.
๐Ÿ† Weekly Wins Recap | May 9 โ€“ May 15
Hermes agent/workspace
So i have been playing around with hermes and recently hermes workspace, I was curious about how users are backing up - server backup or github repo with cron. I came across a git repo skill but its seems to contradict what it will do, this is the skill hermes-backup-repo it mentions Include: - ~/.hermes/config.yaml - ~/.hermes/.env - ~/.hermes/auth.json but later states Store secrets only in ~/.hermes/.env which should already be excluded by .gitignore patterns. so if they are excluded why is it included? the workspace folder is outside of the hermes agent folder - I can link to it as part of the backup, has anyone got a github skill that can work with hermes and hermes workspace or should I just modify this hermes-backup-repo skills to fit my purpose? thanks
0
0
Future-Proofing Our Builds: How are you handling Agent Portability? ๐Ÿ”„๐Ÿค”
Hey everyone! ๐Ÿ‘‹ I watched and meditated on Nateโ€™s recent video:Anthropic Just Dethroned OpenAI. Here's What Happens Next. and one specific operational insight really struck a chord as I structure these new agentic workflows for my agency: "Portability is the antidote to vendor dependency. A resilient project should be movable within about an hour without derailing the week." As the landscape shifts, I want to make sure I'm setting up my local foundations correctly so I don't get permanently locked into a single vendor's ecosystem. Conceptually I get it, but practically, I'm hitting a bit of an architectural wall. For the experienced builders in the trenches, Iโ€™d love to get your technical insights on a few things: 1. Local Organization: How are you currently organizing your local projects to maintain seamless portability between different agents like Claude Code, Codex, and Opencode? 2. Decoupling Logic: Do you utilize any specific frameworks or directory structures to cleanly decouple your core business logic from agent-specific LLM calls? 3. Skill Interoperability: Are there shared architectural patterns you recommend for making skills and plugins interoperable across agents? (Specifically, I'm trying to minimize redundancy and avoid storing the exact same skills in different folders for different coding agents). I want to build a resilient tech stack from day one. Would love to hear what your local architecture looks like! Drop your setups and frameworks below. ๐Ÿ‘‡ Thanks in advance! ๐Ÿš€
0
0
1-30 of 16,894
AI Automation Society
skool.com/ai-automation-society
Learn to get paid for AI solutions, regardless of your background.
Leaderboard (30-day)
Powered by