Agent skill · data analytics · jeremylongshore
miro-observability
Design and implement repository-side Miro instrumentation with safe metrics, rate-credit headers, semantic outcomes, and actionable alerts. Use when operating a Miro integration. Trigger with \"monitor Miro integration\".
Why this skill is useful
Adds executable scripts for Prometheus metrics and OpenTelemetry traces specifically tailored for Miro API integrations.
What it needs
Requires prom-client 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 Integration Observability Overview Observe vendor transport and business correctness without turning board content, credentials, or high-cardinality identifiers into telemetry; use the evidence produced here to make the next decision explicit and reviewable. Prerequisites Service objectives and supported user journeys Operation, retry, queue, reconciliation, and token lifecycle map Approved telemetry fields, retention, access, and alert owners 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 Rate responses expose limit, remaining, and reset credit headers suitable for gauges and forecasts. HTTP success alone does not prove a mutation or synchronization outcome; semantic reconciliation needs separate signals. Miro's public status is a dependency clue, not proof that a local authorization or tenant issue is vendor-wide. Board names, item content, resource URLs, tokens, and raw user/team IDs should not be metric labels or logs. 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. Define SLIs for availability, latency, errors, credits, queue age, token refresh, reconciliation lag, and semantic drift. 2. Instrument adapters with bounded operation names, status classes, retry decisions, and redacted tenant hashes. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/miro-observability