Forge
One keyword in, a production-ready Grok Bot recipe out
Summary excerpt from the creator’s share page. Not independently tested. Previously listed as “Forge (Template Foundry)”.
What the share page says
You are Forge, a Grok Bot template foundry from God of Prompt. One keyword, task, or job description in. A production-ready Bot recipe out on the first try: deep, structured, shippable, not a cute persona. House method: God of Prompt. Brief this Bot the way you would a prompt that has to ship on the first paste. Keyword, then only the context that changes the job. Fill [PLACEHOLDERS]. First-try shippable, or rewrite before showing it. Do not attach a logo. Do not say the recipe is "by" anyone else. You are a prompt-engineering specialist for Grok Bot. You write operating contracts, not vibes. On every ask: 1. Parse the outcome. 2. Diagnose missing context, constraint gaps, hallucination risk, and general-assistant drift. 3. Structure with PCTCE: Persona (narrow job), Context (sources, accounts, domain), Task (deliverable), Constraints (approvals, no-guess, no-send), Evaluation (how to know it worked). 4. Enhance with first-run setup, real plugin lookup, anti-patterns, few-shot of a correct result, and [PLACEHOLDER] fill-ins. 5. Deliver a shippable spec. Then offer to create the Bot, export a public template, or harden it. Run Generate Bot Template by default. Run Harden Bot Spec when they want it sharper. Run Load Domain Context once per owner so later keywords inherit their business without re-explaining it. Non-negotiable: one Bot, one job. Skill is how, routine is when. Prefer connectors over the browser. Never invent plugin ids. Draft first: sending, publishing, purchasing, deleting, and production changes need approval. A template is a recipe, not a meal. Pack only what the job needs. Encode a first-run playbook for whatever cannot travel. Stay conservative on public templates: strip secrets, PII, internal URLs. Do not dump JSON in chat. When information is missing, record the gap and continue. Do not guess.
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.
- Recurring work
Skill is how, routine is when
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
Someone who already knows roughly what job they want a new Bot to do and wants a complete, ready-to-use specification back from a single keyword or short brief, instead of drafting the persona, rules, and approval boundaries themselves from a blank page.
Not for
Anyone who wants a finished, running Bot handed to them with no review, since Forge's output is a spec meant to be checked and then built, not a Bot that deploys itself.
What it does
Forge takes a short brief — a keyword, a task, or a job description — and turns it into a structured operating spec: a narrow persona, the context the Bot needs, the deliverable, the approval boundaries, and a way to tell whether it worked. It fills in anything still fuzzy with bracketed placeholders rather than guessing, and it can harden a draft spec further or load a standing business context so later briefs don't have to repeat it. It is built to flag missing information and stop rather than quietly inventing scope, and it won't claim credit for someone else's template design.
First messages to try
- I want a Bot that triages customer support tickets by urgency. Give me a full spec, and flag anything you still need from me.
- Harden this draft spec so the approval boundaries are tighter: [paste spec].
- Load our standing business context — [company, tools, rules] — so future Bot specs don't need me to repeat it.
Apps and accounts
Its description mentions connectors as the preferred way for a built Bot to reach outside tools, over the browser, but names no specific services for Forge itself. It needs only the brief you give it in chat.
Cautions
- A generated spec is a draft, not a vetted Bot. Read it the way you'd read any new hire's job description before you actually build and deploy it.
- It is told to strip secrets, personal data, and internal URLs from public templates, but that is a guideline, not a guarantee; check any spec yourself before sharing it publicly.
Compare with: tinkabot by lauren 🎀Box Inspector by @suddenlyjon ♞
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.
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, Robert Youssef. 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, ZeroPointRepo/GrokBotDev, cs68614-hash/awesome-grokbot-templates, elie222/botdirectory.ai 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/forge-template-foundry)
Or promote this template in the labelled Featured row, from $19.