Agent skill · data analytics · jeremylongshore
miro-debug-bundle
Design and implement a repository-side Miro diagnostic-bundle workflow with bounded metadata and automatic redaction. Use when escalating a Miro failure. Trigger with \"build Miro debug bundle\".
Why this skill is useful
Adds an executable script that automates the collection of Miro API diagnostic information, which is not readily available in public documentation.
What it needs
Requires curl, jq 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 Redacted Debug Bundle Overview Create evidence useful to maintainers or Miro support while excluding credentials, authorization codes, board content, personal data, and unrestricted configuration; use the evidence produced here to make the next decision explicit and reviewable. Prerequisites Incident identifier and narrow UTC window Approved evidence destination and retention period Known redaction rules for identifiers, URLs, headers, and payloads 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 Safe evidence includes versions, operation names, status/code, latency, rate headers, counts, hashes, and timestamps. Authorization headers, cookies, tokens, client secrets, callback query strings, and raw board payloads are never safe evidence. Access-token context is useful only after user/team identifiers are pseudonymized. Official status evidence should include observation time because incidents 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. Define the incident window, failing operations, recipient, purpose, and retention. 2. Collect repository version, deployment version, app mode, safe configuration names, and dependency lock facts. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/miro-debug-bundle--99deda