// Author lionagi playbooks — reusable YAML workflow templates that define parametric agent tasks. Playbooks live at ~/.lionagi/playbooks/ and run via li play <name>. Use when: creating reusable workflows, parameterizing agent tasks, or setting up repeatable pipelines.
| name | playbook |
| description | Author lionagi playbooks — reusable YAML workflow templates that define parametric agent tasks. Playbooks live at ~/.lionagi/playbooks/ and run via li play <name>. Use when: creating reusable workflows, parameterizing agent tasks, or setting up repeatable pipelines. |
| allowed-tools | ["Bash","Read","Write","Glob","Grep"] |
A playbook is a .playbook.yaml file that defines a reusable, parametric agent
workflow. Install in ~/.lionagi/playbooks/ and invoke with
li play <name> "<prompt>", which expands to li o flow -p <name> "<prompt>".
name: hello
description: Greet and answer a question.
model: claude-code/sonnet-4-6
prompt: |
You are a patient teacher. Explain the following topic in plain language,
with one concrete example.
Run: li play hello "what is a monad?"
The positional text is appended to the prompt with a blank line because the
template contains no {input} placeholder. That is the only behaviour difference
from a template that declares {input} explicitly.
<name>.playbook.yaml~/.lionagi/playbooks/name: matches the filename stem exactlydescription: is one clear sentencemodel: or agent: is set (both is allowed; agent provides the profile, model overrides the model)prompt: references only declared args keys and optional {input}args entry has type, default, and helpargs:team_mode and team_attach are not both setworkers is 1–32 if set; max_ops is 0–50 if setli o flow -p <name> --dry-run "test prompt" plans without executingli play <name> --help lists your custom flags (if argument-hint is set)| File | Contents |
|---|---|
field-reference.md | Complete field table, args schema, template interpolation rules, team semantics, reserved names, pitfalls, source code reference |
examples.md | Three annotated example playbooks (minimal, audit, pr-review) plus the examples directory index |
patterns.md | Orchestration patterns and advanced composition strategies |
Systematic debug workflow: research → orchestrate agents → escalate. Suggest when: stuck after 2-3 attempts, unfamiliar tooling, tempted to "try random things", or errors don't match documentation.
Plan and execute multi-agent workflows using lionagi's CLI: li o flow (DAG pipelines), li o fanout (parallel workers), and li play (playbook invocations). Use when a task needs multiple agents working in parallel or staged phases.
Multi-perspective PR review procedure. Plan a minimal DAG of specialists scoped to what the PR actually touches, synthesize with a critic, post ONE consolidated comment per verbosity tier. Pull before any structured PR review so the methodology stays consistent.
General-purpose code review checklist. Use when reviewing any code change without a narrower specialization. Complements security-review, pr-review (multi-perspective), and the other review skills — pull this when you need the standard correctness/quality rubric without a specific angle.
Threat-model rubric for a focused security review of a code change. Use when reviewing auth / input validation / crypto / secrets / supply chain, or as the "security" dimension of a multi-perspective PR review. Pull this skill before starting so severity calibration and coverage stay consistent.
Orchestrate multi-play shows: decompose a complex goal into sequential plays (each a li play invocation), gate each output for quality, adapt the plan based on results, and merge work into an integration branch. Shows are first-class entities in Lion Studio with dedicated UI at /shows.