Back to skill
Skillv1.0.5
ClawScan security
Miro CLI · ClawHub's context-aware review of the artifact, metadata, and declared behavior.
Scanner verdict
SuspiciousMar 14, 2026, 3:52 PM
- Verdict
- suspicious
- Confidence
- medium
- Model
- gpt-5-mini
- Summary
- The skill is a plausible CLI wrapper around an external npm package (mirocli) and its helper scripts are consistent with that purpose, but the package/manifest has mismatches about credentials and relies on an external npm package that you must trust—review before installing.
- Guidance
- This skill is a wrapper around an external npm tool (mirocli). Before installing: 1) Verify the npm package and GitHub repo (review source, recent commits/issues, and maintainer reputation). 2) Prefer testing in an isolated environment or container and with a non-production Miro account. 3) Understand that npm install -g executes package install scripts—avoid installing globally on sensitive machines until reviewed. 4) Confirm where mirocli stores tokens (~/.mirocli and system keyring) and inspect that directory after first run. 5) Ask the skill publisher to correct the manifest to list required credentials (org id, client id, client secret) so the metadata matches the runtime instructions. If you cannot or do not want to trust a third-party npm binary with your Client Secret, do not install this skill.
Review Dimensions
- Purpose & Capability
- concernThe SKILL.md clearly requires OAuth credentials (org id, client id, client secret) and documents interactive credential setup, which aligns with the stated Miro CLI purpose. However the registry metadata lists no required environment variables or primary credential, creating a manifest/metadata mismatch that is unexplained.
- Instruction Scope
- okRuntime instructions and helper scripts only call the external mirocli binary, jq, and standard shell tools; they instruct interactive OAuth setup and store secrets via the external tool's system keyring. The instructions do not read unrelated system files or post data to unexpected endpoints.
- Install Mechanism
- noteInstallation uses an npm package (davitp/mirocli) which is a public community package (moderate risk). There are no ad-hoc downloads from unknown servers. npm install -g runs maintainer-provided install scripts—verify the package source and recent activity before installing globally.
- Credentials
- concernThe skill requires OAuth credentials per SKILL.md (Client ID/Secret, Org ID) but the skill's declared registry requirements list no required env vars or primary credential. The credential handling is delegated to the external binary (mirocli) and said to be stored in the system keyring, but the manifest should explicitly declare the credential requirements to match the instructions.
- Persistence & Privilege
- okThe skill is not always-enabled and does not request elevated platform privileges. It does recommend installing a global npm binary (which writes to system/global npm locations) and suggests adding the scripts directory to PATH—both are normal but worth caution.