OpenClaw publishes blog posts after Telegram review
Nnorukam reports a working blog pipeline that researches opportunities, drafts in his style and deploys an approved post through GitHub and Vercel.
chudi.dev
Original prompt
Shared by the source author. See source notes for context.
GO
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source author
- Chudi Nnorukam
- Original account
- Read the source ↗
- Published
- 20 Feb 2026
- Source link checked
- 15 Oct 2026
- Reported result
- Nnorukam reports a working blog pipeline that researches opportunities, drafts in his style and deploys an approved post through GitHub and Vercel.
- Human involvement
- The author approves topics and publication through Telegram. Build failures stop the publisher and produce an error message.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Read existing posts and Search Console queries to produce a topic brief.
- Draft the approved topic using a style guide and relevant prior articles.
- Send a preview through Telegram and wait for publication approval.
Chudi Nnorukam built an OpenClaw workflow around his existing blog and Google Search Console data. The agent reads writing samples to extract a style guide, monitors queries with improvement opportunities and turns selected topics into content briefs. The author describes using Claude Sonnet behind OpenClaw.
A drafting skill loads the style guide and relevant previous posts, writes a new article and checks its consistency. Telegram carries separate topic and publication decisions. The source includes an example exchange in which the author approves a brief, reviews a preview and replies to publish. Only then does the publishing skill write frontmatter, run the build, commit and push to GitHub for Vercel deployment.
The author reports that this system changed his publishing pace and gives a concrete path from approved topic to live URL. Those observations remain his account, not a measured causal study of traffic growth or search rankings. The build can fail, in which case the publisher reports the error and stops. The useful boundary is that research and drafting can proceed through tools while the author keeps control of what reaches the public site.
Prompt
Original prompt
Source: Blog · Chudi Nnorukam
Frequently asked questions
When does publication happen?
The publisher pushes only after the author replies with publication approval in Telegram.
What happens if the build fails?
The workflow reports the error to the author and stops.
Does this prove improved search rankings?
No. The account describes the workflow and the author’s publishing observations, not a controlled ranking study.
More details
Remaining steps
- Write the content file, build, commit and push for Vercel deployment.
About this account
Read existing posts and Search Console queries to produce a topic brief. Draft the approved topic using a style guide and relevant prior articles.
Firsthand account read. Primary page visibly published 2026-02-20; matching BlogPosting structured date verified. Publishing and cost observations are author reports; no causal search-performance claim. Reported outcomes were not independently reproduced. Original prompt box contains a short excerpt of the author's published instructions.
Credit: Chudi Nnorukam
Source published 20 Feb 2026
Source checked 15 Oct 2026
Tools and topics
OpenClaw · Google Search Console · Telegram · GitHub · Vercel
OpenClaw · Google Search Console · Telegram
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.