--- name: miro-core-workflow-a-fd86dcd9ef76 description: "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\"." argument-hint: "[board-id] [requested-change]" allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit version: 1.9.0 author: Jeremy Longshore license: MIT tags: - saas - miro - boards - items - writes model: inherit effort: high compatibility: Designed for Claude Code; live work requires an authorized Miro app and redacted evidence --- # 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. Re-read affected IDs and compare normalized desired versus observed state. 6. Return a redacted receipt and rollback outcome; never retry an ambiguous write blindly. ## Approval Boundaries Require explicit approval for board creation/deletion, sharing changes, member changes, or deleting/replacing existing items. Do not infer a target from a board name alone. Pause when the responsible owner or exact target is uncertain. ## Output Return board/team confirmation, planned and applied counts by item type, credit estimate, reconciliation result, rollback handle, and exceptions. State what was not inspected or changed so the receipt cannot overclaim coverage. ## Error Handling | Condition | Response | |---|---| | 409 conflict | Re-read state, recompute the plan, and request approval if intent changes. | | Ambiguous timeout | Search or re-read by known IDs/markers before retrying. | | Bulk create fails | Treat the operation as uncommitted, then verify before any replay. | | Permission changed mid-run | Stop remaining writes and preserve completed-action evidence. | ## Examples The example is a redacted operator receipt; identifiers are hashes or bounded labels, not board content or credentials. ```text board=hash:8d2; create=6; update=2; delete=0; estimated-credits=800; reconciled=8/8; rollback=ready ``` ## Resources - [Skill-specific official documentation](references/official-docs.md) - [Create items in bulk](https://developers.miro.com/reference/create-items) - [Create board](https://developers.miro.com/reference/create-board-1) --- Source attribution: jeremylongshore Original project: https://github.com/jeremylongshore/claude-code-plugins-plus-skills/blob/ab85a061f7bcc039dac13ee193de7a4cd4388571/plugins/saas-packs/miro-pack/skills/miro-core-workflow-a/SKILL.md License: MIT License information: https://opensource.org/license/mit Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice MIT License Copyright (c) 2025 Jeremy Longshore Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. # Mega AI Hub resource metadata Creator / publisher: jeremylongshore Original project: https://github.com/jeremylongshore/claude-code-plugins-plus-skills/blob/ab85a061f7bcc039dac13ee193de7a4cd4388571/plugins/saas-packs/miro-pack/skills/miro-core-workflow-a/SKILL.md Attribution basis: Source repository record Fields of work: Design, Product Management, Project & Program Management Roles: Product Manager, Project Manager, UX Designer Specialties: API Tools: Miro Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 8041fc38bba708b8b1f05ab9dd1bc56d42fb907e7fbb90e7a68ef70442d79bb4