From ciao
Trigger a Ciao QA playbook run. Use when the user asks "run the login flow playbook", "kick off the smoke test on X".
How this skill is triggered — by the user, by Claude, or both
Slash command
/ciao:ciao-playbook-runThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Starts a playbook execution. The playbook's mode (e.g. `qa-buddy`) opens
Starts a playbook execution. The playbook's mode (e.g. qa-buddy) opens
a session, the agent reads the brief + criteria, runs the linked
recordings, and reports a verdict.
source "$CLAUDE_SKILL_DIR/../../lib/ciao-api.sh"
PAYLOAD="$(jq -n \
--arg sid "$AGENT_SESSION_ID" \
--argjson params "${PARAMS:-{}}" \
'{agent_session_id: $sid, params: $params}')"
RESPONSE="$(ciao_agent_post "/playbooks/$PLAYBOOK_ID/runs" "$PAYLOAD")"
Returns the playbook body, criteria, and the run id. The caller is expected to attach a WebSocket and send the first prompt — but the CLI flow stops at "run registered." Report the run id and a browser link.
If the playbook has runtime parameters (params_schema is non-empty), the
form rendering belongs in the browser. Resolve the workspace slug with
ciao_workspace_slug and link the user to the QA dashboard at
https://app.ciao.dev/w/$WS_SLUG/qa/playbooks. The CLI is best for
parameterless playbooks.
403 Missing required scope: playbooks:run → re-mint the PAT404 playbook not found → bad id, list playbooks first400 agent_session_id required → the run needs an existing session;
spawn one with /ciao-handoff first, then chain the runProvides 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.
npx claudepluginhub desygner/cc-marketplace --plugin ciao