Agent skill · software engineering · jeremylongshore
miro-enterprise-rbac
Audit organization, team, board, role, and Enterprise-scope access with plan-aware evidence. Use when reviewing Miro enterprise governance. Trigger with \"miro enterprise access governance\".
Why this skill is useful
Adds executable scripts for managing Miro Enterprise features via REST API that are not commonly known or documented.
What it needs
Requires typescript 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 Enterprise Access Governance Overview Compare intended access with effective plan, app-scope, role, team, and board controls; 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 Enterprise scopes have distinct plan and role availability. v2 team endpoints are Enterprise-only and require an Enterprise-team installation. App scopes and user/admin roles jointly constrain access. Board movement permissions vary by plan and role. 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. Define organizations, teams, boards, apps, identities, roles, and policy in scope. 2. Verify plan and scopes before Enterprise queries. 3. Collect minimum membership/settings evidence with pseudonymized people. 4. Classify excessive, missing, orphaned, conflicting, and unknown access. 5. Prepare but do not apply changes during audit mode. 6. After approved changes, re-read effective access and retain attestation evidence. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/miro-enterprise-rbac