Grok Bot Skills: Save, Switch On And Share A Skill (2026)

Grok Bot skills turn one task you got right into a method every Bot on your account can repeat on request.

This is the exact order I'd set them up in: run the job once, save it, switch it on, call it, then share it, all straight from the skills and routines docs and the Grok Bot changelog.

Every step below names the real buttons, so you can follow along with the app open.

Want a second pair of eyes on your agent setup? Book a free SEO strategy session with my team.

What a Grok Bot skill is, and what it isn't

A skill is a reusable set of instructions for how to do one task.

It holds the steps, the decision rules, the output you expect and the safety boundaries.

A routine is a different object: it tells one Bot when to run a workflow, on a schedule or after an event.

The Grok Bot FAQ puts it in one line: the skill is the how, the routine is the when.

Skills are available across your Bots, but a Bot still needs the matching app or login before it can use one.

Get the skill right first, and only then hand it to a routine.

Step 1: Run the task once by hand before you save anything

Don't write a skill from a blank page.

The docs' own advice is to start with a one-time task, make it reliable, save the method, and only then automate it.

So pick one real job, such as a weekly account check or a lead list clean-up, and do it in a normal chat with the Bot.

Correct it until the output is exactly what you'd hand a client.

That finished chat is now the raw material for the skill.

Step 2: Save it with a prompt that names all six parts

In the same conversation, ask the Bot to save the process as a named skill.

The docs' example prompt is this:

Save the process we just used as a skill called "Weekly account health."
Include the source systems, risk definitions, output format, and the rule that
customer contact always requires approval.

Then check the saved skill covers the six things the docs list for a useful skill:

Part	What the skill should spell out
1. Trigger	The situations it should be used in
2. Inputs	Which inputs and access it needs
3. Steps	The order the work happens in
4. Checks	How the result gets validated
5. Output	What it hands back
6. Approval	Which actions need sign-off first

If any of the six is missing, tell the Bot to add it before you move on.

Number six is the one people skip, and it's the one that stops a Bot sending an email you never saw.

Step 3: Find it in the Add skills library under Connect apps

Open Connect apps in the sidebar.

Supported apps and packaged skills are found and installed from that screen.

Select the connected count next to the title to manage what you've installed and your private skills, per the settings docs.

The changelog calls the skill picker the Add skills dialog, and it has a library step.

Since v0.78.1 (27 Oct) that library step no longer shows a Back button, so close the dialog when you're done instead of hunting for one.

🔥 Want the skill library I'd build first? Inside the AI Profit Boardroom you get step-by-step video trainings on saving, testing and sharing agent skills, the installable Agent OS, four coaching calls a week and 3,400+ members swapping the skills that work. → Join the AI Profit Boardroom

Step 4: Switch it on for the Bot that can't see it

Every Bot you own draws on the same single library of private skills.

That doesn't mean every Bot has every skill switched on.

Bot can't find a private skill? Go to Connect apps, click the connected count, then switch the skill on for this Bot in the Private skills list.

This is the most common "it doesn't work" moment I'd expect, and it's a toggle, not a bug.

On iPhone, Duplicate a Bot and the copy keeps its enabled skills, which saves redoing the toggles for a second region or client, per the Bots docs.

Step 5: Call it by name, with @ for the apps it needs

Running a skill is just asking the Bot for it by its name.

Pull in Bots, groups, routines and apps alongside it with @.

Don't type / and wait for a menu: since v0.68.1 (7 Oct) the slash no longer opens a list of skills and actions.

A clean call looks like "Run Weekly account health for @Acme using @HubSpot, and stop before any customer email."

Name, scope, app, stop point. That's the whole pattern.

Teach a task: record the workflow instead of typing it

When Teach a task is available, you can show the Bot a browser workflow instead of describing it.

In a one-to-one Bot chat, open the computer view and pick Teach a task; describe the result you want, do the job once yourself, then stop the recording.

The Bot turns it into a skill you review and test on a safe example before any schedule touches it.

Recording covers visible screen interaction for up to ten minutes and doesn't capture microphone audio.

Keep secrets off screen and use the secure handoff flow for logins.

Treat the result as a draft: add the decision rules, failure handling and approval points one demo can't show.

The control may roll out gradually, so if you can't see it, ask the Bot to build the skill from written steps plus the finished task.

Plugin skills: 200 per Bot and usable mid-task

Plugins bring their own packaged skills, and the ceiling moved a lot this autumn.

Since v0.71.2 (14 Oct), the cap on skills a Bot can use from your installed plugins went from 24 to 200.

Since v0.75.8 (24 Oct), when a Bot installs a plugin while it's working, it can use that plugin's skills straight away, without a restart.

For the install side, sign-ins and per-app gotchas, see my Grok Bot plugins walkthrough; this page stays on the skills themselves.

My rule: install the plugin, then wrap its raw skills in one private skill of your own that adds your approval line.

"From template" skills, and why you can't publish them

Start a Bot from a template and it arrives with skills baked in.

