Agent skill · operations · jeremylongshore
canva-incident-runbook
Analyze and contain a Canva Connect incident with evidence-led recovery. Use when authentication, design, export, asset, webhook, or provider failures affect users. Trigger with: "Canva incident", "Canva outage", "triage Canva production".
Why this skill is useful
Adds a comprehensive incident response script and decision tree specifically for Canva API outages that the AI cannot generate on its own.
What it needs
Requires bash installed locally. Requires canva account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Canva Incident Response Overview Contain impact before debugging deeply. Distinguish provider status, application release/config, tenant authorization, endpoint throttling, async-job backlog, and preview drift. Prerequisites Incident ID, severity policy, affected operations, and UTC window Current deployment/config revisions and last known good Approved test user, rollback owner, and communications channel Instructions Step 1: Declare and bound Record start time, reporter, user-visible symptom, affected tenants/operations, suspected data exposure, and current severity without copying customer content. Step 2: Contain Pause only unsafe mutations, refresh races, or affected queues. Preserve existing job identity and keep safe read-only paths available when policy permits. Step 3: Check broad signals Use Read and Grep to compare deployment/config changes, error/status trends, queue age, authorization failures, and Canva's official status/changelog. Step 4: Run a minimal probe Use an approved test user for one non-mutating endpoint. Never infer global provider health from a single production user. Step 5: Mitigate and reconcile Roll back the responsible release/config, reduce endpoint concurrency, disable a changed preview path, or reauthorize only affected users based on evidence. Reconcile queued jobs before resuming. Step 6: Close with proof Use Write or Edit to record timeline, decisions, impact, data assessment, recovery evidence, remaining jobs, rollback result, and preventive owner. Authentication Canva Connect calls use Bearer access tokens obtained by a backend through OAuth 2.0 Authorization Code with SHA-256 PKCE. Request explicit least-privilege scopes, keep client secrets and tokens out of browser-visible state, and serialize refresh so the replacement single-use refresh token is stored atomically. Tool Discipline Use Read and Grep for discovery and evidence. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/canva-incident-runbook