Agent skill · software engineering · jeremylongshore
miro-prod-checklist
Audit repository readiness for a fail-closed Miro production release across authorization, data, resilience, rollback, and an approval-gated live handoff. Use when preparing to enable a Miro integration in production. Trigger with \"ship Miro integration\".
Why this skill is useful
Adds executable scripts and detailed procedures for deploying Miro integrations, including OAuth configuration and error handling that are not commonly found in public documentation.
What it needs
Requires bash, curl, grep 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 Production Readiness Gate Overview Turn production approval into an evidence-backed decision bound to one immutable release and app configuration; use the evidence produced here to make the next decision explicit and reviewable. Prerequisites Immutable release candidate and deployment manifest Production app/team ownership and approved scopes Test, observability, incident, rollback, and data-handling evidence 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 Production REST uses v2 resource endpoints and OAuth under /v1/oauth. Experimental features are not production contracts and must be isolated behind explicit risk acceptance. Rate capacity is credit-weighted and must include all callers for a user/application pair. Miro service status, token revocation, and tenant mismatch need operational responses before launch. 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. Bind the review to release SHA, dependency lock, app ID hash, scopes, redirect URIs, and environment. 2. Verify tenant isolation, expiring-token rotation, revocation, least privilege, and redaction controls. 3. Run unit, contract, bounded live-read, failure, rate, rollback, and recovery tests. 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/miro-prod-checklist