When template skills show in preview but export empty
Use this when you imported a Bot template and the skills you saw in its preview are missing. A Bot template preview can list skills under Context → Skills with the full body visible, then the published import ships "skills": []. Instructions, memories, routines, and plugin references still arrive (routines often pause until you approve). The skill is not applied to the imported Bot and does not appear in that Bot's skill list (Cursor staff, forum 169911, Aug 31, 2026). On desktop, a missing / menu is also expected since changelog v0.68.1 and is not by itself proof the import was empty — see When typing / on desktop no longer opens the skills menu. Staff (mohitjain, Aug 31, 2026) called this unintended and tracked on forum 169911.
Recreate the skill on the imported Bot
- Open the template preview before or after publish and read the skill name plus body under Context → Skills.
- On the imported Bot, ask it to recreate the skill, for example:
Create a skill called <name> with this content: <paste body>. - Confirm the skill appears in that Bot’s skill list and runs when you name it in a message (or, on mobile, from the
/menu if that menu still appears).
Happy-path share links still follow Share a Grok Bot with a public link. This page is only for the empty-skills import case.
When the preview Content field will not copy
On some Windows desktop builds the preview Content field is not selectable (Ctrl+A grabs the chat behind the modal). Staff’s copy-and-recreate path needs selectable text or another source for the body. If you authored the skill, open the original Bot and copy from there, then recreate on the import. Third-party templates without a selectable body stay blocked until staff ships selectable Content or a copy control.
Related
- All how-tos: How-to index.
- Save the skill again: Save a skill in Grok Bot.
- Review imported routines: Save a Grok Bot skill and schedule a routine.
- Desktop
/menu gone: When typing / on desktop no longer opens the skills menu.
Pitfalls
- Treating empty
"skills": []as a failed share of instructions or routines — those fields can succeed while skills stay empty. - Expecting Uninstall / reinstall of the template to fill skills while the import path is still broken.