play
/play
Run an existing lionagi playbook through the orchestration MCP server and retrieve its background result. Use when a saved `.playbook.yaml` workflow should be executed with concrete input or declared arguments.
- Author
- ohdearquant ↗
- Repository
- lionagi ↗
- Licence
- Apache-2.0
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Run an existing lionagi playbook through the orchestration MCP server and retrieve its background result. Use when a saved `.playbook.yaml` workflow should be executed with concrete input or declared arguments.
Original author description
Run an existing lionagi playbook through the orchestration MCP server and retrieve its background result. Use when a saved `.playbook.yaml` workflow should be executed with concrete input or declared arguments.
How it works
- Required call sequence
- Worked example
- Arguments and planning
- Checkout-local alternative
SKILL.md preview
---
name: play
description: >
Run an existing lionagi playbook through the orchestration MCP server and
retrieve its background result. Use when a saved `.playbook.yaml` workflow
should be executed with concrete input or declared arguments.
allowed-tools: [Bash, Read, Write, Glob, Grep]
---
# Running a Saved Playbook
Use `play.submit` for a playbook that is already installed on the MCP server's
machine. Use the `playbook` skill instead when the file itself needs authoring or editing.
## Required call sequence
1. Ask for the catalog in its own call and confirm `play.submit` is available:
```text
mcp__plugin_orchestrate_lion__request(help=true)
```
2. Ask for the schema with the exact playbook name. A playbook's declared arguments change
the schema, so the catalog marks this fingerprint as varying by `playbook`:
```text
mcp__plugin_orchestrate_lion__request(help={"verb": "play.submit", "playbook": "minimal"})
```
3. Copy that reply's `schema_fingerprint` into the op as a sibling of `args`:
```text
mcp__plugin_orchestrate_lion__request(ops=[
{"op": "play.submit",
"args": {"playbook": "minimal", "prompt": "Explain monads with one example."},
"schema_fingerprint": "<fingerprint from the qualified help call>"}
])
```
Never put `schema_fingerprint` inside `args`. It is not read there, so the server refuses the
op as stale. Do not combine `help` and `ops` in one call; the server refuses that shape too.
## Worked example
This example uses a saved playbook at `~/.lionagi/playbooks/minimal.playbook.yaml`. If it is
not already present, create it first:
```yaml
name: minimal
model: claude
prompt: |
Explain the supplied topic in plain language, with one concrete example.
```
Run the qualified help and submit calls above, then read the returned `run_id`:
```text
mcp__plugin_orchestrate_lion__request(ops=[
{"op": "job.status", "args": {"run_id": "<run_id>"}}
])
```
Repeat `job.status` until the run is terminal, then retrieve its console tail and artifact list:
```text
mcp__plugin_orchestrate_lion__request(ops=[
{"op": "job.output", "args": {"run_id": "<run_id>"}}
])
```
The submit response is only a run id, not the playbook's result. `job.list` finds recent runs;
`job.kill` stops one by `run_id`.
## Arguments and planning
- Read the qualified help schema for every custom playbook argument. Pass each declared
argument directly inside the op's `args`; do not invent another nesting layer.
- Set `dry_run: true` inside `args` to plan without executing workers. The dry run is still a
background job, so inspect it through `job.status` and `job.output`.
- If calling `flow.submit` with a `playbook` instead, use the same qualified-help rule with
`{"verb": "flow.submit", "playbook": "<same name>"}`.
- Multiple ops run in order, but one op returning `ok=false` does not stop its siblings. Check
every op's `ok` field instead of trusting the top-level response alone.
## Checkout-local alternative
Inside a lionagi checkout with `li` on `PATH`:
```bash
li play minimal "Explain monads with one example."
```
Use `li play minimal --help` to see the playbook's declared flags.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · ohdearquant/lionagi | 100 | Apache-2.0 |
| microsoft/Copilot-Managed-Runtime | 95 | MIT |
| microsoft/managed-apps | 95 | MIT |
Database snapshot: 13.11.2026 · package version c776848f9f58 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100playbook
Author lionagi playbooks — reusable YAML workflow templates that define parametric agent tasks. Playbooks live at ~/.lionagi/playbooks/ and run via the `play.submit` MCP verb (or `li play <name>` from a lionagi checkout). Use when: creating reusable workflows, parameterizing… - 100orchestrate
Plan and execute multi-agent workflows through lionagi's orchestration MCP tool: flow.submit (DAG pipelines), fanout.submit (parallel workers), agent.submit (one agent), and play.submit (saved playbooks). Use when a task needs multiple agents working in parallel or staged phases. - 100playbooks
This skill should be used when the user asks "which playbooks apply", "list the plays", "add a play", "capture this as a rule", "add this to the playbook", "show my playbook", or when completion offers a note as a play and the person says yes. It lists the plays from the… - 95workflow
Run a multi-step skill workflow declared in a workflow YAML file. Use when the user asks to "run the workflow at <path>", "execute workflow <name>", "run the <name> workflow", "chain these skills", "compose <skill-a> and <skill-b>", or supplies a path to a `.yaml` workflow… - 90dev10x:playbook-maintenance
Review user playbook overrides against current defaults to detect drift. Identifies new steps, improved prompts, updated fragments, and structural changes in defaults that overrides have missed. Presents findings with recommendations and delegates edits to dev10x:playbook.… - 100playbook-format
The file contract for a brain playbook (phases, playbook.md, brief.md) and the rules that make one actually run. Use when writing, reviewing or repairing a playbook, or when brain could not read one.