Event audit skill + bot QA polish

A reusable checklist skill and a real audit pass that caught bad event data, fixed titles and dates, and kept a static meetup site in sync with its feeds.

@gurungbuilds

web3meetups.xyzvisit ↗

process.log7 fields

toolsGrok (xAI)Python (BeautifulSoupsite helper scripts)Gitt.ly + Luma as data sources

iterationsA few tries

name → audit → fix → title/day polish

time20 minutes

%_ai35

me 65

ai 35

self-reported · generously rounded

# how_it_was_made

questions2

@salmanneedsajob1mo

nice product revamp Gurung! fan of webmeetups.xyz

@gurungbuildscreator1mo

I appreciate the kind words, Salman!

@salmanneedsajob1mo

curious - does event entered into the web3meetups goes through this QA bot? or is it something you invoke on-demand?

@gurungbuildscreator1mo

i invoke it on demand. i have a workflow for it with scripts!

ask about the process…sign in

~/slopfolio··

did a light audit with deep checks only on what the bot added that day. The AI pulled remote, verified structure and derived JSON, unfurled short links, and compared dates to source pages. I chose what to keep (drop a 2027 tour stop, shorten titles, full weekday names). We encoded those rules in the skill and workflows so the next run stays consistent.

// best_dead_end

Treating “2 Jan” as a past event looked right until Luma showed 2027 — the yearless calendar made a future stop look expired. That forced an explicit product call, not a blind auto-delete.

# prompting_approach

Did a clear run mode (light everywhere, deep on today’s bot adds). Follow-ups were one concern at a time: fix findings, polish titles, long-form days, commit/push when ready.

~/slopfolio · the work + how it was made

see what's inside → ~/explore get an invite