All use cases

Engineering

Tip: end every polling routine with a stop condition

Zombie shipping checks quietly burn your weekly usage after delivery.

Share

What hurt

nick (@thecsguy) tip after Elon's Lego delivery story: end every polling ask with a stop condition like "check daily until it's delivered, then delete this routine" so dead checks don't eat weekly usage. Optional: a bot that manages zombie routines for you. Not affiliated with xAI.

What to install or create

Edit existing poll routines. Add stop + delete. Tip only.

Bots

  • Any polling bot

    Every poll ends with stop + self-delete.

Plugins

  • None on day one. Follow the first-run steps.

Routines

  • None on the first run. Watch one manual pass first.

The prompt

This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.

First run

  1. 1Read https://x.com/thecsguy/status/2110146834610213172 (credit @thecsguy).
  2. 2List routines that poll (shipping, status, price).
  3. 3Rewrite each ask to include a stop condition and "then delete this routine".
  4. 4Optional: ask a desk bot to find routines with no stop condition.
  5. 5Confirm one finished poll actually deleted itself.

Approval fence

Routines may delete only themselves when the stop condition is met.

What to tweak

Steal stop-condition → self-delete. Kill zombies before they meter you.

Source

nick @thecsguy · Original post

Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.

Browse templates

Browse team blueprints

Pro pack

Want the full setup, not just the idea?

Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.

See Pro