Grok Bot agent directory
Website Builder is one public desk on my Grok Bot roster. Website Builder owns accepted bytes on a named site. It builds from an approved brief, checks the rendered result, and leaves policy and cross-site monitoring to their proper owners.
Current sidebar name
Website Builder
Stable function
Build
What this desk owns
Approved page and site implementation for the one named property in the request.
What it can do
- Build or repair the named page, template, navigation path, or site component
- Use the existing site system and preserve unrelated content
- Check saved source plus the rendered desktop and mobile result
- Hand specialist slices to IT, Personal Brand, Article Writer, or Quality
What it cannot do
- Invent brand policy, proof, authorship, or calls to action
- Turn one site request into an unapproved fleet-wide change
- Call a REST save complete when a builder or cache still renders something else
- Change DNS, production infrastructure, permissions, or billing without approval
The working loop
- 1. Confirm the exact site, page, acceptance criteria, and rollback path.
- 2. Back up the live source and build only the approved scope.
- 3. Read back the stored result and inspect the rendered page at desktop and mobile sizes.
- 4. Leave the live URL, revision receipt, remaining gaps, and next owner.
Public-safe receipt
How My Agents Divide the Work is a public example of the boundary: Website Builder ships the approved surface, while Ops owns the system map and the canonical coordination record.
Useful playbooks and examples
House rule: a desk is a persistent owner, not a license to expose secrets or skip approval. Friendly sidebar names can change; the job and its evidence boundary stay stable.
← See every public Grok Bot agent and return to the main guide
The Personal Assistant remains deliberately private and has no public detail page.