miro-migration-deep-dive
Execute major Miro migrations \u2014 migrate boards between teams/orgs,\n\ export board content to external systems, import data into Miro,\nand re-platform\ \ from competing whiteboard tools using REST API v2.\nTrigger with phrases like\ \ \"migrate miro\", \"miro migration\",\n\"export miro boards\", \"import to miro\"\ , \"miro data migration\".\n"
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill miro-migration-deep-dive --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Miro Migration Deep Dive ## Overview Comprehensive guide for migrating Miro boards between teams and organizations, updating from REST API v1 to v2, and re-platforming from competing whiteboard tools (Lucidchart, FigJam). Covers board content export with cursor pagination, bulk import with rate-limit aware queuing, widget API changes between v1 and v2, and the new app framework patterns. Typical
What does the miro-migration-deep-dive skill do?
Execute major Miro migrations \u2014 migrate boards between teams/orgs,\n\ export board content to external systems, import data into Miro,\nand re-platform\ \ from competing whiteboard tools using REST API v2.\nTrigger with phrases like\ \ \"migrate miro\", \"miro migration\",\n\"export miro boards\", \"import to miro\"\ , \"miro data migration\".\n"
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill miro-migration-deep-dive --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
