Grokbot Templates
All use cases

Engineering

Fill the permit pack, then stop for review

Read pack, type Word templates, stamp, combine PDF — about an hour each.

Share

What hurt

CivilSiteAI issues permits in a day job. The slow part was the same every time: read the pack, pull names, dates, and addresses, type them into Word templates, stamp the cover, combine the PDF. About an hour each. Python on the Grok Bot cloud computer now builds the Word files, stamps the cover, and combines the PDF. There is a human review gate at the end of each stage. The author still reviews what the bot built.

What to install or create

One bot on the shared computer. Paste the published workflow as the brief. Upload one permit pack. Extract fields, fill templates, stop for review before stamp, stop again before combine. Do not file, submit, or email the permit.

Bots

  • Permit clerk

    Extract, fill, stamp, combine — stop for review at each stage.

Plugins

  • None on day one. Paste the prompt and run the first task.

Files

  • One permit pack plus the owner’s Word templates on the shared computer.

Routines

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

The prompt

Paste as the workflow brief

CivilSiteAI posted this workflow in the cited tweet. Copied as published.

Last line is our approval fence: Never send, post, spend, or buy without my explicit yes.

In my 9-5 I issue permits. The slow part used to be the same every time. Read the pack. Pull out names, dates, and addresses. Type them into Word templates. Stamp the cover. Combine the PDF. About an hour each.

Grok Bot and Python on its cloud computer now do that repetitive bit. I have Python scripts that build the Word files from templates using data Grok pulled out, and scripts that stamp the cover and combine the final PDF. There is a human review gate at the end of each stage of the workflow. I review what Grok Bot built, so I still have full control of the output.

I can get through two or three in about one hour. Same review. That used to take at least an hour for one permit. Less copy-paste. I rarely touch the keyboard now. I do the whole workflow from my phone, in the Grok Bot app.

Never send, post, spend, or buy without my explicit yes.

First run

  1. 1Upload one permit pack and point the bot at your Word templates.
  2. 2Ask it to extract names, dates, and addresses. Review the fields.
  3. 3Let it fill the templates. Stop for review before any stamp.
  4. 4Stop again for review before it combines the PDF.
  5. 5Do not file, submit, or email the permit.

Approval fence

No filing, no email to applicants, no stamp of a real official seal unless the owner’s own template is used. Review gate at every stage.

What to tweak

Steal the stage gates, not a real seal. Use the owner’s own Word templates. Do not stamp a real official seal unless that template is yours. Review at every stage. Throughput claims stay with the author.

Source

CivilConstruct AI @CivilSiteAI · Original post

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

Browse templates

Browse team blueprints