Agent skill · software engineering · jeremylongshore
canva-upgrade-migration
Plan and verify a Canva Connect contract upgrade from pinned OpenAPI and changelog evidence. Use when endpoints, scopes, enums, validation, deprecations, or preview behavior change. Trigger with: "upgrade Canva API", "Canva breaking change", "diff Canva OpenAPI".
Why this skill is useful
Adds specific migration scripts and API change detection patterns for the Canva Connect API that the AI wouldn't reliably generate on its own.
What it needs
Requires git, npm 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 Contract Upgrade Overview Canva uses date-based Connect API versions while the path v1 is an epoch marker. Preview features may change without a new version, so upgrade evidence must include feature status and live protected checks. Prerequisites Current OpenAPI/checksum, generated code, and deployment version Target OpenAPI/changelog and affected operation inventory Compatibility suite, migration owner, rollout window, and rollback Instructions Step 1: Freeze both contracts Use Read and Grep to record exact source URLs, retrieval times, bytes/checksums, API version metadata, generator version, and current deployed artifact. Step 2: Classify the diff Review endpoints, methods, scopes, required inputs, validation, enums, response requiredness, error/status behavior, deprecations, and preview changes. Step 3: Map consumers Find adapters, schemas, fixtures, policies, UI assumptions, queues, data stores, metrics, and runbooks that depend on each changed fact. Step 4: Build compatibility Use Write or Edit to update code and add old/new fixtures for success, error, unknown additive fields, changed enums, async states, redaction, and rollback. Step 5: Protect authorization Treat any scope or capability change as an authorization migration requiring portal configuration and possibly fresh user consent; never silently broaden. Step 6: Roll out gradually Ship an immutable feature-flagged artifact to a protected environment, run mocked plus read-only live evidence, then expose a bounded cohort under local thresholds. Step 7: Reconcile and close Roll back on drift, preserve job/resource identity across versions, remove deprecated code after the window, and record exact evidence and residual preview risk. 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-upgrade-migration