Agent skill · software engineering · jeremylongshore
miro-multi-env-setup
Design and implement repository-side isolation for Miro development, staging, and production apps, redirects, token references, teams, and boards with hard guards. Use when configuring multiple environments. Trigger with \"miro multi-environment isolation\".
Why this skill is useful
Adds specific configuration patterns and OAuth management for Miro API that the AI wouldn't reliably generate on its own.
What it needs
Requires aws, gcloud, vault 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 Multi-Environment Isolation Overview Make environment confusion detectable before a request leaves the process; 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 Each app has independent identity, redirects, scopes, token mode, and installations. Access-token context must match the intended tenant. Production credentials never belong in local or preview environments. Token-expiration mode can differ because it is fixed at app creation. 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. Build an environment matrix of app hash, redirects, token mode, scopes, team, boards, store, and owner. 2. Fail startup on missing, duplicated, or inconsistent mappings. 3. Resolve credentials only through each environment's approved server-side reference. 4. Assert token context before enabling operations. 5. Test that production identifiers cannot appear in lower-environment config. 6. Exercise rotation, revocation, promotion, and rollback per environment. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/miro-multi-env-setup