Agent skill · software engineering · jeremylongshore
miro-sdk-patterns
Choose and implement Miro Node client or raw REST adapter patterns with typed boundaries, pagination, tenant isolation, and explicit operator commands. Use when designing a Miro API adapter. Trigger with \"review Miro SDK pattern\".
Why this skill is useful
Provides production-ready patterns and TypeScript examples for using the Miro API, which the AI wouldn't reliably generate on its own.
What it needs
Requires @mirohq/miro-api installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Miro Client and Schema Patterns Overview Keep vendor transport details behind a narrow adapter so auth rotation, response drift, retries, and test doubles stay independently verifiable; use the evidence produced here to make the next decision explicit and reviewable. Prerequisites Runtime and deployment constraints Required REST operations and response schemas Official client version or pinned OpenAPI contract 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 @mirohq/miro-api is Miro's official Node.js client for REST API v2. Miro manages OAuth-oriented flows and storage; MiroApi represents an access-token-bound API client. Collection helpers can be asynchronous iterators; callers must preserve pagination and bounded termination. Official examples simplify storage and sessions; production adapters must supply durable tenant-bound implementations. 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. Inventory current HTTP/SDK calls, token lookup, retries, pagination, and response assumptions. 2. Choose raw REST when protocol control is required or the official client when its surface is verified and sufficient. 3. Expose domain operations through an adapter that accepts tenant context rather than raw credentials. 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/miro-sdk-patterns