Agent skill · software engineering · jeremylongshore
miro-core-workflow-a
Plan and implement an approval-gated Miro client workflow for board and item mutations with preconditions, bounded batches, and rollback evidence. Use when creating or changing Miro content. Trigger with \"update Miro board\".
Why this skill is useful
Adds executable scripts for full CRUD operations on Miro boards and items using the REST API 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 Governed Board and Item Writes Overview Convert a requested canvas change into an explicit write set. Confirm board identity and permissions before any mutation, then reconcile what Miro actually persisted; use the evidence produced here to make the next decision explicit and reviewable. Prerequisites Approved target board and expected team OAuth installation with only the required board scopes Desired state, ownership, rollback, and collision policy 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 and item writes require boards:write; reads use boards:read. The v2 API exposes item-type endpoints rather than the polymorphic v1 widget model. Bulk item creation accepts at most twenty items, is transactional, and charges Level 2 credits per item. A successful mutation response must be followed by a read when persisted state matters. 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. Resolve token context, team, board, and current permissions; stop on any mismatch. 2. Read the target objects and calculate a deterministic create/update/delete plan. 3. Present counts, affected types, destructive actions, credit estimate, and rollback before writing. 4. Apply the smallest approved operation or a maximum-twenty-item transactional bulk create. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/miro-core-workflow-a