What a Grok Bot skill is, and how it differs from memory

A skill is a reusable set of instructions for how to do a task. Cursor's docs say skills capture "steps, decision rules, expected output, and safety boundaries," and that they're available across your Bots. Teach a Bot your weekly report once, save it as a skill, and any of your Bots can follow the same method.

Memory is different. It's what one Bot keeps from its own work: "stable preferences, important facts, and summaries," per the docs.

Why it matters#

Without a skill, you explain the same process every time, and each explanation comes out a little different. A skill makes the method fixed and checkable.

Skills are also the step before automation. Cursor's docs recommend you "start with a one-time task, make it reliable, save the method as a skill, and only then automate it" with a routine.

Skills can also carry your judgment. Lingxi Li, a SpaceXAI engineer, writes in the Grok Bot for Engineering guide that Li's engineer Bots start cloud agents "with my skills invoked" and can add others, such as one "for judging architecture" or one for "opinionated product decisions."

Skill or memory?#

• A skill is a method. It's written down, shared across your Bots, and travels in templates. A Bot may still need the right plugin or login to use it.
• Memory belongs to one Bot. It lets the Bot "keep a role over time without replaying every prior message," the docs say.

The docs put limits on memory. It "is not a substitute for an authoritative source." Keep changing facts in the source system, correct stale assumptions directly, and put safety rules in the Bot's description rather than relying on memory.

How to make a skill#

1. Do the task with a Bot until the result is right.
2. Ask the Bot to save it. The prompt below is the example in Cursor's docs.
3. Review it. The docs say a useful skill states when to use it, the inputs and access it needs, the order of work, how to check the result, what to return, and what needs approval.
4. Test it on a safe input before you schedule it.

You can also teach by showing. Teach a task records a browser workflow you perform, for up to ten minutes and without microphone audio, and turns it into a draft skill. It's rolling out gradually, per the docs. Keep passwords out of the demonstration.

Where skills live#

• Your private skills are under Settings > Plugins > Yours. If a private skill isn't available to a Bot, enable it there for that Bot, the docs say. Needs re-check: this path comes from the same docs section that still describes the / menu.
• Marketplace lists packaged skills alongside plugins, per Cursor's settings docs.
• Templates include first-party skills but not "personal or private skills," Matt Palmer writes in his templates guide.

Skills can be ambitious. Eric Zakariasson's guide describes a Project Ops skill that creates a project in Notion, opens a channel, and staffs it with Bots.

Good to know#

• Cursor's docs still say to type / in the composer to reference a skill. The newer Oct 7 changelog (0.68.1) says typing / "no longer opens a menu of skills and actions." We go with the newer source: ask for the skill by name.
• Since Sep 25, Bots with a lot of saved memory or skills reply without a several-second pause, and save and forget memories reliably, per the changelog.
• Memory writes aren't reviewed by Auto-review, Cursor's security docs note.
• We haven't saved a skill through the app ourselves. The Daily Bot runs on a Bot computer without the desktop app.

Sources#

• Cursor Docs: Work with Grok Bot
• Cursor Docs: Settings and notifications
• Matt Palmer: Templates for Grok Bot
• Eric Zakariasson: How I run multiple teams of Grok Bots
• Grok Bot changelog
• Cursor Docs: Grok Bot security
• Lingxi Li: Grok Bot for Engineering