Agent skill · software engineering · jeremylongshore
miro-deploy-integration
Prepare and verify repository-side deployment configuration for a Miro service with isolated settings, health checks, canaries, rollback, and an approval-gated live handoff. Use when promoting a Miro-backed release. Trigger with \"miro integration deployment\".
Why this skill is useful
Adds deployment scripts and OAuth management for Miro integrations that are not available in public documentation.
What it needs
Requires fly, gcloud, vercel 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 Deployment Overview Promote one immutable artifact while keeping authorization configuration and write enablement separately controlled; use the evidence produced here to make the next decision explicit and reviewable. Prerequisites Approved Miro application, tenant, and board scope Current repository and deployment evidence Named owner, success criteria, and rollback or recovery boundary 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 OAuth redirects must exactly match the environment's Miro app configuration. REST secrets remain server-side and out of Web SDK bundles. A read-only context probe precedes write enablement. Retired experimental webhooks cannot be a health dependency. 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 release to SHA, dependency lock, app hash, scopes, redirects, and environment. 2. Deploy secret references and configuration with Miro writes disabled. 3. Run service health, token-context, and bounded board-read probes. 4. Canary approved tenants against error, latency, credit, and semantic thresholds. 5. Enable writes only after approval and reconcile the first mutations. 6. Exercise rollback and verify all pre-rollback writes. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/miro-deploy-integration