Verified Grok Bot Job · Research · House 288

r3House 28800518.r3Aug 26, 2026

Configure a Grok Bot to Automate Laser Engraving and Card Creation

JSON· Markdown· House 288 · scouted on x · Steward Rich Silver · Music, Art video creator · QA Enriched

Job

Configure a bot to access and control a laser engraver, load software, and create custom business cards using a USB instruction manual and online research

Connectors

web, SMS

What happened

One person gave a bot access to their laser engraver and instructed it to create custom business cards. The bot set up the engraver, loaded software, and created the cards without direct human input. The user hit a usage limit and was unable to use the bot for 7 days, despite having a paid subscription.

Constraints

Grok Bot usage limits; exact reset schedule unpublished; cannot see detailed per-action usage log

Would run again

Yes

Evidence

https://x.com/RichSilver/status/2092099610730791263 — Imported from the X thread tagged for @tryreallybot.

https://x.com/RichSilver/status/2091971316547010787 — Pulled on QA revisit of the source thread.

Changelog

r1: Filed. (Aug 26, 2026)
r2: QA revisit: more from the source thread. (Aug 26, 2026)
r3: Public job and prompt from the specific filing. (Aug 26, 2026)

Also: /takes

FAQ

How do I use Grok to configure a grok bot to automate laser engraving and card creation?

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

Does 00518 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?

Grok Bot usage limits; exact reset schedule unpublished; cannot see detailed per-action usage log

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 this Run

Same job, better version. Copy the prompt, paste it into your AI, paste the reply, attach evidence. 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 really.bot.

A patch is the same job, done better, with evidence. 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 really.bot.

## This Run

URL: https://really.bot/house288/00518
Markdown: https://really.bot/house288/00518.md
Serial: 00518.r3
Title: Configure a Grok Bot to Automate Laser Engraving and Card Creation

### Job
Configure a bot to access and control a laser engraver, load software, and create custom business cards using a USB instruction manual and online research

### Connectors
web, SMS

### What happened
One person gave a bot access to their laser engraver and instructed it to create custom business cards. The bot set up the engraver, loaded software, and created the cards without direct human input. The user hit a usage limit and was unable to use the bot for 7 days, despite having a paid subscription.

### Prompt
Configure a bot to automate the setup and operation of a laser engraver, using a USB instruction manual and online research to create custom business cards and products

### Constraints
Grok Bot usage limits; exact reset schedule unpublished; cannot see detailed per-action usage log

Would run again: Yes

### Changelog
- r1: Filed.
- r2: QA revisit: more from the source thread.
- r3: Public job and prompt from the specific filing.

## Questions to answer

1. What is better? Required. One paragraph, tied to the evidence. 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 here. A public URL of proof, plus one sentence on what it proves. You can also attach files on the site.
7. Evidence note? Optional. If the screenshot stays private, describe what it showed. Redact PII.

## Output format

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

# What is better

# Proposed job

# Proposed prompt

# Proposed what happened

# Evidence note