Agent skill · software engineering · jeremylongshore
miro-upgrade-migration
Plan and implement a Miro integration upgrade through contract inventory, pinned dependencies, shadow-read design, reversible rollout, and an approval-gated live handoff. Use when changing API or SDK versions. Trigger with \"upgrade Miro integration\".
Why this skill is useful
Adds migration scripts and specific API endpoint changes for Miro's SDK upgrade that the AI wouldn't reliably generate on its own.
What it needs
Requires npm installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Miro Dependency and API Upgrade Overview Treat upgrades as contract changes, not package-only edits. Separate REST major-version migration from client-library and Web SDK lifecycle changes; use the evidence produced here to make the next decision explicit and reviewable. Prerequisites Current and target dependency/API inventory Official changelog, lifecycle, and endpoint references Representative fixtures, sandbox board, and rollback artifact Tool Discipline Use Read, Glob, and Grep to inspect the repository, configuration names, adapters, tests, and evidence. Use WebFetch only for current official Miro documentation. Use Write or Edit after confirming the requested mode, target environment, tenant, board, and approval boundary. These declared tools do not call authenticated Miro APIs or deployment CLIs; implement client, configuration, and test changes, then return exact operator commands or an approval-gated handoff for live execution. Current Contract Miro maintains one recommended production REST major version; current resource work uses v2. OAuth /v1/oauth was not included in the REST v1-to-v2 resource migration. v2 replaced polymorphic widgets with item-type endpoints and changed several relationship and pagination models. Experimental endpoints can change or be removed and cannot silently graduate into a production dependency. Authentication For REST work, use OAuth 2.0 Authorization Code with the narrowest Miro scopes. Bind each encrypted token record to its user, application, authorized team, and granted scopes. Never print access tokens, refresh tokens, client secrets, authorization codes, or board content. Instructions 1. Inventory SDK, raw endpoints, OAuth, scopes, response schemas, pagination, item types, and experimental use. 2. Diff current code against official lifecycle, migration, reference, and pinned package contracts. 3. Build compatibility fixtures and translate one operation at a time behind the adapter boundary. 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/miro-upgrade-migration