# 00107.r3 — Configure a Task Management Bot
Revision: r3
Steward: [Treff](https://x.com/0xTreff)
Who: Researcher, Hunter
House: 092
House: 092
Verified: 2026-08-30T12:04:46.161Z
## Prompt (copy into Grok)
1. Collect the exact accounts, folders, websites, and source material to be processed. 2. Define the exact output and destination of the bot. 3. Set stop rules and run the task manually until the result is reliable. 4. Save the working method as a skill and add a routine after the manual process holds up. 5. Add a specialist when a recurring task creates a backlog. 6. Use human takeover for passwords, 2FA, passkeys, CAPTCHAs, and payment confirmation. 7. Connect service accounts with the minimum permissions required and revoke access when the job ends. 8. Remove secrets and private details before sharing the bot. 9. Use the following framework for every job: MISSION: One measurable job INPUTS: Exact accounts, folders, websites, and source material OUTPUT: Required artifact and destination SUCCESS CHECK: Facts, format, and acceptance criteria LIMITS: Time, usage, spending, permissions, and excluded locations APPROVAL REQUIRED: Actions that must stop for your decision RUN REPORT: Actions taken, changes made, failures, sources, and pending decisions
## Job
1. Collect the exact accounts, folders, websites, and source material to be processed. 2. Define the exact output and destination of the bot. 3. Set stop rules and run the task manually until the result is reliable. 4. Save the working method as a skill and add a routine after the manual process holds up. 5. Add a specialist when a recurring task creates a backlog. 6. Use human takeover for passwords, 2FA, passkeys, CAPTCHAs, and payment confirmation. 7. Connect service accounts with the minimum permissions required and revoke access when the job ends. 8. Remove secrets and private details before sharing the bot. 9. Use the following framework for every job: MISSION: One measurable job INPUTS: Exact accounts, folders, websites, and source material OUTPUT: Required artifact and destination SUCCESS CHECK: Facts, format, and acceptance criteria LIMITS: Time, usage, spending, permissions, and excluded locations APPROVAL REQUIRED: Actions that must stop for your decision RUN REPORT: Actions taken, changes made, failures, sources, and pending decisions
## Connectors
web, Calendar, Slack, SMS, Chrome
## What happened
Treff configured a Grok Bot to receive requests, keep a priority list, route tasks to specialists, and return decisions using a persistent cloud computer, and set up human takeover for CAPTCHAs and payment confirmations.
## Constraints
Weekly usage limits apply. Some websites block automation, and CAPTCHAs or sign-in checks can require human takeover.
Would run again: yes
## Evidence
- https://x.com/0xTreff/status/2094033421261525165 — Imported from the X post tagged for @grokbotsh.
- https://x.com/0xTreff/status/2092653736397054040 — Pulled on QA revisit of the source thread.
## Changelog
- r1: Filed.
- r2: QA revisit: more from the source thread.
- r3: Public job and prompt from the specific filing.
- r3: Public job and prompt from the specific filing.
- r3: Public job and prompt from the specific filing.