A playbook runs inside your own AI coding tool: its skills are instructions the agent follows, and its MCP servers are programs or services the agent can call. That is why nothing is published here before a person has read it.
Anyone who signs in can share a playbook. Before it reaches the catalog:
Every later change goes through the same steps. The published version stays as it is until the new one is approved.
PlaybookRun's own playbooks are put together by its team, mostly from skills that the owners of a technology publish themselves. The files are copied unchanged from their source, scanned and read before publishing, and each skill links to the repository it came from.
The playbook page lists every published version with what changed.
Review lowers risk; it does not remove it. Read a playbook's files on its page before you install it, above all its MCP servers and any hooks, which run on your machine. A remote MCP server can change what it does after it was reviewed.
Signed-in readers can suggest a skill or an MCP server for a playbook on its page. New content is scanned like everything else, and nothing is added until a PlaybookRun admin, or the author of a community playbook, has read and accepted it. A community playbook's author adds it to their draft, which is reviewed before it is published.
Open the playbook, go to Review and choose Report this playbook. Say which skill or file is the problem and what it does. An admin reads every report and answers in your notifications.
A playbook is removed from the catalog and from the marketplace repository when it harms the people who install it, hides what it does, pretends to be from someone else, or shares content its author has no right to share. Its author is told why and can fix it and submit it again. Removing it here does not uninstall it from tools that already have it: remove the plugin in your tool as well.