Skip to main content
Super Magic is the surface where your automation becomes reusable. You can widen what it reaches with connectors, and capture a proven workflow as a skill your whole team runs by name. This is where a good automation engineer stops resolving tickets and starts shipping capability.

​
Connectors: give Super Magic more reach

Out of the box Super Magic works with Thread’s own data and its built-in integrations. Connectors extend it to external tools over MCP, so Super Magic can read and act in systems your desk already lives in. Connector tools appear in Super Magic only; they are not exposed over the Thread MCP server. Add external tools to Super Magic with connectors (Super MCP) is the setup path; the high-value ones for automation work:
Connector tools need their own sign-in and inherit the same permission model as every other Super Magic tool — they show up only once connected, and writes still run under your identity with confirmation.

​
Skills: package a workflow once, run it everywhere

A skill is a saved, prompt-first workflow — a proven way of doing a task that anyone can run in Super Magic by name. The Automation & Flows category is full of them, and the Connectors category shows real skills built on the connectors above. When you have a prompt that reliably does the job, don’t leave it in your head — make it a skill.
1

Prove the prompt by hand

Run it in the Super Magic composer until it works every time. A skill is only as good as the prompt underneath it.
2

Turn it into a reusable skill

Use the Skill Authoring Coach to shape the prompt into a clean, named skill — clear inputs, defined output, no dependence on one person’s context. Keep the instructions under 3,000 characters; the coach counts them for you and shows you where to cut.
3

Wire it to a Flow if it should run itself

A Flow that fires Super Magic on a ticket event is a Super Magic Agent (Super Magic + Flows). The Flow carries its own prompt and a write scope — it doesn’t call your saved skill, so paste the proven prompt in and give it only the write tools you’re comfortable with it using unattended.

​
The 3,000-character limit

Skill instructions and Flow agent prompts are capped at 3,000 characters. A skill saved before the cap keeps running, but it can’t be saved again until it’s shortened, so the limit shows up the moment you go to edit a long one. Almost every prompt that’s over the line is over because it explains why a step matters two or three times. Say it once, in the imperative, and most drafts land well under. When that isn’t enough, name a base skill instead of restating a contract you share with other skills — PSA Note Discipline for plain-text notes, Write Guardrails for confirmation gates, Connector Degradation for a missing integration, Sweep Honesty for result caps.
Naming a skill only works in Super Magic, not in a Flow. Working conversationally, Super Magic can reach your other saved skills, so naming one pulls in its contract. A Super Magic Agent fires a prompt with no skill lookup, a name there is just words on the page. Always keep a few words of gloss beside the name so the sentence stands on its own, and for anything a Flow runs, write the rule out in full.
Don’t buy space by deleting a guardrail, a confirmation before a destructive write, a data-loss consent step, an escalation trigger. If a skill can’t fit without losing one, it was two skills.
Mine your own backlog for skill candidates: run the Automation Opportunity Finder against last week’s tickets, then author a skill for the pattern that showed up most.

​
Where the pieces fit

You now have the full automation toolkit. A quick map of which layer owns what:
  • Flows / status automations: deterministic routing and state, no code.
  • Intents: conversational handling of a request type by the Triage Agent.
  • Super Magic skills: packaged, reusable workflows a person runs by name in Super Magic.
  • Connectors: extend that reach to external tools over MCP.
  • Thread MCP / API / Rewst: the same tool layer in your own client or code.

​
Next

That’s the course. Take a pattern from your own desk and ship it (an Intent, a skill, or a connector), then come back and browse the full library for the next one.

Back to your course

The hub: your starter kit, build ritual, and FAQ.

Automation & Flows skills

The full Magic Library category built for your role.