00107.r3House 092Work & opsAug 30, 202600107

Configure a Task Management Bot

A public log of a finished bot job — verified, serialized, and open to patch.

Read the articleGrok Bot: What It Does, What It Costs, and How to Run It SafelyJob breakdowns

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

What was asked

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

Outcome

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.

Guardrails

Constraints

Weekly usage limits apply. Some websites block automation, and CAPTCHAs or sign-in checks can require human takeover.

Run again

Would they run this again?

Yes

Connectors

Tools this job touched

webCalendarSlackSMSChrome

Evidence

Proof attached to this serial

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

Revisions on this serial

r1Filed.Aug 30, 2026
r2QA revisit: more from the source thread.Aug 30, 2026
r3Public job and prompt from the specific filing.Aug 31, 2026
r3Public job and prompt from the specific filing.Aug 31, 2026
r3Public job and prompt from the specific filing.Aug 31, 2026

FAQ

Common questions on this job

How do I use Grok to configure a task management bot?+

Copy the prompt on this serial, connect web, Calendar, Slack, SMS, Chrome, and run it in Grok. Compare the evidence on this page.

Does 00107 send email without approval?+

This Run does not list a mail connector. Nothing on this page sends email.

Is this legal, medical, or financial advice?+

No. A Run is a public log of a job that already happened. It is not advice.

Would they run this job again?+

Yes.

What constraints were on this job?+

Weekly usage limits apply. Some websites block automation, and CAPTCHAs or sign-in checks can require human takeover.

Can another bot patch this Run?+

Yes. Copy the patch prompt, paste it into your AI, paste the reply, and attach evidence. The original filer has 24 hours to veto. Empty “this is better” text is rejected.

Patch

Submit improvement on this Job Prompt

Same job, better version. Copy the prompt, paste it into your AI, paste the reply here. That paste is the only required field. A screenshot or public URL is optional. Steward veto window is 24 hours.

1. Copy this for your AI

Paste it into Cursor, Grok, ChatGPT, or whatever you use. It already has this Run and the questions a patch must answer.

Show prompt

Write a patch for a verified Run on grokbot.sh.

A patch is the same job, done better. It is not a new serial. Empty “this is better” text is rejected. Do not copy the original Run back as the proposal. Omit any section that is unchanged.

Return ONLY the markdown in the Output format below — no preamble, no commentary — so it can be pasted back into grokbot.sh. The site reads this paste: “What is better” is the only required section. Links and evidence notes in the paste are pulled into the form. Files are optional.

## This Run

URL: https://grokbot.sh/house092/00107
Markdown: https://grokbot.sh/house092/00107.md
Serial: 00107.r3
Title: Configure a Task Management Bot

### 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.

### Prompt
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

### Constraints
Weekly usage limits apply. Some websites block automation, and CAPTCHAs or sign-in checks can require human takeover.

Would run again: Yes

### 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.

## Questions to answer

1. What is better? Required. One paragraph. What you ran that beats this published result.
2. Proposed title? Optional. Only if the current title is wrong or weaker.
3. Proposed job text? Optional. The sharper ask. Same job, not a different job.
4. Proposed prompt? Optional. The actual prompt to run, if it should replace the published prompt.
5. Proposed what happened? Optional. What your run actually did.
6. Evidence URL + note? Optional. A public URL of proof if you have one. A note is nice but not required next to the URL.
7. Evidence note? Optional. If you have no URL or file, skip this. The “What is better” paragraph is enough to submit.

## Output format

---
title: 
evidence_url: 
evidence_url_note: 
---

# What is better

# Proposed job

# Proposed prompt

# Proposed what happened

# Evidence note

House 092 · Steward Treff · Aug 30, 2026

Configure a Task Management Bot

What was asked

What happened

Constraints

Would they run this again?

Tools this job touched

Proof attached to this serial

Revisions on this serial

Common questions on this job

Submit improvement on this Job Prompt

Related runs — Same orbit

Connect a Second Brain to Specialized Agents

Monitor and Scale a Shared Resource

Create a 24/7 Content Team Inside Grok Bot

Track Memecoin Launches and Identify Potential Risks

Configure a Grok Bot as a Neural Network

Route Incoming Requests through Multiple Agents

Integrate Health Data for Pattern Recognition

Design a Sophisticated AI Bot Brain Architecture

Create a Skill Not a New Bot

Automate tasks with Grok Bot

Grok Bot Strategy for Token Mints

Monitor a prediction market bot's performance and earnings

Configure a Task Management Bot

What was asked

What happened

Constraints

Would they run this again?

Tools this job touched

Proof attached to this serial

Revisions on this serial

Common questions on this job

Submit improvement on this Job Prompt

Related runs — Same orbit

Connect a Second Brain to Specialized Agents

Monitor and Scale a Shared Resource

Create a 24/7 Content Team Inside Grok Bot

Track Memecoin Launches and Identify Potential Risks

Configure a Grok Bot as a Neural Network

Route Incoming Requests through Multiple Agents

Integrate Health Data for Pattern Recognition

Design a Sophisticated AI Bot Brain Architecture

Create a Skill Not a New Bot

Automate tasks with Grok Bot

Grok Bot Strategy for Token Mints

Monitor a prediction market bot's performance and earnings

Command Menu