What is sqemes?

A team's AI know-how, written down once and reused everywhere it already works with AI — and an honest list of what sqemes is not.

For: everyone. Start here if you have just arrived and nothing else makes sense yet.

sqemes is where a team keeps the way it works with AI, so that it can be reused instead of retyped. The good version of a task — the wording that actually produces a usable offer, the rules your replies have to follow, the tone your company writes in — exists somewhere already, usually in one person's head or one person's chat history. sqemes is the place it lives instead, and the mechanism that puts it back in front of whoever needs it.

The three things there are

  • A prompt is what to do — a task with gaps you fill in, like {{customer_name}}.

  • A skill is what to know — a block of company knowledge you apply alongside whatever you are doing, and that stays in effect while you do it.

  • A persona is who to be — a working role that already knows which of the above to load, and when.

Prompts and skills are the two kinds of playbook. A persona is not a third kind; it sits above them and composes them.

Three places to use them, and you pick

The point is not that people come to this webapp. It is that the playbooks reach them where they already are:

  • The browser extension — your playbooks inside ChatGPT, Claude and Gemini.

  • sqemes Chat — in the webapp, with an AI provider you connect.

  • The MCP server — Claude Code, Claude Desktop, Cursor, Codex and anything else that speaks MCP.

Most teams use one or two of these, not all three. Which ones are set up is a decision your admin made during setup, and it can be changed later.

What sqemes is not

Worth saying plainly, because each of these is something people arrive expecting:

  • Not an AI model. sqemes does not generate anything by itself. It uses the models you connect, or the credits included in your plan.

  • Not a replacement for ChatGPT or Claude. If your team uses the extension, you keep using exactly the tools you use now; sqemes adds a shelf next to them.

  • Not an automation tool. There are no triggers, no schedules and no chains of steps that run on their own. A playbook is something a person reaches for.

  • Not useful for one-off work. Something earns a place here when a second person needs it, or the first person needs it a second time. Below that threshold an ordinary chat is the better tool, and using one is not a failure to adopt anything.

Where to go from here

If a colleague added you: Someone added me to a sqemes workspace. If you are setting a workspace up: I am setting up a new workspace. What do I do first? If you want the difference between the two kinds of playbook in detail: What is a playbook — and what is the difference between a prompt and a skill?

Updated 27 September 2026 · Article version 1

Did this answer your question?
😞
😐
😁