Automated Content Pipeline with Claude Code

The short version: Claude keeps getting confused by Post For Me (the social media API I use for publishing). Every time I asked it to schedule something, it would forget the flow, mix up steps, repeat the same mistakes. So I wrote a 659-line skill file that teaches Claude the entire API, step by step.

That fixed the posting. But I kept building.

I now have three scheduled agents running automatically:

1. An ops sweep every 4 hours that checks my inbox, flags stale drafts, and spots posting gaps
2. A morning briefing at 9am with posting activity, engagement analytics, draft pipeline status, and one priority for the day
3. A weekly strategist on Saturdays with performance analysis, content gaps, and three priorities for next week

None of them auto-post. They suggest. I decide. That turned out to be the right call because the useful automation isn't automatic posting. It's having something review your whole system regularly and tell you what matters right now.

The whole pipeline runs through an Obsidian vault: ideas come in, get processed through stages (develop, polish, humanize, quality check), and Post For Me handles publishing. Each stage has its own Claude Code skill. Published posts get tracked and fed back into the system.

I wrote a full blog post with the complete walkthrough and included the entire 659-line skill file so you can use it yourself.

Blog post: https://www.igorgridel.com/blog/automated-content-pipeline-claude-code-post-for-me

If you have questions about the setup or want to build something similar, drop into the Discord.