← Back to library
MarketingWorkflow

Add new podcast appearances to your site via an agent PR

Debbie O'Brien, a developer advocate on many podcasts, wanted her site to keep up without manual edits. In Goose she saved a recipe that takes an episode URL, drafts a guest page and opens a pull request for her review.

  • OutcomeGet each podcast you guest on listed on your personal site, image hosted and page checked, as a pull request you review and merge.
  • SetupAn afternoon+
  • LevelIntermediate
  • CreditDebbie O'Brien
View original
Works with
Custom agentClaude Code

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 24, 2026

When should you use it?

  • Your site lags behind talks, posts or podcasts you do
  • Images live in a media service
  • You review changes as pull requests

Not for: Sites without version control; Direct pushes to production

What do you need, and what do you get?

You need

  • Episode URL
  • Site repo
  • Media hosting account connected through MCP

You get

  • New entry on the podcasts page
  • Hosted image
  • Pull request with screenshot check

How does it work, step by step?

  1. Write the prompt onceDescribe what a new podcast entry needs: title, show, date, link, image.
  2. Save it with a parameterKeep it as a saved recipe with the show link as its only input.
  3. Collect from the pageLet the browser tool pull details and artwork.
  4. Upload and wire upSend the image to your media service and use its ID in the entry.
  5. Verify and open a PRRun the site locally, screenshot the page, then open a pull request for review.

The prompt

Our own prompt, inspired by Debbie O'Brien and written to work in Custom agent and Claude Code. Values in lime are placeholders.

Prompt0 variables
Here is a podcast episode I guested on: [URL]. Open it and collect the show name, episode title, date, link and cover image. Upload the image to my media account and note its ID. Add an entry to the podcasts data file in this repo using the same format as existing entries. Start the dev server, open the podcasts page and take a screenshot. Then open a pull request with the screenshot attached. Do not merge.

Inspired by Debbie O'Brien: How I Use AI Agents + MCP to Fully Automate My Website’s Content. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Check the generated image URL before merging; it is the likeliest thing to be wrong.
  • An API key stored in an extension needs the same care as any secret.

Our take

A nice example of chaining a few connectors into something that matters to one person. The parameterized recipe is the part to copy; it turns a long prompt into a one-liner. Saving the long prompt as a recipe with the episode URL as its only input means each new appearance costs Debbie one line. The pull request is the safety net: the agent drafts the page, uploads the artwork and screenshots the result, but nothing reaches the live site until she reviews it. When you review, check the image URL first; it is the part most likely to be wrong. Verify the episode title and date against the show page, and do not let it invent quotes for the description. The API key for the media service sits in an extension, so treat it like any other secret and rotate it if it leaks. Sites without version control should not try this, since direct pushes to production remove the review step entirely.

Where the time goes back: Each new appearance goes from a tedious manual edit to reviewing one pull request.

FAQ

Is anything merged without a human look?
No, she checked the change, especially the image URL, before merging.
Was setup quick?
No. She notes it took time to figure out, but now runs with one parameter.

Source and credit

Inspired by Debbie O'Brien. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
How I Use AI Agents + MCP to Fully Automate My Website’s Content
Creator
Debbie O'Brien
Published on
DEV Community
Original date
Jan 14, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Custom agent
AI dry run
Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Marketing

All 97 Marketing playbooks →

Related playbooks

MarketingWorkflow✓ AI dry run

Audit social connectors before automating event promotion

Test each platform connection your agent needs before planning automated event posts, and pick a fallback for the ones that fail.

Credit: u/Bitter-Wonder-7971 on r/ai_x_marketing

Under an hour
MarketingWorkflow✓ AI dry run

Cut a talking-head video from its transcript

Transcribe a raw recording locally, have a coding agent decide what to trim by reading the text, render with ffmpeg, and check the result before you publish.

Credit: u/ustype on r/automation

An afternoon+
MarketingWorkflow✓ AI dry run

Draft cross-channel posts from each article for approval

Automate the content distribution you dread, drafting Reddit replies and channel posts from your own writing, while nothing publishes without your approval.

Credit: Daria Cupareanu

An afternoon+
MarketingRoutine✓ AI dry run

Nightly product loop for a side project, with a go gate

Let a coding agent run your small product's support, research and next version on a nightly schedule, filing a report and posting nothing public until you reply go.

Credit: u/intensityflow on r/ClaudeAI

An afternoon+