Agent skill · marketing growth · jeremylongshore
miro-incident-runbook
Plan and implement repository-side containment and recovery controls for Miro authorization, capacity, outage, and data-correctness incidents, with approval-gated live actions. Use when responding to a Miro service incident. Trigger with \"Miro incident\".
Why this skill is useful
Adds executable scripts for Miro incident response that automate triage, mitigation, and recovery processes not found in public documentation.
What it needs
Requires bash, curl, jq 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 Integration Incident Response Overview Stabilize user impact before changing authorization or replaying writes. Keep an UTC action log and make ambiguity explicit; use the evidence produced here to make the next decision explicit and reviewable. Prerequisites Incident commander, owners, severity, and affected window Current deployment, app/team context, dashboards, and safe logs Write-disable, circuit-breaker, reconciliation, and rollback controls 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 401, 403/404, 409, 429, network, and 5xx failures require different containment. One refresh attempt is safe only when serialized against rotating token storage. 429 recovery follows observed reset headers and shared credit demand. Timeout/5xx on a mutation is ambiguous until target state is reconciled. 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. Declare incident scope, commander, severity, start time, affected tenants/operations, and change freeze. 2. Contain with write disablement, queue pause, concurrency reduction, or circuit opening appropriate to evidence. 3. Correlate deployment changes, token events, rate headers, semantic drift, and official Miro status. 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/miro-incident-runbook