Turn new WordPress posts into engaging X threads

Build me an agent that turns every newly published WordPress blog post into a tailored X (Twitter) thread.

Trigger: run on an hourly cron. On each run, the agent should track the timestamp of the last successful run and only act on WordPress posts published since then. On the very first run, use the last 60 minutes as the window.

Step 1. Call WordPress List Posts filtered to status "publish" and the published-after timestamp from the previous run. Page through results if there is more than one new post. For each post, also call WordPress Retrieve a Post to make sure you have the full title, excerpt, and rendered content.

Step 2. For each new post, draft a thread that follows these rules:

- 4 to 7 tweets total.

- The opening tweet is the hook. Pick a vivid pull-quote, a surprising stat, or a sharp claim from the article. Do not restate the article title.

- Break the rest of the argument into bite-sized points, one idea per tweet, each under 280 characters.

- The final tweet closes with a one-line takeaway and a link to the full article.

- Use one or two relevant hashtags only when they fit naturally. Skip hashtags entirely if nothing fits.

- Never use em dashes. Use periods or commas instead.

- Do not invent quotes, statistics, or facts. Only use material that actually appears in the article.

Step 3. Post the thread. Call X Create Tweet for the opening tweet. Capture the returned tweet id, then call X Create Tweet again for tweet 2 with in_reply_to_tweet_id set to that id. Chain each subsequent tweet as a reply to the one before it so the thread renders cleanly top to bottom.

Step 4. Remember which WordPress post ids have already been threaded so the agent never threads the same article twice, even if the cron overlaps or the published-after window is slightly off.

Voice: confident, plain-spoken, lightly conversational. Sound like a smart human who actually read the article, not a press release. No hype words like "unlock," "game-changer," or "revolutionize." No corporate clichés.

If no new posts are found on a run, do nothing and exit cleanly. If X returns a rate-limit error, back off and pick up on the next run.