Agent skill · software engineering · jeremylongshore
miro-hello-world
Design and implement a bounded, read-only Miro connectivity probe that proves authorization context before writes are enabled. Use when smoke-testing a new Miro integration. Trigger with \"test Miro connection\".
Why this skill is useful
Provides specific commands and patterns for interacting with the Miro REST API v2 that the AI wouldn't reliably generate on its own.
What it needs
Requires @mirohq/miro-api 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 Read-Only Connection Probe Overview Run the smallest useful REST probe and produce a redacted receipt. A successful HTTP response is insufficient unless tenant and scope context also match; use the evidence produced here to make the next decision explicit and reviewable. Prerequisites An approved OAuth installation with boards:read Expected team and user context A test board or permission to list board metadata 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 GET https://api.miro.com/v2/boards requires boards:read. Filtering by teamid or projectid is indexed immediately; other search filters can lag by several seconds. Board-list responses are paginated and must not be treated as a complete inventory from one page. Response bodies can contain confidential names, descriptions, owners, and links. 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. Inspect the integration configuration without reading credential values. 2. Confirm token context and expected team before querying board resources. 3. Request one bounded board page filtered to the approved team when available. 4. Record status, latency, rate-limit headers, page size, and only redacted board identifiers. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/miro-hello-world