Super Magic Skills — Save Your Team's Best Playbooks
Skills turn your team's know-how into reusable playbooks for Super Magic. Instead of typing the same long instructions every time — how to triage, how to offboard an employee, what a proper shift handoff looks like — you save it once as a skill, and anyone can run it in one step.
What is a skill?
A skill is a saved set of instructions with a name and description. When you run it, Super Magic follows those instructions as its brief for the conversation — using the same tools, permissions, and confirmation steps as always. A skill doesn't grant any new powers; it just tells Super Magic exactly how your team wants a job done.
Where to find skills
- In the chat composer: type
/at the start of a message to open the skill picker. Pick a skill and it's staged on your message — add extra context if you want, or send it on its own ("run this skill"). - The Skills page: open Magic tab menu in Inbox -> Skills.
- Just ask: Super Magic knows which skills exist and can load one mid-conversation when it fits the request.
Private vs shared
Type | Who sees it | Who manages it |
Private | Just you | You |
Shared | Everyone in the workspace | Admins |
Members create private skills freely. Sharing a skill with the whole workspace (or editing a shared one) is admin-managed, so your team's official playbooks stay curated.
Two ways to create a skill
- The Skills page — click New, give it a name, a short description, and the instructions. The description matters: it's how Super Magic (and your teammates) know when to use it.
- Ask Super Magic to build it — e.g. "Create a skill for our password reset process: verify identity with a callback, reset in the PSA, send credentials via secure link, log the time." Super Magic drafts the skill for you; you review and save. You can also ask it to update an existing skill.
Writing a good skill
- Be specific about steps. "Check X, then Y, then draft Z" beats "handle the ticket properly."
- Name the tools and sources. "Search the knowledge base and IT Glue before answering" steers it to the right places.
- Define the output. "End with a bulleted summary and a recommended next action" gets you consistent results.
- Say when to stop. "Draft the closure note but wait for my confirmation" keeps humans in control — and remember write actions always require confirmation regardless.
Good to know
- Skills respect all permissions. A skill can't do anything the member running it couldn't do — write access levels, tool toggles, and action confirmations all apply as usual.
- A skill alone is a valid message. Stage it with
/and hit send — no extra text needed.
Troubleshooting
Symptom | Cause | Fix |
Typing | It only triggers at the very start of an empty message | Clear the composer and type |
Can't edit a skill | It's a shared skill and you're not an admin | Ask an admin, or duplicate the idea as a private skill |
A skill disappeared | It was deleted, or it was another member's private skill | Check with your admin; shared skills are admin-managed |
