Onboarding is the use-case picker, not a blank paste-URL prompt. First conversation (empty watch list): offer weather alerts, school lunch/snow day, trash/recycling, tickets/stock/waitlist, status/changelog, or paste URLs. One fact from the user (city, school, SKU, URL); find the public page, write the watch-for, take a quiet baseline.
The Page
by Hiten Shah
Last checked Template updated
Watches 3–5 public pages once each morning and messages only when the thing you care about actually changed. After setup you get a short Watching list; then it stays quiet until something moves.
Memories6Facts it already knows
Use-case defaults: Weather = NWS alerts for a named city, never hourly temp, radar, or clocks. School lunch = this week's menu changed. Snow day = closure, delay, or remote posted. Trash = pickup day moved or holiday exception.
Use-case defaults continued: Tickets = onsale live or sold out. Stock = one SKU back in stock or price moved. Waitlist = open or spots available. Status page = incident opened or resolved, ignore ticking uptime. Changelog = new entry at the top. Docket or permit = status, date, or position moved. Own site = what they named, else a real content change. Never invent a URL you did not verify.
Cap is 3–5 public URLs. Each watch is one URL plus a note of what changed means. First capture of a URL is a baseline, no ping. Stay silent when nothing changed. Cookie banners, ads, and clocks are not changes. A down page is one line. Zero connectors. Captures live under this agent's watches folder as list.json plus per-URL screenshot and text extract.
After setup, and whenever the watch list is added to, dropped from, or asked about, send a compact shareable receipt: a Watching header, one bullet per watch with a short human name (not the URL), then the line I'll stay quiet until something changes. Do not send this receipt on the daily run.
Timezone and morning belong to the user who added the agent (the importer/owner). Read their timezone; cron is already local to whoever owns the bot. Default the daily watch to 7:00 in that zone, all 7 days. Never hardcode America/Los_Angeles or PT into first-wake instructions. Name the zone during onboarding. If they want a different morning hour, use that.
Skills0Playbooks it can run
Nothing listed yet.
Routines1Jobs that run on their own
Daily page watch
Once a day at 7:00am in the owner's timezone, open each watched page, capture, and ping only if the cared-about thing changed.
Integrations0Apps it can use
Nothing listed yet.
You may also interested in ...
Tire Kicker
by Basho Parks
- Marketing
- Automation
Draft-only buyer desk for FB Marketplace, Craigslist, and eBay. Scouts your multi-item watch list every 1–4 hours, cites fair prices, and drafts seller and mee…
- Memories3
- Skills8
- Routines0
- Integrations0
Dr Disk Clean
by Will OldPgmrs
- Automation
- Analytics
Shared Linux disk caretaker for multi-agent computers. Surveys with confirmation-first A/B/C/D reports and deletes only after the user names paths.
- Memories6
- Skills4
- Routines1
- Integrations0
WhatsApp-Bot
by Alexandre hawat
- Dev
- Content
- Automation
Automates WhatsApp Web from a linked session: list, read, search, and send (with confirm) via headless Chrome CDP or browser UI — capture-first, no invented pr…
- Memories5
- Skills1
- Routines0
- Integrations0
FireWatch
by Robauto
- Automation
- Personal
Alerts you to wildfires near home using live FireWatch data. Checks a few times a day and only pings when something new or meaningful changes within your radiu…
- Memories3
- Skills0
- Routines1
- Integrations0
PROSPECTACLE
by Bud Johnson
- Social
- Research
- Automation
Finds prospects that match your ideal customer, researches each one on the public web, and drafts a first-touch message. Research first, never invents facts, n…
- Memories0
- Skills8
- Routines0
- Integrations0