Agent skill · software engineering · jeremylongshore
miro-migration-deep-dive
Plan and implement a reversible client migration from v1 widgets and relationships to v2 item endpoints with translation and shadow comparison. Use when modernizing a legacy Miro REST integration. Trigger with \"miro v1-to-v2 resource migration\".
Why this skill is useful
Adds executable scripts for migrating Miro boards, including API interactions and data handling that are not publicly documented.
What it needs
Requires npm installed locally. Requires miro account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Miro v1-to-v2 Resource Migration Overview Modernize legacy resources without changing OAuth unnecessarily or flattening distinct v2 item schemas; use the evidence produced here to make the next decision explicit and reviewable. Prerequisites Approved Miro application, tenant, and board scope Current repository and deployment evidence Named owner, success criteria, and rollback or recovery boundary 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 OAuth /v1/oauth is outside the resource migration. v2 replaces generic widgets with item-type endpoints. Connection objects became direct actions such as sharing. Several collections changed from offset to cursor pagination. 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 v1 endpoints, widgets, connections, pagination, timestamps, and consumers. 2. Map each operation to official v2 behavior and record no-equivalent cases. 3. Build typed translators retaining IDs, types, relationships, and unsupported fields. 4. Run v1/v2 shadow reads and compare normalized semantic state. 5. Canary bounded writes with read-after-write and rollback. 6. Cut over incrementally and remove v1 resource code only after retained evidence. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/miro-migration-deep-dive