Agent skill · software engineering · jeremylongshore
miro-core-workflow-b
Design and implement a Miro read-and-reconcile client with cursor-safe pagination, bounded snapshots, and drift reports. Use when syncing or auditing Miro content. Trigger with \"reconcile Miro board\".
Why this skill is useful
Adds specific commands for managing Miro connectors and embeds that the AI wouldn't reliably generate on its own.
What it needs
Requires curl, 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 Board Read and Reconciliation Overview Produce a consistent, bounded view of board state and distinguish indexing delay, pagination defects, and real drift before proposing changes; use the evidence produced here to make the next decision explicit and reviewable. Prerequisites Approved board and team scope OAuth installation with boards:read Field, item-type, pagination, freshness, and redaction requirements 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 Board collection filters other than team/project can have indexing delay. Collection endpoints use cursor pagination where documented; cursor presence, not page fullness, controls continuation. Different item types have distinct v2 schemas and must not be collapsed into a v1 widget shape. Resource URLs and board content are sensitive and may be time-bound or access-controlled. 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. Confirm token context and board ownership boundary. 2. Define item types, fields, page/item ceilings, freshness window, and comparison keys. 3. Traverse documented cursors while detecting repeats and enforcing termination limits. 4. Normalize item-specific fields without discarding type or parent relationships. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/miro-core-workflow-b