Skip to main content
figma-debug-bundle Collect Figma API diagnostic evidence for support tickets and troubleshooting.
Use when encountering persistent issues, preparing support tickets,
or collecting diagnostic information for Figma API problems.
Trigger with phrases like "figma debug", "figma support bundle",
"collect figma logs", "figma diagnostic".
Jump to install Skills Marketplace Discover and explore AI skills built by the community.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Copy promptShow prompt details A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills --skill figma-debug-bundleThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Download Zip Downloading... More from this repository Implement user sign-up and sign-in flows with Clerk.
Use when building authentication UI, customizing sign-in experience,
or implementing OAuth social login.
Trigger with phrases like "clerk sign-in", "clerk sign-up",
"clerk login flow", "clerk OAuth", "clerk social login".
Implement session management and middleware with Clerk.
Use when managing user sessions, configuring route protection,
or implementing token refresh and custom JWT templates.
Trigger with phrases like "clerk session", "clerk middleware",
"clerk route protection", "clerk token", "clerk JWT".
Configure enterprise SSO, role-based access control, and organization management.
Use when implementing SSO integration, configuring role-based permissions,
or setting up organization-level controls.
Trigger with phrases like "clerk SSO", "clerk RBAC",
"clerk enterprise", "clerk roles", "clerk permissions", "clerk organizations".
Related occupations SOC
Based on SOC occupation classification
name figma-debug-bundle description Collect Figma API diagnostic evidence for support tickets and troubleshooting.
Use when encountering persistent issues, preparing support tickets,
or collecting diagnostic information for Figma API problems.
Trigger with phrases like "figma debug", "figma support bundle",
"collect figma logs", "figma diagnostic".
allowed-tools Read, Bash(curl:*), Bash(tar:*), Bash(node:*), Grep version 1.6.0 license MIT author Jeremy Longshore <jeremy@intentsolutions.io> tags ["saas","figma"] compatibility Designed for Claude Code
Figma Debug Bundle
Overview
Collect all diagnostic data needed to troubleshoot Figma REST API issues or submit a support request. Outputs a redacted archive with connectivity tests, token validation, rate limit status, and API response samples.
Prerequisites
FIGMA_PAT environment variable set
curl and jq available
A Figma file key to test against
Instructions
Step 1: Create Debug Bundle Script
#!/bin/bash
set -euo pipefail
BUNDLE_DIR="figma-debug-$(date +%Y%m%d-%H%M%S) "
mkdir -p "$BUNDLE_DIR "
echo "=== Figma Debug Bundle ===" | tee "$BUNDLE_DIR /summary.txt"
echo "Generated: $(date -u +%Y-%m-%dT%H:%M:%SZ) " >> "$BUNDLE_DIR /summary.txt"
echo "---" >> "$BUNDLE_DIR /summary.txt"
echo "--- Environment ---" >> "$BUNDLE_DIR /summary.txt"
echo "Node: $(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 "OS: $(uname -srm) " >>
>>
>>
>>
>>
-n >>
curl -s -o -w \
-H \
https://api.figma.com/v1/me >>
>>
[ -n ];
-n >>
curl -s -o -w \
-H \
>>
>>
>>
>>
curl -s -D -o /dev/null \
-H \
https://api.figma.com/v1/me
grep -iE >> 2>/dev/null || >>
>>
>>
[ -f ];
jq \
> 2>/dev/null ||
-f
-f
>>
tar -czf
-rf
"$BUNDLE_DIR /summary.txt"
echo
"PAT configured: ${FIGMA_PAT:+YES (${#FIGMA_PAT} chars)} "
"$BUNDLE_DIR /summary.txt"
echo
"File key: ${FIGMA_FILE_KEY:-NOT SET} "
"$BUNDLE_DIR /summary.txt"
echo
""
"$BUNDLE_DIR /summary.txt"
echo
"--- Connectivity ---"
"$BUNDLE_DIR /summary.txt"
echo
"GET /v1/me: "
"$BUNDLE_DIR /summary.txt"
"$BUNDLE_DIR /me.json"
"%{http_code} %{time_total}s"
"X-Figma-Token: ${FIGMA_PAT} "
"$BUNDLE_DIR /summary.txt"
echo
""
"$BUNDLE_DIR /summary.txt"
if
"${FIGMA_FILE_KEY:-} "
then
echo
"GET /v1/files: "
"$BUNDLE_DIR /summary.txt"
"$BUNDLE_DIR /file-meta.json"
"%{http_code} %{time_total}s"
"X-Figma-Token: ${FIGMA_PAT} "
"https://api.figma.com/v1/files/${FIGMA_FILE_KEY} ?depth=1"
"$BUNDLE_DIR /summary.txt"
echo
""
"$BUNDLE_DIR /summary.txt"
fi
echo
""
"$BUNDLE_DIR /summary.txt"
echo
"--- Rate Limit Headers ---"
"$BUNDLE_DIR /summary.txt"
"$BUNDLE_DIR /headers.txt"
"X-Figma-Token: ${FIGMA_PAT} "
"(rate|retry|figma)"
"$BUNDLE_DIR /headers.txt"
"$BUNDLE_DIR /summary.txt"
echo
"No rate limit headers"
"$BUNDLE_DIR /summary.txt"
echo
""
"$BUNDLE_DIR /summary.txt"
echo
"--- Redaction ---"
"$BUNDLE_DIR /summary.txt"
if
"$BUNDLE_DIR /me.json"
then
'{handle: .handle, id: .id, img_url: "[REDACTED]", email: "[REDACTED]"}'
"$BUNDLE_DIR /me.json"
"$BUNDLE_DIR /me-redacted.json"
true
rm
"$BUNDLE_DIR /me.json"
fi
rm
"$BUNDLE_DIR /headers.txt"
echo
"Redaction complete"
"$BUNDLE_DIR /summary.txt"
"$BUNDLE_DIR .tar.gz"
"$BUNDLE_DIR "
rm
"$BUNDLE_DIR "
echo
"Bundle created: $BUNDLE_DIR .tar.gz"
Step 2: Run the Bundle chmod +x figma-debug-bundle.sh
./figma-debug-bundle.sh
Step 3: Review Before Sharing
tar -tzf figma-debug-*.tar.gz
tar -xzf figma-debug-*.tar.gz
cat figma-debug-*/summary.txt
Output
figma-debug-YYYYMMDD-HHMMSS.tar.gz containing:
summary.txt -- environment, connectivity, rate limit status
me-redacted.json -- authenticated user (email redacted)
file-meta.json -- file metadata (if file key provided)
Error Handling Item What It Catches Why It Matters /v1/me response codeToken validity 403 = expired/invalid PAT /v1/files response codeFile access 404 = wrong key, 403 = not shared Rate limit headers Throttling state Retry-After shows if currently limitedResponse time Latency issues >2s suggests network or server problems
Examples
ALWAYS REDACT Before Sharing
Personal access tokens (figd_*)
Email addresses
OAuth client secrets
File content (unless relevant to the bug)
Safe to Include
HTTP status codes and response times
Error message text
Node IDs and file keys (not secrets)
Rate limit header values
Resources
Next Steps For rate limit issues, see figma-rate-limits.