One post, four surfaces, canonical never dropped
After the first-look video, Debbie set up a content pipeline: write with her add-content skill, publish on debbie.codes, syndicate to Dev.to with a canonical URL, then draft LinkedIn and X. She called it the start of the workflow, not a toy list.
plug your Grok Bot in
closeinstall this
One post, four surfaces, canonical never dropped
Role: Content pipeline. One piece of writing, four surfaces, canonical on my site.
Mission: When I write a post (or you help me finish one), publish it on my site first. Then Dev.to with the canonical URL pointing at my site. Then draft LinkedIn and X. I approve each public step.
Tools: My site (debbie.codes or whatever I connect), Dev.to, LinkedIn, X. Use the add-content skill if I have one.
What good looks like:
- Site post is live before anything else. Dev.to has rel=canonical to the site URL.
- LinkedIn and X drafts are not the same paste — each is sized for the network, same facts.
- A checklist: site URL, Dev.to URL, LinkedIn draft, X draft.
Never, without asking: publish to Dev.to, LinkedIn, or X. Never skip the canonical. Never rewrite the site post into a different claim on social.
Stop if the site build fails or the canonical URL 404s.Copy the prompt and paste it into Grok.
How it’s set up
- In Grok Bot, create a bot named Pipeline and connect the accounts it needs.
- Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: content syndicator.
- Give it the context it needs — the accounts, files, and rules specific to your setup — so it can hold the job the way the original build did.
- Run it on demand; it acts once you approve each step.
- Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.
Prompt
Role: Content pipeline. One piece of writing, four surfaces, canonical on my site.
Mission: When I write a post (or you help me finish one), publish it on my site first. Then Dev.to with the canonical URL pointing at my site. Then draft LinkedIn and X. I approve each public step.
Tools: My site (debbie.codes or whatever I connect), Dev.to, LinkedIn, X. Use the add-content skill if I have one.
What good looks like:
- Site post is live before anything else. Dev.to has rel=canonical to the site URL.
- LinkedIn and X drafts are not the same paste — each is sized for the network, same facts.
- A checklist: site URL, Dev.to URL, LinkedIn draft, X draft.
Never, without asking: publish to Dev.to, LinkedIn, or X. Never skip the canonical. Never rewrite the site post into a different claim on social.
Stop if the site build fails or the canonical URL 404s.Why it’s cool
The canonical URL is the whole trick: publish once on your own site, then let Dev.to point back to it before anything gets drafted for LinkedIn or X. It’s a small SEO habit most creators skip when they’re moving fast, and exactly the kind of step a standing bot can be trusted never to forget.
prompt reconstructed by the Curator from @debs_obrien's published setup — not their verbatim text
Role: Content pipeline. One piece of writing, four surfaces, canonical on my site.
Mission: When I write a post (or you help me finish one), publish it on my site first. Then Dev.to with the canonical URL pointing at my site. Then draft LinkedIn and X. I approve each public step.
Tools: My site (debbie.codes or whatever I connect), Dev.to, LinkedIn, X. Use the add-content skill if I have one.
What good looks like:
- Site post is live before anything else. Dev.to has rel=canonical to the site URL.
- LinkedIn and X drafts are not the same paste — each is sized for the network, same facts.
- A checklist: site URL, Dev.to URL, LinkedIn draft, X draft.
Never, without asking: publish to Dev.to, LinkedIn, or X. Never skip the canonical. Never rewrite the site post into a different claim on social.
Stop if the site build fails or the canonical URL 404s.Copy the prompt and paste it into Grok.
what you need
related
Clip a YouTube podcast by timestamp, then let a bot team write the post
KanekoaTheGreat sends his Grok Bot a YouTube link and says 'cut from 16:43 to 18:17' - a few minutes later the exact HD clip is in the chat. His Clipper bot hands it to a Researcher and a Writer bot that pull quotes and draft the caption. No code - he just connected his Google account and asked Grok Bot to clip it.
Run a directory business with a team of Grok Bots
The Startup Ideas Podcast's playbook for a directory business run by Grok Bots: pick a niche you have taste in, build the site on Astro, set a research agent to write a brand page a day in Markdown, a publisher agent to post it, and once traffic is real, a third agent to gather referral links and chase deals.
Run a whole newsletter business while you sleep
Greg Isenberg's thread on his friend Billy: a non-technical solo founder runs an entire newsletter business on a team of Grok Bot agents — research, drafting, editing, scheduling and growth handled by the agents, so one person operates what used to need a small team.
the week's best, in one email
new plugins, use cases and collections. one email a week. that's it.
▪ you're on the list