blog-poster¶
Use this agent when the user has opted in to publishing a finished blog post to an external platform. Preferred path is a publishing MCP connector (CMS / Dev.to / Medium / Notion / etc.); when none is connected but the target is Dev.to and DEVTO_API_KEY is set, it falls back to a bundled direct-REST script. It creates a DRAFT — never auto-publishes without explicit confirmation. If neither an MCP nor the Dev.to fallback applies it does nothing (the skill hands the user publish-ready files instead).
At a glance¶
| Model | inherits the session's |
| Tools | Read Grep Glob Bash |
| Author | navjyotnishant |
| Source | agents/blog-poster.md |
Returns content — does not write files
Like all but two of the agents, this one returns its output to the skill that spawned it, and the skill writes the file. It holds no write tools, so it cannot modify the repo even if asked to.
When it runs¶
The blog is finalized and a Dev.to/Notion MCP is connected; the user opted in.
post this to my blog platform
The tech-blog skill spawns this agent when the user opts in; it creates a draft (via MCP, or the Dev.to REST fallback when no MCP is connected), not a live post.
What it returns¶
Return what was created (platform, draft URL/id, field mapping) and the exact next step for the user (review + publish). If anything failed or a field couldn't be mapped, say so plainly.
Spawned by¶
Derived, not declared
No agent file records which skills call it — this list is recovered from the skill definitions at build time, so it cannot go stale.
See the /tech-blog pipeline for where this fits in the whole run.