For: everyone. Anyone can use a persona; creating one needs the admin or editor role. ⚠️ Personas work in sqemes Chat and over MCP — not in the browser extension.
A persona is a working role: a support agent, a bid writer, a code reviewer. It is prose describing how that role works, plus a set of routes saying which playbook to load in which situation. It is not a third kind of playbook — it sits above prompts and skills and composes them.
The problem it solves
Once a team has thirty playbooks, the hard part stops being writing them and becomes knowing which one applies right now. The person with the question is usually the one least able to answer that — they are new, or it is not their area, or they do not know the shelf exists.
A persona moves that knowledge out of people's heads. You adopt the role, and the right playbook arrives when the situation calls for it.
Why it loads one route at a time
A persona does not pour all its playbooks in at once. Each route carries a condition, and a route is loaded only once its condition applies.
That restraint is the whole point. Twelve playbooks loaded together are twelve sets of instructions competing for attention, and the result is worse than any one of them alone. A persona is the mechanism for having many playbooks available without having them all active.
When you need one
The right playbook depends on the situation, and the person working cannot reliably tell which situation they are in.
A job always needs the same combination — two skills plus a choice of three prompts — and assembling it by hand every time is the actual friction.
You are onboarding someone into a role and want the role to carry its own instructions.
When you do not
If you have five playbooks and everybody knows all five, a persona adds a layer and solves nothing. If a single skill covers the job, apply the skill. And if you only ever use one prompt for a task, use the prompt.
Personas earn their keep at scale and in handovers. Early on they are usually premature, and a persona built before the playbooks are any good just routes reliably to mediocre ones.
One thing that surprises people
A persona's routes are filtered against your access, never its author's. If a route points at a playbook you are not allowed to see, you get the persona without that route — silently, with no gap where it would have been.
That is deliberate: attaching a playbook to a persona must never widen who can read it, or building a persona would become a way of handing out permissions. It does mean a persona can behave differently for two colleagues, and if one of them seems to be missing a step, access is the first thing to check.
Updated 27 September 2026 · Article version 1