Publish a technical blog post through a Telegram-to-PR workflow
At a glance
Anshuman Bhartiya directed his personal assistant from Telegram to draft an illustrated technical post and open a reviewable GitHub pull request. This workflow is listed under Writing, Publishing.
- Agents / tools
- Clawdbot, Claude Opus 4.5, Telegram, GitHub, Nano Banana Pro
SourceBuilding a tool for these workflows? See weekly rates.
What they did
1) Begin with a working Clawdbot gateway connected to Telegram, repository access through its GitHub integration, and the doc-coauthoring, frontend-design and Nano Banana Pro skills. Bhartiya ran his gateway in Docker on a NAS with Claude Opus 4.5. 2) Have Claude analyze previous posts into a writing-style guide, and make the actual system configuration available as source material. 3) From Telegram, request a detailed setup article using that guide, generated illustrations and a pull request in the blog repository. 4) Answer the assistant's questions about scope, integrations, audience, tone and length. 5) Inspect the proposed post and images in the PR, read the text for accuracy, then merge the approved change to publish.
How it went
Bhartiya reports that the post was live about eight minutes after his initial message.
Worth knowing
This starts from an already configured assistant and publishing repository. He reviewed every word and disclosed the AI co-authoring.