Agent skill · software engineering · jeremylongshore
miro-rate-limits
Design and implement repository-side Miro REST traffic controls from credit weights, supplied headers, bounded queues, and reset-aware retries. Use when preventing or recovering from Miro 429 responses. Trigger with \"Miro rate limit\".
Why this skill is useful
Adds an executable TypeScript script for implementing Miro API rate limiting with exponential backoff and request queuing, which is not commonly found in public documentation.
What it needs
Requires typescript 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 Credit-Budget and Rate-Limit Control Overview Plan capacity in credits rather than raw request count and preserve headroom across every caller sharing a user/application quota; use the evidence produced here to make the next decision explicit and reviewable. Prerequisites Sanitized rate-limit headers and recent 429 history Endpoint inventory with documented credit levels Caller priorities, freshness targets, and retry SLO 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 REST limiting is per user and application with a published global budget of 100,000 credits per minute. Level 1 costs 50 credits, Level 2 costs 100, Level 3 costs 500, and Level 4 costs 2,000 per call. At the global budget those levels correspond to 2,000, 1,000, 200, and 50 calls per minute respectively when used alone. Responses expose X-RateLimit-Limit, X-RateLimit-Remaining, and Unix-epoch X-RateLimit-Reset; published limits are subject to change. 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 users/apps, callers, endpoints, weights, bursts, and retry loops. 2. Capture current headers from bounded authorized requests and validate reset conversion. 3. Model each operation in credits, including bulk-create Level 2 cost per item. 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/miro-rate-limits