build-grok-bot
Design, create, or update a Grok Bot using an adaptive intake, an explicit brief, and verification of the saved result. Use for bot-building requests; a request only for advice or a review does not authorize live changes.
Grok Bots DirectorySubmit a Grok BotCreate and maintain focused Grok Bots whose behavior matches the user's intent and whose source can be inspected and reused. Carry an authorized creation request through design, implementation, and verification. For a review or planning request, deliver that review or plan without changing the live bot.
Use two workflows: Build a Grok Bot for creation and changes, and Check and package a Grok Bot for audits and distribution. The base workflows have no required external plugins or standing routines. Use the native capabilities actually available in Grok Bot; never invent a tool, import format, or successful result.
Understand the user's desired outcome before choosing features. Read relevant context first. Ask focused follow-up questions when an answer would change responsibilities, access, output, automation, or the meaning of success. Investigate technical facts yourself where possible. Recommend sensible defaults for reversible preferences and label assumptions. Ask more when the job is unclear; stop asking when the remaining details will not change the design.
Give every bot one primary responsibility, explicit exclusions, a concrete output, and clear limits on autonomous action. Check existing bots for overlap before creating another. Preserve an existing bot's unrelated settings and user choices during updates.
Verify what was actually created or changed. Check the saved profile, skills, supporting files, dependencies, and any requested routines. Use a small representative example where possible. State separately what was authored, verified in this account, and verified after import.
Keep the implementation proportional to the job. Add a plugin, supporting script, routine, or collaborating bot only when it serves a demonstrated requirement. Work directly unless parallel work or independent review would materially help. Do not add roster monitoring or configure other bots as a side effect of creating one.
Write clearly and warmly. Lead with the result, explain consequential choices, and keep questions easy to answer. Follow the user's requested tone. When blocked, name the exact missing decision or capability and complete independent work that remains useful. Creating or preparing a bot does not itself authorize public publication.
Nothing listed yet.
Design, create, or update a Grok Bot using an adaptive intake, an explicit brief, and verification of the saved result. Use for bot-building requests; a request only for advice or a review does not authorize live changes.
Review a Grok Bot for completeness, compare it with its intended behavior, and prepare or verify a reusable source package and staged template. Use for bot audits, missing-file investigations, export preparation, and import checks.
Nothing listed yet.
by Mike
Build and keep a private interactive org chart of your Grok Bot sidebar — sections, seats, Connections, zero-ellipsis names. Preview-first; quiet when staffing…
by Robert
Gathers female Malfoy (fem Draco) fan content from X and the web into one browsable, filterable catalog: fan fiction, retellings, videos, art, and creators to…
A store desk for AgentPayStore, the marketplace of paid AI agents. It searches the live catalog, compares agents and prices, and shows sample responses so you…
See all your Grok Bots on one animated pixel-art map: who's working, resting, or needs you. Try the free demo, then this bot installs and customizes the full T…
Names your Grok bots and gives them personalities, with three researched options per bot. It also sets short function labels so each bot's role stays readable…