Agent skill · software engineering · jeremylongshore
miro-webhooks-events
Design and implement a repository-side replacement for retired Miro REST webhooks using explicit freshness requirements, bounded reconciliation, or in-board Web SDK events. Use when designing Miro change detection. Trigger with \"Miro webhooks\".
Why this skill is useful
Provides specific commands and patterns for integrating Miro's webhook API that the AI wouldn't reliably generate on its own.
What it needs
Requires express 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 Eventing Gap and Supported Alternatives Overview Prevent new systems from depending on Miro's discontinued experimental webhook infrastructure. Select an alternative that honestly represents durability and freshness; use the evidence produced here to make the next decision explicit and reviewable. Prerequisites Event use case, consumers, and freshness/loss tolerance Current REST and Web SDK capability inventory Authorized boards, rate budget, and reconciliation state store 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 Miro discontinued experimental REST webhooks and /v2-experimental/webhooks/boardsubscriptions. There is no current production Miro REST callback/signature contract documented as its replacement. Web SDK UI events such as items:create and items:delete run in active board app contexts; they are not durable server-to-server delivery. experimental:items:update remains experimental, and items:create does not fire for copy-paste or duplication. 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 every retired subscription call, callback handler, signature assumption, queue, and downstream consumer. 2. Define required freshness, completeness, replay, ordering, and active-board assumptions. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/miro-webhooks-events