For: people who were invited into a workspace. Written for the member role, which is what most invited colleagues get. If you were the one who created the workspace, you want I am setting up a new workspace. What do I do first? instead.
Someone on your team set sqemes up and added you to it. Nobody asked you first, and the product does not explain itself on the way in. Here is what it is, in the order that matters to you.
What your colleague actually put in there
A playbook is one piece of your team's AI know-how, written down once so that everybody uses the same version of it. There are two kinds, and the difference is worth knowing before you open anything.
A prompt is a task. It has gaps in it —
{{customer_name}},{{product}}— that you fill in each time you use it.A skill is knowledge. Your tone of voice, your pricing rules, the way your company writes a commit message. You fill nothing in: you apply it, and it stays in effect while you work on something else.
A persona is a working role — a support agent, a bid writer — that already knows which playbooks to load and when. If your team built one, start there instead of picking playbooks yourself.
You probably do not have to come back to this website
That is the part most people miss. Playbooks are built to reach you where you already work:
In your browser. The sqemes extension puts your playbooks inside ChatGPT, Claude and Gemini, without switching tabs.
In sqemes Chat, here in the webapp, using whichever AI provider your team connected.
In Claude Code, Cursor, Codex and anything else that connects over MCP.
Your team may have set up only one of these. It is worth asking which one before you go looking.
What you can and cannot do
Most invited colleagues get the member role. As a member you can use every playbook and persona you have been given access to, and you can create your own MCP connection for your own tools. You cannot create or edit playbooks, manage the team, or touch the workspace's AI provider keys. If you want to write a playbook, ask an admin to make you an editor.
One thing that confuses people: the setup wizard your admin saw when the workspace was created does not appear for you. Nothing is broken. It exists for the person configuring a workspace, not for the people joining one.
Is it actually worth your time?
Honestly, that depends on whether you repeat work.
It helps when several people do the same kind of AI task and the result should not depend on who happened to do it — support replies, offers, release notes, code review. Someone already worked out the good version; you get to use it instead of rebuilding it.
It helps much less when your AI use is one-off exploration, or when you are the only person who does a task and you are already happy with how you do it. Something is worth writing down as a playbook when a second person needs it, or when the first person needs it a second time. If neither is true yet, an ordinary chat is the right tool and nobody will mind.
Five minutes, if you want to try it
Open Playbooks in the sidebar and read one. Read, not run — you will see straight away whether your team wrote something real or something generic.
Ask the colleague who invited you which of the three places above they set up.
Run one playbook on a piece of work you actually have today, not on a test case.
Updated 27 September 2026 · Article version 1