How I Automated My Blog Publishing With Cowork

Every Saturday at 10am, a Cowork task wakes up and drafts a blog deploy.

It syncs my Obsidian vault to my portfolio. Picks up posts dated today or earlier, packages the assets, runs the build check. Then it stops. Waits for me to say go.

That's not a technical limitation. That's the design.

Here's the setup: every LinkedIn post I write lives in Obsidian first, each one front-mattered with a scheduled date. The vault is the source of truth. Saturday morning I get a summary of what's changed, review it once, and confirm. Ten seconds. Then Vercel redeploys, and the same posts I put on LinkedIn are permanently on a site I own.

Three hours to build. Probably twelve hours recovered per month from not manually syncing files, forgetting to push, or publishing something half-finished.

The part I kept manual is the final push to GitHub. Not because I don't trust the script. Because the moment I'm not in the loop on what goes live, publishing stops feeling like something I own. The gate is what makes it mine.

AI does the infrastructure. I do the editorial call. That split matters more than it sounds.

The blog is at rahul-m-shah-portfolio.vercel.app/blog. It's just my LinkedIn posts with a permanent home.

What's one workflow you'd automate but keep a human approval gate on?

Hashtags

#gameproduction #ai #automation #mobilegaming #productmanagement

Related Posts

• Pulled forward from Jul 2 slot. Pairs naturally with the Jun 30 AI coding tools post (both practical AI-workflow posts).