Your library
SkillsYour company's knowledge, loaded where neededPersonasRoles that know what to loadPromptsThe tasks you repeat, ready to fill inGovernanceWho sees, who edits, review, versionsUse it in
Browser extensionPlaybooks inside ChatGPT, Claude, Geminisqemes ChatAny provider you connect, with personasMCP serverClaude Code, Cursor, Codex and more
Probably AI-generatedSee it in Claude CodeHow an agent finds and loads a skill
By team
MarketingOne brand voice in every toolSalesYour best messaging in every replyEngineeringStandards your agents can followProductProduct context you can build onSupportOne source of truth for every answerOperationsRecurring work, actually repeatableBy role
Team leadsShared playbooks, clear rightsEnterpriseSelf-host or a dedicated instancePartnersFor agencies and implementers
Probably AI-generatedOne library, every teamHow teams share playbooks
Decide who sees and who edits each playbook, let changes wait for your approval and restore any version. Your team's know-how stays in one place, even when people change.
Probably AI-generatedReview (2) · waiting for you
So the team can rely on it, and nobody has to ask which version is right.
Rights
Restrict a playbook to named people and groups or keep it to yourself, and decide separately who may edit it. Admins do not get automatic sight of restricted playbooks.
How governance works
Probably AI-generated
Who can see "Hiring plan"
Everyone in the workspace
Only meSelected
Review
Switch on review, and an editor's change to a shared playbook becomes a proposal. The team keeps working with the released version until you release or reject the change.
Probably AI-generated
Review (2)
Brand voice · change by TomRelease
Event recap · by MiraRelease
Usage
The Overview shows the most used playbook in each channel over the last seven days. It never shows who used it.
Probably AI-generated
Last 7 days
Brand voiceMost used in Chat
Release notesMost used over MCP
One library
Shared playbooks live in the workspace, not in one person's chat history. A new colleague starts from the same library on the first day.
Probably AI-generated
Team library
SkillsShared
PromptsShared
PersonasShared
Keep the library in shape without becoming its bottleneck.
Everyone, named people and groups, or only you, per playbook.
Separate from who sees, with a default for everything new.
Let new playbooks and changes to shared ones wait for review.
Every change is kept; go back at any time.
How often each playbook is used per channel, never by whom.
The Setup Wizard and the marketplace give new teams a first library.
What team leads ask.