Since v0.77.0 (26 Oct), those template skills sit under Private skills with a From template label.

That label matters: per the docs, you can't publish a skill to a team if it shipped with the app or came from a Bot's template.

If you want to share one, ask the Bot to write a new skill based on it, with your own name and description.

That new skill is yours, so the Publish button works on it.

Publish a skill to your team, then Sync every edit

On desktop it's Connect apps, then the connected count, then the skill itself, where Publish sits in the header.

In more than one team? Pick the team under Publish to.

The skill needs a description first, because teammates and their Bots read it to decide when the skill applies.

Once it's live, the button reads Published and its menu offers Sync, Copy link and Unpublish.

Sync is the step people forget: your later edits don't reach the team's copy until you press it.

If publishing is refused, the message says why: either you need to join a team, or an admin has turned off member publishing.

📞 Setting up skills for a client team? Book a free SEO strategy session and we'll map which of your workflows to save, publish and automate first. → Get the free call

Team Bot skills: what Managers can change

A shared Team Bot works differently from your personal library, per the shared Bots docs.

The owner or a Manager adds skills under Bot settings, next to Plugins, Secrets and Files, and those skills work in every teammate's chat.

When you share, Add as lets you pick Collaborator to chat, or Manager to change instructions, skills, memory and apps.

The changelog tracks how this grew: v0.61.0 walks a new Team Bot through plugins, secrets, skills and files, v0.62.0 shows their counts in the info pane, and v0.64.0 lets Managers edit skills.

Since v0.77.0, a Team Bot also follows the skill guide of a connector a teammate has allowed.

Give Manager rights to the one or two people who own the workflow, not the whole team.

Errors and fixes worth knowing

"Can't find the skill." It's in the library but off for this Bot. Enable it under Private skills.
Skills fail to load. Since v0.70.2 the app shows the error with Try again; press it before you rebuild anything.
Old "Couldn't load skills" row. Removed from the @ menu in v0.71.2, so don't wait for it.
Slow first reply. v0.59.0 removed the several-second pause for Bots with lots of saved memory or skills; update the app if you still see it.
Two accounts merged. When you unify Cursor accounts, matching skills replace the primary account's, and skills only the primary has are kept.

Test it on a safe input before a routine sees it

A test run performs real work: it can browse sites, change files and call connected tools.

So give the new skill a harmless input, like last month's data or a test inbox, and watch the run.

Then read the result against the review points the docs list for a first run.

Did it pick current inputs, not stale ones?
Is the output in the format you asked for?
Does every action have a source or audit trail?
Did it stop where it was told to wait for approval?
When something was missing, did it say so clearly?

Any "no" goes straight back into the skill as a new rule, then you test again.

Two clean runs in a row is my bar before a routine gets to own it.

My pre-flight checklist for every new skill

Run the task once in chat and fix the output.
Save it with a clear name and all six parts.
Write a one-line description, even if you never publish it.
Enable it for the Bots that need it under Private skills.
Test it on a safe example and read every action it took.
Keep send, buy, delete and publish behind approval.
Only then attach it to a routine.

If you want the routine side of step seven, my Grok Bot routines guide picks up where this one stops.

For a done-for-you library of agent skills plus weekly coaching, join the AI Profit Boardroom.

Or book a free strategy call and we'll pick your first three skills together.

Also On Our Network

FAQ: Grok Bot Skills

Why can't my Bot find a skill I saved?

Private skills are one shared library, but each Bot needs the skill enabled. Open Connect apps, select the connected count and switch it on for that Bot under Private skills.

Does typing / still open the skills menu?

No. Since v0.68.1 the slash no longer opens a menu of skills and actions. Ask for the skill by name and use @ for apps, Bots, groups and routines.

How long can a Teach a task recording be?

Up to ten minutes of visible screen interaction, with no microphone audio. The result is a draft skill you review and test.

Why is the Publish button refused on some skills?

Skills that came with the app or a Bot's template can't be published, and you also need a team plus an admin who allows member publishing. A description is required too.

Do edits reach the team copy automatically?

No. After publishing, use Sync in the Published menu to push later edits to the team's copy.

📺 Video notes + links to the tools 👉

🎥 Learn how I make these videos 👉

🆓 Get a FREE AI Course + Community + 1,000 AI Agents 👉

About Julian

I'm Julian Goldie, an SEO entrepreneur, author and founder of the AI Profit Boardroom, which has 3,400+ members.

I help business owners scale with AI agents, automation and SEO.

I've built a 7-figure SEO and link building agency, Goldie Agency, with a team of 70+ SEO experts.
I've grown a YouTube channel to 400,000+ subscribers.
I wrote "Link Building Mastery".
My Udemy courses have taught over 29,000 students.

→ Get my best AI training inside the AI Profit Boardroom

Run one task, save it, switch it on, test it, and only then share it: that order keeps your Grok Bot skills reliable. If you want help picking which workflows to save first, book a free SEO strategy session and set up your Grok Bot skills this week.