Claude keeps getting confused by Post For Me.
Every time I ask it to schedule something, it forgets the flow. Mixes up steps. Makes the same mistakes on repeat. The API itself is good, the docs are clear, but Claude cannot hold the whole workflow in its head across conversations.
This is the part of AI automation nobody warns you about. The AI works. The tool works. The connection between them doesn't exist, and you have to build it yourself.
So I did.
I wrote a 659-line skill file that teaches Claude the full Post For Me API. How to list accounts, check for duplicates before posting, handle platform differences between X, Threads, and Instagram, verify that posts actually went through, and deal with errors when they don't.
Post For Me is a social media posting API by Matt Roth and Caleb Panza. One SDK that publishes to X, Threads, Instagram, TikTok, LinkedIn, YouTube, and more. The tool is genuinely good and inexpensive. The problem was never the API. It was that Claude had no reliable reference for how to use it correctly.
The skill solved that. Claude reads it before every posting interaction and stopped making mistakes.
But the skill turned out to be just one piece of something bigger.
The automation stack
I now have three agents running on a schedule through Claude Code. None of them auto-post. They suggest, I decide.
An ops sweep runs every four hours. It checks my Obsidian inbox for unprocessed items, flags stale drafts, and spots posting gaps. One suggestion, max 100 words. Quick desk check, nothing more.
A morning briefing runs at 9am. Full daily review: yesterday's posting activity, engagement analytics pulled from Post For Me, inbox status, draft pipeline, platform balance, Patreon status, and one priority for today.
A weekly strategist runs Saturday mornings. Deep review: best and worst posts with pattern analysis, content gaps, video ideas from top performers, project recaps, three priorities for next week.
The pattern is the same for all three. Look at the system, surface what matters, suggest one thing. No auto-posting, no autonomous decisions. I spent time thinking about full automation and realized what I actually wanted wasn't "post for me automatically." It was "review everything and tell me what matters right now."
That turned out to be far more useful.
How it all connects
Everything runs through an Obsidian vault. Ideas get captured in the inbox from voice notes, text dumps, screenshots, conversations. They get processed and routed. Developed into post options. Polished. Humanized if they still sound flat. Run through a quality check. Then Post For Me handles the publishing.
Each stage has its own Claude Code skill. One turns raw ideas into post options. One polishes drafts. One fixes robotic-sounding text. The Post For Me skill handles the final step.
Published posts get tracked. Performance gets reviewed by the agents. Top performers get analyzed and fed back into the system. It loops.
The Obsidian vault is the operating system. The skills are the tools. The agents are the assistants that keep checking the system without being asked.
What I learned building this
Build the skill first. Before the agents, before the pipeline. The skill is what makes the posting step reliable, and that's the step where everything used to break.
A skill isn't code. It's a markdown document that Claude reads before it acts. I was surprised how well that works. You write down the exact steps, the edge cases, the mistakes to avoid, and Claude follows them. No plugin, no extension, just a text file.
The ops sweep is the agent I use most. Every four hours, a quick check on the whole system. That rhythm is what keeps things moving without me having to remember anything.
The full Post For Me skill
The complete 659-line skill file is available for download. If you're using Claude Code, save it as SKILL.md in your .claude/skills/post-for-me/ folder and it works immediately.
Download the Post For Me skill file
If you build something similar or want to talk through the setup, I'm on Patreon. There's also a Discord, but getting access is part of the game. It's not as simple as clicking a link.
Originally published on Igor Gridel. Follow me for more on AI workflows and automation.
Top comments (0)