Personal and shared skills
Every skill is either Personal or Shared.
On the Skills page, your personal skills are listed under Your Skills and workspace skills under Shared Skills.
- Only an admin can create a shared skill, or share a personal skill while editing it.
- Everyone else can open a shared skill to read its instructions, but can’t change or delete it.
- Sharing only goes one way. A shared skill can’t be turned back into a personal one.
Create a skill
1
Open Skills
In Super Magic, select Skills in the left sidebar. You can also type
/ in the message box and select Manage Skills at the top of the list.2
Select New Skill and fill in the fields
- Scope: Personal, or Shared if you’re an admin. New skills start as personal.
- Name: a short, clear name. It has to be different from every other skill you can see, shared ones included.
- Description: one line on what the skill does and when to use it. Super Magic reads the name and description to decide when a skill fits a request, so be specific.
- Instructions: the steps Super Magic should follow. Markdown works here, and a counter shows how close you are to the 3,000-character limit.
3
Save it
Select Save Skill. The skill now shows on the Skills page, ready to run.
Run a skill in Super Magic chat
1
Open the skill list
Type
/ at the start of your message. A list of your personal and shared skills opens, each tagged Personal or Shared. Keep typing to filter by name.You can also select the + button in the message box and choose Skills.2
Pick a skill
Select the skill and it’s added to your message as a badge. Send it as is, or add some context first, like the client or user it’s for. Picked the wrong one? Remove the badge and pick again.
3
Review and confirm
Super Magic follows the skill’s instructions on the ticket you have open, or on whatever you named in your message. By default, it shows a Confirm action card before it changes anything, and nothing happens until you select Confirm.
Run a skill from a Flow
To run a skill on its own whenever a ticket matches, add an Agent Builder action to a Flow and choose Run a Skill. This works well when technicians also run the same job by hand in chat, because the instructions live in one place.1
Create or open a Flow
In Thread Admin, open Flows and create a flow or edit one. Set conditions so it only matches the tickets you want, and start small, with a test board or a single test client.
2
Add Run a Skill
Add the Agent Builder action, choose Run a Skill, and pick the skill under Skill. Only shared skills are listed. If yours is missing, it’s probably personal, so ask an admin to share it.
3
Choose the write tools
Tick the write tools the skill needs. Read tools are always available.Pay attention here, because the two Agent Builder modes behave differently when no write tool is ticked:
Your workspace’s Super Magic write settings still apply either way. For a tightly scoped skill, tick the tools you want it to use. Destructive actions, such as rebooting a device, stay blocked in unattended runs.
4
Test, then turn it on
Leave the flow off while you create a test ticket that matches, then turn the flow on and watch. Check three places: the ticket itself, Super Magic → Flow Chats for the agent’s reasoning, and Flows → Logs to see whether the flow fired. Agent actions show Dispatched in the log, which means the handoff worked, not that the job is done.
- A flow runs its actions once per ticket. That includes a run that failed, and there’s no automatic retry. Use a fresh test ticket each time.
- What the agent says isn’t posted to the ticket. The ticket only changes through the write tools you ticked. If you want a note, tick the tool for adding a note and tell the skill to post its result as an internal note.
- The run acts as the skill’s creator. Its chat shows up in that person’s Flow Chats. If the creator is no longer an active member, the run acts as an active admin instead.
Limits and tips
- Instructions are capped at 3,000 characters. The same cap applies to a Flow’s agent prompt. A longer skill saved before the cap keeps running, but you can’t save changes until it’s shortened. Building with Super Magic shows how to trim a long prompt.
- Names must be unique among the skills you can see. If a name is taken, you’ll see “A skill with this name already exists.”
- Write a description that says when to use the skill. It’s how Super Magic recognizes that a skill fits.
- Keep each skill to one job. Short, focused instructions are easier to test, and easier to chain later.
- Share a skill before you automate it. Only an admin can set a skill to Shared.
- Your Super Magic settings still apply. In a Flow, the write tools you tick are the skill’s scope. See the Super Magic admin guide.
Related
Super Magic FAQ
Quick answers on where skills run and why one might not.
Chaining skills
Run several skills in order from one orchestrator skill.
Build an agent with Agent Builder
Set triggers, tools, and debugging for unattended runs.
Magic Library
Browse prebuilt prompts to start a skill from.
Meet Super Magic
Get to know the assistant that runs your skills.