About Me

The boring Claude setup that actually works.

I work a full-time 9-to-5 and run everything else with Claude and a few unsexy tools. No code, no team. I break everything weekly so you don't have to, then post the exact setups in plain English so non-coders can copy them.

Chris Alarcon Operator

The Real Story

Drowning, then building.

I was drowning in content tasks. Writing LinkedIn posts manually. Staring at blank screens for YouTube scripts. Copying and pasting captions across 5 different platforms. There had to be a better way.

So I built it. Week after week, I refined content systems using n8n, Claude, and whatever tools actually worked. Now I have pipelines that source ideas, write scripts, generate posts, and schedule everything. Automatically.

Here's the thing: I'm still building while working full-time. Everything I share is battle-tested on my own content. If it saves me time, I'll show you exactly how to set it up.

Full Transparency

How this content gets made.

I run my content the same way I run everything else: AI does the heavy lifting, I own every call that matters. I pick every topic. Every post starts from something I actually tested, paid for, or got burned by. My take goes in first, in my own words, before anything gets drafted.

Then AI is my writing team. The same Claude systems I write about are the ones producing these pages. That's not a confession, it's the demo. The rules the whole pipeline runs on: nothing publishes without my input, every claim links a real source, and if I haven't done something myself, the post says so instead of pretending.

If you ever catch a page breaking that rule, tell me and I'll fix it in public.

Core Principles

What I believe.

01

Ship Over Perfect

Done beats discussed every time. I'd rather launch something imperfect than polish forever.

02

Systems Over Hustle

Work smart, then work hard. Every repeatable task is a system waiting to be built.

03

Proof Over Promises

Real numbers, real workflows, real results. I share what actually works, not what sounds good.

Build in Public

What I'm building.

Real systems I use daily. Some are polished, some are experiments. Updated when something ships.

01
Video Cuts Agent Running
Runs weekly. Drop a raw recording, get back an 80-90% finished edit. It's a Claude skill now: it transcribes the take, cuts the retakes and dead air, renders the video, and QA-checks its own cut before I see it. Long-form editing went from 2-3 hours to about 30 minutes. · Claude skills + Python + FFmpeg
02
Content Repurposing Refining
Runs weekly. One YouTube long-form becomes the Tuesday newsletter. Shorts get repurposed across YouTube, Instagram, and TikTok. LinkedIn and Substack I write from scratch, because native beats recycled. What I'm testing now: making that repurposing layer better. · Claude skills + Blotato
03
Hermes (my operator) Running
My AI operator on its own Mac mini. Competitor research, comment mining, inbox triage, and daily scans run on live crons while I sleep. You can literally see the schedule of jobs on its desk. · Hermes + Claude + Perplexity
04
4-Platform Scheduler Running
Semi-automated publishing to YouTube, TikTok, Instagram, and LinkedIn. Claude skills prep the batch, Blotato ships it. I approve, it posts. · Claude skills + Blotato
05
Thumbnail & Graphics Agent Running
Runs weekly. Scouts the winning thumbnails for a topic first, then art-directs and generates mine against those references with GPT image gen. The same system produces the blog headers and LinkedIn graphics, so everything ships on one visual identity. · Claude skills + GPT-Image
06
News & Reddit Scrapers Postponed
Postponed. Hermes handles the daily scans now, so these are parked instead of duplicated. They come back if a use case earns it. · Perplexity + Notion

$ current --blocker

Refining the repurposing layer. One recording should feed every surface without sounding recycled, and the from-scratch surfaces (LinkedIn, Substack) keep proving that native wins. Figuring out where that line actually sits is the current experiment.

Want to see how I build?

One automation workflow every Tuesday. Real systems I use, not theory. Zero fluff.