A blank editor and a deadline is where most content calendars stall. Feed this a few keywords and it returns a full draft: outline, headings, body, and the SEO fields WordPress expects.
sonnet4 daysOpenAIWordPress REST APISERP APIn8n
Claude
74ROI
80Scale
$2.3k89Saved
ROI for
README.md
Why this subagent
A blank editor and a deadline is where most content calendars stall. Feed this a few keywords and it returns a full draft: outline, headings, body, and the SEO fields WordPress expects.
It checks what already ranks, writes section by section, and lands the post in your dashboard as a pending draft. You review and publish; you never start from an empty page.
How it runs
Used at step 01 to kick off the pipeline.
Write
Used at step 01 to kick off the pipeline.
WebFetch
Used at step 01 to kick off the pipeline.
WebSearch
Used at step 01 to kick off the pipeline.
Draft an outline with H2 and H3 headings, then write each section against that structure.
pending
Generate a meta title, slug, and excerpt that fit WordPress SEO fields.
pending
Push the finished draft into WordPress as a pending post for a human to review and publish.
pending
Sample output
json
// Sample output
// (generated when the pipeline finishes)
Write a complete blog post from the given keywords; return JSON with title, slug, excerpt, and HTML body.
Unlock the rest
The full agent definition, install snippet, and starter task are gated for community members.
Members get the full `.md` agent file, the npm / pnpm install one-liners, a starter prompt that we've tuned against real runs, and the open-source repo when this automation ships there. One email, magic link, done.