Agent skill · software engineering · jeremylongshore
canva-common-errors
Analyze and classify Canva Connect failures by HTTP status, provider error code, operation, and authorization state. Use when deciding whether to refresh, reauthorize, wait, reconcile, correct input, or escalate. Trigger with: "Canva API error", "Canva 401", "Canva 403 or 429".
Why this skill is useful
Provides specific error handling patterns and API integration techniques for the Canva Connect API that the AI wouldn't reliably generate on its own.
What it needs
Requires curl, jq 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 Error Classification Overview Treat HTTP status alone as insufficient. Use the current endpoint reference and redacted provider error code to separate caller defects, authorization failures, throttling, preview drift, and provider incidents. Prerequisites HTTP status, provider error code, endpoint pattern, and UTC window Opaque request, resource, or job reference without payload content Pinned OpenAPI or endpoint documentation version Instructions Step 1: Capture a minimal envelope Record method, endpoint pattern, status, provider code, terminal job state, retry metadata if actually present, and deployment version. Exclude tokens, bodies, signed URLs, and customer identifiers. Step 2: Handle authentication failures For an invalid or expired access token, serialize the authorized refresh flow and atomically store the replacement refresh token. Reauthorize after revocation or unrecoverable refresh failure. Step 3: Handle authorization failures Compare the operation with explicit granted scopes, resource ownership, capabilities, tenant policy, and preview availability. Never assume a write scope grants its read counterpart. Step 4: Handle throttling Pause only the affected endpoint/user queue. Use documented endpoint metadata and response instructions; otherwise apply bounded exponential backoff with jitter rather than a guessed fixed delay. Step 5: Handle async failures Poll the existing job to a documented terminal state. Correct validation or entitlement errors before any new submission. Step 6: Escalate provider failures Correlate repeated server errors with Canva status/changelog and provide a redacted support receipt after bounded retry is exhausted. Authentication Canva Connect calls use Bearer access tokens obtained by a backend through OAuth 2.0 Authorization Code with SHA-256 PKCE. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/canva-common-errors--a11cc9