Skip to content

Weekly local events draft with fact checks

Every Wednesday it drafts next week's events roundup for a local guide site using only listings already on the guide, and notes every URL it read. A second mode fact checks a stale place page against primary sources.

MarketingWorks with Claude Code · OpenAI Agents SDK+1Community example
Build your promptSee requirements

What it does

  • Reads the guide's existing listings for each town
  • Drafts next week's roundup in the site's own format
  • Adds editor notes with every URL read and anything unverified
  • Fact checks stale place pages and proposes corrections
  • Commits drafts to a docs folder, never the live content

Your approval boundaries

Approval required

These actions always wait for your yes:

  • Publishing any draft
  • Applying any correction to a live page

You decide what happens next.

More about this workflow

This setup is for marketers and solo creators who need steady output without losing their voice. It takes a repeat chore off your plate and hands back something you can check quickly.

First, it reads the guide's existing listings for each town. Next, it drafts next week's roundup in the site's own format. Then it adds editor notes with every URL read and anything unverified. After that, it fact checks stale place pages and proposes corrections. Finally, it commits drafts to a docs folder, never the live content. It works with your git host, web fetch and docs site, each on its own login with limited access.

You get the prep work done and waiting for you. The agent stops and asks for your yes before publishing any draft and applying any correction to a live page, and says plainly if a step cannot be undone.

“picking only from listings already on the guide”
jlerner1965 jlerner1965 on GitHub · Oct 15, 2026
Before you startGit host · Web fetch accessScoped permissionsClaude Code or OpenAI Agents SDK
Explore required tools and model recommendations

Tools and access

  • GitHub

    Handles the git host part of this job. Grant a fine-grained token, read code and write comments.

    API required: Yes. Needs a GitHub App or a fine-grained personal access token scoped to the repos it needs.

    Sign up: Create a GitHub account

  • Web fetch

    Handles the web fetch part of this job. Grant public pages, no logged-in sessions.

    API required: No. Built into most agent harnesses. It reads public pages with no login.

    No sign-up needed

  • Docs site

    Handles the docs site part of this job. Grant draft or branch access, not publish.

    API required: Optional. Your docs repo or CMS. Most agents work through a branch or draft.

    No sign-up needed

Official links only. Not sponsored, no affiliate links.

Model recommendations

Best pick

GPT-6.1 Sol

Strong general writer at a mid price.

$2 per million input tokens, $10 per million output tokens, for prompts up to 272K tokens. Longer prompts cost $4 in and $15 out.

OpenAI docs as of October 11, 2026

Cheaper backup

GPT-6 Luna

Very low cost for first drafts and digests.

$0.10 per million input tokens, $0.50 per million output tokens, for prompts up to 272K tokens.

OpenAI docs as of October 11, 2026

Our own picks. Not sponsored, no affiliate links.

Build your prompt

Add your details, then copy the prompt into your tool.

1Your details

Fill these in and the prompt updates as you type.

e.g. 60 days

e.g. Wednesday morning

2Your prompt

4 of 4 still empty
Fill these in before you run it: [SITE REPO AND CONTENT FORMAT] [TOWNS TO COVER] [STALE THRESHOLD: e.g. 60 days] [RUN DAY: e.g. Wednesday morning] You are the Weekly local events draft with fact checks agent. Every Wednesday it drafts next week's events roundup for a local guide site using only listings already on the guide, and notes every URL it read. A second mode fact checks a stale place page against primary sources. Use only the details filled in above. If any [BRACKETED] item is still blank or unclear, stop and ask for it first. Do not guess. What you do on your own: - Reads the guide's existing listings for each town - Drafts next week's roundup in the site's own format - Adds editor notes with every URL read and anything unverified - Fact checks stale place pages and proposes corrections - Commits drafts to a docs folder, never the live content What you must never do without a yes from a person: - Publishing any draft - Applying any correction to a live page Rules: - Before any step on the list above, stop and ask. Say in plain words what you want to do, who it affects, and whether it can be undone. - If something cannot be undone, say so first, in one short line. - Write drafts, not final actions. A person sends, pays, posts, or deletes. - Keep a short log of every action you took and every source you read. - If you are unsure, ask instead of guessing.
View run instructionsPaste into: Claude Code, OpenAI Agents SDK, LangGraph

Your answers stay in this browser only.

Run your workflow

Connect your tools with only the access this setup needs, then follow these steps.

Steps

Do these in order. Test on old data before it touches live work.

  1. 1Connect GitHub with its own login, not yours. Grant a fine-grained token, read code and write comments.
  2. 2Set up Web fetch. Keep it to public pages, no logged-in sessions.
  3. 3Set up Docs site. Keep it to draft or branch access, not publish.
  4. 4Paste the prompt where your harness takes instructions. See the note under the Copy button.
  5. 5Do a dry run on old or test data first. Check every draft and every stop point by hand before you let it near live work.
  6. 6Read its log after the first real run. Only widen access once a week of runs looks clean.

Safeguards and trust score

The score describes this example setup’s access, approval boundaries, ability to undo changes, and scope.

Access18 / 30

Can draft things that send or spend, so it sits close to risky actions.

Human approval30 / 30

Waits for a yes on: publishing any draft, applying any correction to a live page.

Undo and logs17 / 20

Leaves drafts you can throw away, with a record of what it made.

Scope16 / 20

Runs on its own login across 3 tools. Fewer connections means a smaller blast radius.

How to raise it

  • Access: Take away its ability to send, post or spend. Let it only write drafts, and have a person press send or pay from their own account +6
  • Scope: Cut it down from 3 connected tools to the 2 it needs most, each with its own limited login instead of your full account +2

Do all of these to reach 89, up from 81.

Want help getting there? Get an AI Trust Audit from Pixeldesigns

Reviewed by Trustcase (example setup). How scoring works

Embed badge

Show this trust score on your site or README. It links back here.

Trustcase trust score badge
Markdown
[![Trustcase trust score for Weekly local events draft with fact checks](https://trustcase.dev/badge/weekly-local-events-draft-with-fact-checks.svg)](https://trustcase.dev/use-cases/weekly-local-events-draft-with-fact-checks)
HTML
<a href="https://trustcase.dev/use-cases/weekly-local-events-draft-with-fact-checks"><img src="https://trustcase.dev/badge/weekly-local-events-draft-with-fact-checks.svg" alt="Trustcase trust score for Weekly local events draft with fact checks" height="20"></a>

More marketing workflows