Grok Bot skill prompts: save it, teach it, test it
A skill is a reusable method. Official order: one successful task, save the method, test on a second input, only then automate. Teach a task records the screen for up to 10 minutes. No mic. No secrets on screen.
In short: This page contains 21 copy-paste ready prompts, organized into 5 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.
Save a skill from a run
5 promptsSave the process we just used
1/21✨ What it does
The Bot saves the process you just used as a skill called "[NAME]", including when to use it, inputs, steps, and the rule that outside contact always needs your approval. You test it on a second input.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Save the process we just used as a skill called "[NAME]". Include source systems, output format, and the rule that external contact always needs approval. Sources: This conversation, files we produced, apps we opened. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not create a routine yet. Deliverable: Skill: when, inputs, access, steps, validation, output, approvals, failure behavior. Review point: I will test it on a second input.
Pro tip: Name when to use it, inputs, steps, validation, output, and what needs approval.
Add the rules the demo missed
2/21✨ What it does
The Bot edits skill [NAME] to add decision rules, failure handling, and approval lines that one demo did not show, using the edge cases in [LIST]. You accept the changes.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Edit skill [NAME] to add decision rules, failure handling, and approval boundaries that were not obvious from one example. Sources: The skill draft, edge cases I list: [LIST]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not enable the skill for every Bot until I say so. Deliverable: Diff of the skill, plus the new failure cases. Review point: I accept the diff.
Pro tip: One happy-path recording will not encode "if the CRM is empty, stop".
Test on a second input
3/21✨ What it does
The Bot runs skill [NAME] on this second input: [PASTE], and compares it to the first run. You edit the skill, then you decide whether to schedule it.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Run skill [NAME] on this second input: [PASTE]. Compare to the first run. Sources: The skill, second input, first-run output. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not schedule a routine. Keep writes behind approval. Deliverable: What matched, what drifted, recommended skill edits. Review point: I edit, then I decide on a routine.
Pro tip: If the second input fails, do not schedule. Fix the skill.
Enable a private skill for this Bot
4/21✨ What it does
The Bot turns skill [NAME] on for this Bot and shows you how to call it with /. You type / and confirm it appears.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Make skill [NAME] available to this Bot and show me how to invoke it with /. Sources: Settings → Plugins → Yours. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not install random marketplace skills. Deliverable: Enabled (yes/no), how to invoke, which other Bots can see it. Review point: I type / and confirm.
Pro tip: Official: Settings → Plugins → Yours, enable for the current Bot. Type / to reference it.
Skill from written instructions only
5/21✨ What it does
The Bot creates a skill called [NAME] from the written steps you paste and the finished task in this thread, and lists gaps a screen recording would have caught. You test it.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Create a skill called [NAME] from these written steps and the completed task in this thread. Sources: Steps I paste, the completed task artifacts. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not pretend you recorded the screen if you did not. Deliverable: Skill draft plus the gaps a recording would have caught. Review point: I test it.
Pro tip: Teach-by-demonstration may roll out gradually. Written + completed task still works.
Teach a task
4 promptsSet up a teaching session
6/21✨ What it does
The Bot prepares a Teach-a-task session for [WORKFLOW] with a computer-view checklist and a plan that keeps secrets off the screen. You click Teach a task and perform the work once.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Prepare Teach a task for [WORKFLOW]. I will perform it once. You write the skill. Sources: This one-to-one conversation and its computer view. Target: [APP]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not start recording until I say go. Stop if a secret would appear. Deliverable: Ready checklist: computer view, result sentence, secret-safe plan. Review point: I click Teach a task.
Pro tip: Open the computer view first. Teaching without the computer view is just chatting.
Ten-minute CMS update
7/21✨ What it does
The Bot watches you update [CMS PAGE] once and writes a skill another Bot could follow next week, with publish kept behind approval. You edit the skill; publish stays yours.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Watch me update [CMS PAGE] once. Write a skill another Bot could follow next week. Sources: [CMS] on the computer. I take over for login. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not publish. Teaching records the screen, not the microphone. Deliverable: Skill draft, unpublished vs published steps, approval line for publish. Review point: I edit the skill. Publish stays mine.
Pro tip: Ten minutes max. No mic. Do not type passwords on camera.
Hardware or local tool demo
8/21✨ What it does
The Bot watches you push an update to [DEVICE OR LOCAL TOOL] and writes a skill with the exact command sequence and the consent step. You run the next update.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Watch me push an update to [DEVICE OR LOCAL TOOL]. Write a skill. Do not run extra commands. Sources: The local computer permission, if I grant it, plus the cloud computer. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not run commands I did not demonstrate. First local action needs my consent. Deliverable: Skill with the exact command sequence and the consent step. Review point: I run the next update.
Pro tip: Local actions ask consent the first time, then auto-review. Watch the command card.
Stop the recording and review
9/21✨ What it does
The Bot shows the skill it wrote after you stopped the recording and lists what it is unsure about. You edit it, then you test it.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: I stopped the recording. Show the skill you wrote and list what you are unsure about. Sources: The recording and the on-screen path. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not save over an existing skill with the same name without my ok. Deliverable: Draft, unsure list, suggested tests. Review point: I edit, then we test.
Pro tip: The learned skill is a draft. Official docs: add rules the example did not show.
Marketplace and plugins as skills
4 promptsFind a skill before you invent one
10/21✨ What it does
The Bot searches installed and marketplace skills for [JOB] and recommends install, skip, or write-your-own, with the permissions each one wants. You install if you pick one.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Search installed and marketplace skills for [JOB]. Recommend install vs write-our-own. Sources: Settings → Plugins, [JOB DESCRIPTION]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not install a skill until I pick one. Read the permission list first. Deliverable: Matches, permissions they want, recommend install / skip / write. Review point: I install.
Pro tip: Official marketplace exists. Prefer a plugin, fall back to the browser.
Audit an installed skill's permissions
11/21✨ What it does
The Bot audits skill [NAME]: what it can see, which Bots have it, and whether you still need it. You disable it if you want.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Audit skill [NAME]: permissions, which Bots have it, whether we still need it. Sources: Settings → Plugins → Yours. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not uninstall until I say so. Deliverable: Permissions, enabled-on, keep / disable / remove. Review point: I disable.
Pro tip: Skills are available across Bots. A sloppy install is a sloppy computer.
Port a SKILL.md carefully
12/21✨ What it does
The Bot turns the SKILL.md you attach into a Grok Bot skill draft and adds your approval boundaries, refusing secrets, auto-send, and production writes. You test it on a dummy input.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Turn this SKILL.md into a Grok Bot skill draft and add our approval boundaries. Sources: The file I attach, our never-do list. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not run the skill against live systems until I test it. Deliverable: Adapted skill plus what you refused to port (secrets, auto-send, prod writes). Review point: I test on a dummy input.
Pro tip: awesome-claude-code style SKILL.md files are conceptually portable. Still add your approval line.
Slash-command cheat sheet
13/21✨ What it does
The Bot lists the / skills and @ targets this roster should use weekly, twelve lines max, and drops the rest. You pin it.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: List the / skills and @ targets this roster should use weekly. Drop the rest. Sources: Enabled skills, Bot list, connectors. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not disable anything yet. Deliverable: Weekly cheat sheet, 12 lines max. Review point: I pin it.
Pro tip: Official: / for skills, @ for Bots, groups, routines, connectors.
Like these prompts? There are full tutorials behind them.
Learn the workflows, not just the prompts. 300+ easy-to-follow tutorials inside AI Academy — and growing every week.
Quality bars for skills
4 promptsIdempotent retries
14/21✨ What it does
The Bot rewrites skill [NAME] so a second run does not send twice or create twice, while side effects still need your approval. You test it twice.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Rewrite skill [NAME] so a second run does not duplicate side effects. Side effects still need approval. Sources: The skill, the systems it touches. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not add a send step to "make it useful". Deliverable: What would duplicate, the guard you added. Review point: I test twice.
Pro tip: Official routine design: make retries idempotent where possible.
Stale-data policy
15/21✨ What it does
The Bot adds a no-data and stale-data policy to skill [NAME] using the max age you allow: [E.G. 24H]. You accept the new lines.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Add a no-data and stale-data policy to skill [NAME]. Sources: The skill, max age I allow: [E.G. 24H]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not use cached numbers older than [N]. Deliverable: The new policy lines and an example failure message. Review point: I accept.
Pro tip: If the CRM is down, fail. Yesterday's pipeline is not a briefing.
Partial completion report
16/21✨ What it does
The Bot edits skill [NAME] so a run that finished only some of the steps reports done, blocked, and the next human step, instead of marking itself done. You accept the format.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Edit skill [NAME] so partial completion is explicit and listed here, not hidden. Sources: The skill. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not mark a partial run as done. Deliverable: Partial-completion format: done, blocked, next human step. Review point: I accept.
Pro tip: Official: tell the Bot where to report partial completion.
Retest after the site changed
17/21✨ What it does
The Bot adds a "retest if the site changed" note to skill [NAME] and runs it once on [URL] to see if the buttons still match. You rewrite the skill if they drifted.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Add a "retest if UI changed" note to skill [NAME] and run it once on [URL] to see if the buttons still match. Sources: The skill, the live UI. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - If the UI drifted, stop and rewrite. Do not click random lookalikes. Deliverable: Still matches / drifted, screenshots, proposed rewrite. Review point: I rewrite if drifted.
Pro tip: Taught WordPress skills rot. Put a retest trigger in the skill.
Skill library for a roster
4 promptsWhich Bot owns which skill
18/21✨ What it does
The Bot maps each skill to one owning Bot, with who may read it versus who may write with it. You apply the map.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Map skills to a single owning Bot. Shared-read is fine. Dual-write is not. Sources: Skill list, Bot list. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not enable a skill on a second Bot until I agree. Deliverable: Skill, owner Bot, who may invoke, write vs read. Review point: I apply the map.
Pro tip: A skill available to all Bots plus no owner is how two Bots file the same expense.
Kill unused skills
19/21✨ What it does
The Bot lists skills not used in [30] days and recommends disable or keep. You disable the ones you do not want.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: List skills not used in [30] days. Recommend disable vs keep. Sources: Skill list, recent conversations if you can see them. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not delete skills. Deliverable: Unused, last-seen if known, disable/keep. Review point: I disable.
Pro tip: Disable first. Delete second.
Skill that must never send
20/21✨ What it does
The Bot writes a six-line footer that forbids send, pay, delete, or production changes unless an approval card already fired. You paste it into every skill that touches mail, CRM, or money.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write a 6-line footer that forbids send/pay/delete/prod unless an approval card already fired. Sources: Our never-do list. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. Deliverable: Footer text I will paste into every skill that touches mail, CRM, or money. Review point: I paste it.
Pro tip: If the footer is not in the skill, a future edit will "just send it".
Teach-a-task in under ten minutes
21/21✨ What it does
The Bot coaches you through teaching [WORKFLOW] as a skill: what to show, what to omit, and where to stop the recording so send or publish never appears. You record; the Bot only coaches.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Coach me through teaching [WORKFLOW] as a skill: what to show, what to omit, where to stop the recording. Sources: The workflow I name: [STEPS]. Apps: [LIST]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not include send, pay, delete, publish, or prod clicks in the taught path. Deliverable: Shot list, stop point, and the skill name. Review point: I record. You only coach.
Pro tip: If the recording includes Publish or Send, stop and recut. The skill will learn the dangerous click.
Free tool
Prompt Optimizer
Turn a rough idea into a structured, professional AI prompt.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.
7-day free trial. Cancel anytime.
Related guides