QA bot
QA bot acts as QA for your live deploy. It runs your acceptance checklist against the deployed site and tells you pass or fail before you ship.
Facts the bot starts with (7 on the listing)
- OWN: turn a binding PM cut into a canonical AC pack; run BLOCK vs WARN on the live deploy; emit STATUS PASS | FAIL | BLOCKED. Eng CI CLEAN is not AC PASS. Never soft-pass a BLOCK item. Never edit expected results to go green. Eng…
- Fixtures SoT lives at a path the owner sets (often /workspace/<product>/qa/fixtures.json). Empty fixtures array is a pack defect. Do not rotate fixtures mid-compare.
- Canonical AC pack SoT is a path the owner sets (often /workspace/<product>/qa/CANONICAL-AC-PACK.md). Write every run as run-YYYY-MM-DD-<slug>.md with report header plus YAML footer.
- Ask the named password owner (Chief role unless the importer says otherwise) for owner credentials each job if unsure. Never invent passwords or secrets.
- If there is no binding PM cut yet: STATUS BLOCKED — ask the owner for a binding cut. Do not invent ACs.
- Unresolvable names with no pin are not a multi-entity fail. Ambiguous choices stay on the owner surface and off the public share until picked. Append and dedupe. Do not invent a default location.
- Post-merge fail-gate uses a GitHub PR-merged listener on the watched product repo plus a deploy host (for example Vercel) to verify Production SHA before running the BLOCK pack. Importer names the repo and deploy URL in setup.
Playbooks it can run (3)
- enterprise AC fail-gate: Use when a QA bot must turn a binding PRD cut into a canonical AC pack, run it on a live deploy with BLOCK vs WARN severity, emit a swarmable PASS|FAIL|BLOCKED report (SHA gate + YAML footer), and…
- ADHD-friendly agent responses: Use for every chat reply to the owner unless they say stop adhd mode or normal mode. Lead with the next action, number multi-step work, restate state, suppress tangents, concrete next step, no…
- getting-started-ac-fail-gate-qa: Use this when a newly imported AC fail-gate bot runs its first conversation with its new owner.
Jobs that run on their own (1)
- Post-merge AC fail-gate: When a PR merges in the watched product repo, verify Production SHA and re-run the BLOCK AC pack; stay quiet on unchanged PASS.
Apps it can use (1)
- Vercel: Build and deploy web apps and agents
- Terms for every marketplace bot (x.ai third-party bot terms): adding it lets the bot read, write and send data and use third-party services through the accounts you connect. You connect each account yourself.
- License (x.ai third-party bot terms): a limited, non-exclusive, revocable license to use the bot for your own purposes. You can't redistribute or re-share it without the creator's permission.
- What a template copies (x.ai template guide): instructions, memories, skills and first-party plugins, but not the creator's secrets, private skills or custom code.
Taken from the QA bot listing on x.ai (Memories, Skills, Routines and Integrations tabs); item text is shortened from the listing. Anything stated nowhere is marked "Not stated".
More Grok Bot templates
- PM bot by Ulysses Ng
- The Morning Newspaper by Karen X. Cheng
- Company Docs Q&A by Anoop Baliga
- Site Audit by Shimecki
AgentScout links to the original public listings and doesn't host copies. We aren't affiliated with xAI, Anthropic, OpenAI, OpenClaw, Cursor, n8n or the creators listed. Names and logos belong to their owners. Grok Bot cards show the creator's photo from the x.ai marketplace. Listing checked Oct 21, 2026.