Collect Miro REST API v2 diagnostic evidence for support tickets.
Use when encountering persistent issues, preparing support tickets,
or collecting diagnostic information for Miro integration problems.
Trigger with phrases like "miro debug", "miro support bundle",
"collect miro logs", "miro diagnostic", "miro support ticket".
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
Instruções da origem · Visualização somente leitura
name
miro-debug-bundle
description
Collect Miro REST API v2 diagnostic evidence for support tickets.
Use when encountering persistent issues, preparing support tickets,
or collecting diagnostic information for Miro integration problems.
Trigger with phrases like "miro debug", "miro support bundle",
"collect miro logs", "miro diagnostic", "miro support ticket".
allowed-tools
Read, Bash(curl:*), Bash(tar:*), Bash(jq:*), Grep
version
1.7.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
["saas","miro","debugging","diagnostics"]
compatibility
Designed for Claude Code
Miro Debug Bundle
Overview
Collect all diagnostic information needed to troubleshoot Miro REST API v2 integration issues and file effective support tickets.
Prerequisites
Access token (even expired ones are useful for diagnostics)
curl and jq available
Application logs accessible
Instructions
Step 1: Create the Debug Bundle Script
#!/bin/bash# miro-debug-bundle.sh — Collect Miro API diagnosticsset -euo pipefail
BUNDLE_DIR="miro-debug-$(date +%Y%m%d-%H%M%S)"mkdir -p "$BUNDLE_DIR"echo"=== Miro Debug Bundle ===" | tee"$BUNDLE_DIR/summary.txt"echo"Generated: $(date -u +%Y-%m-%dT%H:%M:%SZ)" | tee -a "$BUNDLE_DIR/summary.txt"echo"" >> "$BUNDLE_DIR/summary.txt"
echo"--- Recent Application Errors ---" >> "$BUNDLE_DIR/summary.txt"# Search for Miro-related errors in common log locationsfor logpath in \
"$(npm prefix 2>/dev/null)/logs" \
"$HOME/.npm/_logs" \
"/var/log/app" \
"./logs"; doif [ -d "$logpath" ]; then
grep -ri "miro\|api\.miro\.com""$logpath"/*.log 2>/dev/null | \
tail -30 | \
sed 's/Bearer [A-Za-z0-9._-]*/Bearer [REDACTED]/g' \
>> "$BUNDLE_DIR/error-logs.txt" 2>/dev/null
fidone# Redact .env fileif [ -f .env ]; thenecho"--- Config (redacted) ---" > "$BUNDLE_DIR/config-redacted.txt"
sed 's/=.*/=[REDACTED]/' .env >> "$BUNDLE_DIR/config-redacted.txt"fi
Step 5: Package the Bundle
# Remove raw response bodies that might contain sensitive datarm -f "$BUNDLE_DIR/boards-response.json""$BUNDLE_DIR/response-headers.txt"
tar -czf "$BUNDLE_DIR.tar.gz""$BUNDLE_DIR"rm -rf "$BUNDLE_DIR"echo""echo"Bundle created: $BUNDLE_DIR.tar.gz"echo"Review contents before sharing with Miro support."
Sensitive Data Handling
ALWAYS redact before sharing:
Access tokens and refresh tokens
Client secrets
User email addresses and names
Board content that may contain proprietary information
Following this guide produces the Miro integration outcome for its topic—configuration, validation evidence, operational recovery, or a documented migration result. Record command output and relevant identifiers so a failed step is traceable.
Examples
Start with the smallest applicable command or code example in the relevant section, using a dedicated test board and non-production credentials. Confirm the expected response or validation result before applying the pattern to production.
