Agent skill · data analytics · jeremylongshore
miro-common-errors
Diagnose Miro OAuth and REST failures from status, context, scopes, rate headers, and safe evidence. Use when a Miro integration returns errors. Trigger with \"debug Miro API error\".
Why this skill is useful
Provides specific troubleshooting commands and error handling patterns for Miro API that the AI wouldn't reliably generate on its own.
What it needs
Requires 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 API Error Diagnosis Overview Classify the failing layer before changing code or credentials. Preserve the response status, safe error code, request timing, and tenant context without retaining board content; use the evidence produced here to make the next decision explicit and reviewable. Prerequisites Failing operation and sanitized response metadata Expected user, app, team, board, and scopes Deployment and token-mode context 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 generally indicates missing, invalid, expired, or revoked authorization; one refresh attempt is the safe ceiling. 403/404 can represent scope, membership, role, plan, resource, or tenant-boundary failures. 409 means current state conflicts with the requested mutation and requires a re-read. 429 responses must be handled from rate-limit headers; 5xx and network failures do not prove a write was absent. 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. Reproduce once with the smallest safe request and capture status, safe code, timing, and rate headers. 2. Verify URL, method, API version, token context, required scope, plan, and resource ownership. 3. Separate authorization, validation, conflict, throttling, vendor, and network hypotheses. 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/miro-common-errors