Skip to main content Home Creators jeremylongshore tons-of-skills-marketplace figma-debug-bundle
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/tons-of-skills-marketplace --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 langchain-deploy-integration Deploy a LangChain 1.0 / LangGraph 1.0 app to Cloud Run, Vercel, or LangServe correctly — with timeouts sized for chain length, cold-start mitigation, SSE anti-buffering headers, and Secret Manager over .env. Use when prepping a first production deploy, debugging a stream that hangs behind a proxy, or diagnosing p99 latency spikes. Trigger with "langchain deploy", "langchain cloud run", "langchain vercel python", "langchain langserve", or "langchain docker".
langchain-langgraph-agents Build a correct LangGraph 1.0 ReAct agent with create_react_agent — typed tools, error propagation, recursion caps, and stop conditions that actually stop. Use when writing a first tool-calling agent, migrating from AgentExecutor or initialize_agent, or diagnosing an agent that loops on vague prompts. Trigger with "langgraph agent", "create_react_agent", "langgraph tool calling", "AgentExecutor migration", or "agent loop cost".
langchain-langgraph-human-in-loop Build LangGraph 1.0 human-in-the-loop approval flows with interrupt_before /
interrupt_after and Command(resume=...) — JSON-serializable state, clean
resume semantics, and UI wiring for approval decisions. Use when adding an
approval gate before an expensive tool call, wiring a Slack/web UI for agent
approvals, or debugging a graph that crashes on interrupt.
Trigger with "langgraph human in loop", "langgraph interrupt_before",
"langgraph approval flow", "Command resume", "langgraph HITL".
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.