miro-debug-bundle

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 <[e-mail]>
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 diagnostics
set -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"

Step 2: Collect Environment Info

# Runtime environment
echo "--- Environment ---" >> "$BUNDLE_DIR/summary.txt"
echo "Node.js: $(node --version 2>/dev/null || echo 'not installed')" >> "$BUNDLE_DIR/summary.txt"
echo "npm: $(npm --version 2>/dev/null || echo 'not installed')" >> "$BUNDLE_DIR/summary.txt"
echo  >> 


  >> 
npm list @mirohq/miro-api 2>/dev/null >>  ||   >> 


  >> 
  >> 
  >> 
  >>