From ciao
List or read QA playbooks for a Ciao project. Use when the user asks "what playbooks does X have", "show me the login flow playbook", "what are we testing on X".
How this skill is triggered — by the user, by Claude, or both
Slash command
/ciao:ciao-playbooksThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Lists or reads QA playbooks (reusable agent recipes with markdown brief +
Lists or reads QA playbooks (reusable agent recipes with markdown brief + acceptance criteria + optional browser recordings).
source "$CLAUDE_SKILL_DIR/../../lib/ciao-api.sh"
# Workspace-wide
RESPONSE="$(ciao_api list_playbooks)"
# Or filtered to one project
PROJECT_ID="$(ciao_resolve_project "$user_project_hint")"
RESPONSE="$(ciao_api list_playbooks "$(jq -n --arg pid "$PROJECT_ID" '{project_id: $pid}')")"
Shape: { "playbooks": [ { id, name, description, mode_id, project_id, ... } ] }.
RESPONSE="$(ciao_api get_playbook "$(jq -n --arg id "$PLAYBOOK_ID" '{playbook_id: $id}')")"
Returns the full playbook (body, criteria, params_schema) plus linked recordings with their role and ordinal.
For lists, just names + descriptions. For a single playbook, show:
Do not dump JSON. Translate to readable prose.
/ciao-playbook-create403 Missing required scope: playbooks:read → re-mint the PATnpx claudepluginhub desygner/cc-marketplace --plugin ciaoProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.