Get Started

Playbooks

Discover a Playbook through MCP and apply it in the runtime.


  1. Read the teams resource when workspace context matters.
  2. Use epismo_playbook_resource_list when a resource kind can narrow the discovery space.
  3. Find candidates with epismo_playbook_search; pass resourceKind and resourceRef together for a resource-filtered list, or use a text query instead.
  4. Read the latest Definition with epismo_playbook_get, which also returns the Playbook's open Suggestions, recent Versions, and aliases in the same read (free for a Public Playbook, 1 credit otherwise).
  5. Pin reproducible work with epismo_playbook_version_get.
  6. Validate input and adapt Steps into the agent runtime's plan.

A Step is not a Task. The agent may omit, combine, or reorder Steps. Resource hints are candidates, not installation commands; check permission, trust, and credentials before use.

Use epismo_playbook_create, epismo_playbook_version_publish, and the Draft tools to author Playbooks. Use epismo_playbook_access_get and epismo_playbook_access_set for visibility and explicit editors. Public grants published read access only; editors can edit content. An owner manager can archive a Playbook or a historical Version with epismo_playbook_version_archive; the latest Version cannot be archived.

An authoring surface iterates through a Draft instead of publishing every attempt: epismo_playbook_draft_save to save (with baseRevision, not an idempotency key), epismo_playbook_draft_get to read it back, and epismo_playbook_draft_publish or epismo_playbook_draft_discard to finish. A Draft follows Playbook edit access; public readers and share links cannot read it.