Miro Management

Manage Miro through the Miro REST API using OAuth 2.0, saved token files, or direct access tokens. Use when the user wants to connect a personal or local Mir...

This skill appears to be a legitimate Miro API helper, but take these precautions before installing or enabling it: 1) Review scripts/miro_api.py (especially the serve-oauth-callback handler) to confirm it binds only to localhost and doesn't send tokens to unexpected endpoints. 2) Know that the skill expects Miro credentials (client ID/secret, redirect URI, or access token) even though the registry metadata doesn't declare them — don't place secrets inside the skill folder; prefer environment variables or a local token file with restrictive filesystem permissions. 3) Ensure you have a Python 3 runtime available; the metadata doesn't declare this dependency. 4) Be cautious with the 'raw' and 'preview-write' commands: they can send arbitrary API requests. 5) If you want to limit risk, require explicit user invocation (do not allow autonomous invocation) or avoid granting long-lived tokens; prefer short-lived or scoped tokens and review token storage location (.miro/tokens.json) for proper permissions. If you want a higher-assurance decision, request the full, untruncated miro_api.py serve-oauth-callback implementation and confirm no network calls target hosts other than miro.com/api endpoints.

Type: OpenClaw Skill Name: miro-management Version: 1.1.0 The miro-management skill bundle is a legitimate tool for interacting with the Miro REST API. It includes a Python script (scripts/miro_api.py) that handles OAuth 2.0 flows, token management, and various board operations (listing, creating, and exporting items) using standard libraries. The instructions in SKILL.md emphasize security best practices, such as keeping secrets outside the skill folder and confirming write actions. The local OAuth callback server is a standard implementation for CLI-based authorization and is restricted to localhost by default.