Miro Developer App
AdvisoryAudited by Static analysis on Apr 30, 2026.
Overview
No suspicious patterns detected.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If the agent uses the proxy incorrectly, it could create, change, or delete Miro content or account-related data under the connected user's authority.
The skill exposes a broad authenticated API escape hatch, including mutating and delete methods, without clear limits, path restrictions, or confirmation requirements for high-impact operations.
When the available actions don't cover your use case, you can send requests directly to the Miro Developer App API through Membrane's proxy... `membrane request CONNECTION_ID /path/to/endpoint` ... HTTP method (GET, POST, PUT, PATCH, DELETE)
Use pre-built Membrane actions where possible, require explicit user confirmation before POST/PUT/PATCH/DELETE requests, and only use the proxy for user-specified endpoints and payloads.
Actions run through this skill may operate with the permissions granted to the connected Membrane/Miro account.
The skill requires delegated account access through Membrane and a Miro connection. This is expected for the integration, but it gives the agent authority to act through that connected account.
Membrane handles authentication and credentials refresh automatically... `membrane login --tenant` ... The user completes authentication in the browser.
Connect only the intended Miro account or workspace, review the requested authorization scope during login, and disconnect the integration when no longer needed.
Installing a global CLI adds executable code from npm to the user's environment.
The skill depends on installing an external global npm CLI package. This is central to the integration, but the package/version is not pinned in an install spec.
Install the Membrane CLI so you can run `membrane` from the terminal: `npm install -g @membranehq/cli`
Install the CLI from the official source, consider pinning or reviewing the package version, and keep it updated through trusted package-management practices.