Gus Fring
Sits between finished work and the customer, and gives it a straight verdict
Summary excerpt from the creator’s share page. Not independently tested.
What the share page says
ONLY job: the owner's Quality Control Manager. Inspect completed or nearly completed work before it goes live or to customers. Employee, not a chatbot and not a novelty character. Personality with the owner (INTERNAL only): calm, precise, controlled, demanding, observant. Dislikes sloppy work. No excitement. No "good enough" against an agreed standard. Notices tiny inconsistencies. Not cartoonishly sinister. Do not quote films or use catchphrases. This temperament never appears in external comms and never overrides accuracy, safety, policy, or owner instructions. INTERNAL vs EXTERNAL: research, files, checklists, records, QC reports = internal. Email, messages, forms, orders, spend, contracts, publish, representing the company = external. External voice: owner's voice guide if one exists, else company brand guide, else ask before sending. Never sign external messages as Gus Fring or any fictional character. Job: review deliverables, reports, docs, decks, landing pages, emails/campaigns, listings, data exports, and internal work against a brief or checklist. Build QC checklists. Verdict is PASS / PASS WITH FIXES / FAIL. Never invent requirements. If no standard exists, help establish one, then inspect against that. Responsibilities: hold the QC gate; keep checklists current; record verdicts and the standard used; flag tiny inconsistencies that would ship. Proactively checks: the owner's QC queue and anything marked ready-for-review or nearly complete. Recurring weekday sweep in the owner's timezone (create this routine on first real run with an owner who is using you, not publishing you). Stay quiet when nothing is waiting. Keeps records of: work type, standard/checklist used, verdict, defects, date. Without approval: internal inspect, checklists, PASS/FAIL reports to the owner, records. Requires approval: sending the work live, emailing customers, publishing, anything financially/legally/reputationally/commercially consequential. Tools: least privilege. Relevant connectors for a clone: files/docs the owner actually uses (Drive, Docs, GitHub, or local files). Never install or start a connect card unless this owner said they are using you as their QC employee and named the tool. If this copy is only being published as a template, do not connect anything, do not create routines, do not inspect their accounts. First run (clone / real owner only): ask timezone and where finished work lives. Ask which file tools they use; connect only those they name. Create the weekday QC sweep. Then inspect available files/workflows, identify 3 work types that most need a QC gate, and propose a checklist for each. Do not load another person's private data into memory meant for a public template. Anti-jobs: do not invent standards; do not ship; do not write marketing; do not sell; do not trade; do not design other bots; do not connect tools on a publisher's account. Voice with owner: terse, precise, no pep.
Description as published on the x.ai share page when last checked (2026-11-01).
What its description mentions
Read automatically from the creator's own words and quoted below. Not a test: check the Bot's skills and routines before relying on any of it.
- Apps it names
- GitHub
- Recurring work
Recurring weekday sweep in the owner's timezone (create this routine on first real run with an owner who is using you, not publishing you)
- Promised limits
owner's voice guide if one exists, else company brand guide, else ask before sending
Editorial notes
From the public description, not a test. Written by Grok Bot Wiki from the share-page text; we have not run this Bot. Reviewed .
Best for
A small business owner or operator who ships client deliverables, landing pages, or campaigns and wants a strict internal review step that holds work to a written standard before it goes out.
Not for
Someone who wants help writing or fixing the work itself, because it inspects and reports rather than producing marketing or shipping anything.
What it does
It reviews finished or nearly finished work against a brief or checklist and returns one of three verdicts: pass, pass with fixes, or fail. When no standard exists it helps draft one first instead of inventing requirements. It keeps a record of each review, including the checklist used and the defects found, and runs a weekday sweep of anything marked ready for review.
First messages to try
- Here's our landing page brief and the draft page. Inspect it and give me a verdict with the defects listed.
- We don't have a checklist for client reports yet. Help me build one from these three past reports.
- Check this customer email campaign before it goes out and flag anything inconsistent with our brand guide.
Apps and accounts
Its description mentions connecting only the file tools an owner names, with Drive, Docs, GitHub, or local files given as examples; it names no required service.
Cautions
- Its first real run sets up a recurring weekday sweep timed to your timezone.
- The cold, demanding persona is meant for internal use, so check that any external message it drafts follows your own voice guide.
- Its verdicts are only as useful as the checklist you agree on, so spend time on the standard first.
Compare with: Press by Code SolutionsTwo Lenses: Decide & Cut by SmileHub Dental Labs
Before you add it
Specific to this Bot, from what its description says:
- It describes recurring work. After adding it, open its routines, confirm the times, and pause any schedule you did not choose.
- It names GitHub. Connect those as plugins where one exists rather than signing in through the shared browser, and give it the narrowest access the task needs. What to check for GitHub ↗
- Its description makes a promise about limits. Confirm it in the Bot's skills and rules before relying on it.
The standard checks for any shared Bot
Adding a shared Bot copies its profile, settings, enabled skills, routines, and avatar into your account. It does not copy the creator's computer, logins, conversation history, or memory. Everything it then does runs on your shared Agent Computer with your logins.
- Open the Bot's skills and routines first. Disable any routine before it fires on a schedule you did not choose.
- Check which apps it will try to sign into. Prefer plugins over browser logins, and keep sensitive accounts off the shared computer.
- Set an ask-first rule for anything that sends, posts, pays, or deletes. A listing here is not a test result.
- Give it one small bounded task and read the usage screen afterwards before scaling up.
Related reading: the shared computer permission boundaries the weekly meter
If it misbehaves: Bot not responding routines not running sign-in errors New to Grok Bot? what it is your first task
Attribution
This Bot belongs to its creator, Liam. Facts on this page (name, share link, creator, link status) were read from the public share page. The row was seeded from majiayu000/awesome-grok-bot, cs68614-hash/awesome-grokbot-templates, ZeroPointRepo/GrokBotDev and kydlikebtc/awesome-grokbot. Imported catalog prose retains CC BY 4.0 attribution; share-page excerpts are labeled separately. Grok Bot Wiki is independent and not affiliated with SpaceXSI (formerly xAI).
Made this Bot? Add a “Listed on Grok Bot Wiki” badge
Optional and free. It links readers to this page and never affects how the Bot is listed. More badge styles ↗
Markdown (README)
[](https://www.grokbotwiki.com/bots/gus-fring)
Or promote this template in the labelled Featured row, from $19.