Skip to main content Início Criadores jeremylongshore tons-of-skills-marketplace adobe-debug-bundle
adobe-debug-bundle Collect Adobe debug evidence for support tickets and troubleshooting.
Use when encountering persistent issues, preparing support tickets,
or collecting diagnostic information for Adobe API problems.
Trigger with phrases like "adobe debug", "adobe support bundle",
"collect adobe logs", "adobe diagnostic".
Ir para a instalação Skills Marketplace Descubra e explore skills de IA criadas pela comunidade.
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ê.
Mostrar detalhes do prompt Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace --skill adobe-debug-bundleO comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.
Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.
Baixar Zip Baixando... Mais deste repositório 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 adobe-debug-bundle description Collect Adobe debug evidence for support tickets and troubleshooting.
Use when encountering persistent issues, preparing support tickets,
or collecting diagnostic information for Adobe API problems.
Trigger with phrases like "adobe debug", "adobe support bundle",
"collect adobe logs", "adobe diagnostic".
allowed-tools Read, Bash(grep:*), Bash(curl:*), Bash(tar:*), Grep version 1.7.0 license MIT author Jeremy Longshore <jeremy@intentsolutions.io> tags ["saas","design","adobe"] compatibility Designed for Claude Code
Adobe Debug Bundle
Overview
Collect all necessary diagnostic information for Adobe support tickets. This script gathers SDK versions, credential validation status, API connectivity, and redacted configuration into a support-ready archive.
Prerequisites
Adobe credentials configured (env vars or .env file)
Node.js or Python environment with Adobe SDKs installed
Permission to run network diagnostics
Instructions
Step 1: Create Debug Bundle Script
#!/bin/bash
set -euo pipefail
BUNDLE_DIR="adobe-debug-$(date +%Y%m%d-%H%M%S) "
mkdir -p "$BUNDLE_DIR "
echo "=== Adobe Debug Bundle ===" | tee "$BUNDLE_DIR /summary.txt"
echo "Generated: $(date -u +%Y-%m-%dT%H:%M:%SZ) " >> "$BUNDLE_DIR /summary.txt"
echo "Hostname: $(hostname) " >> "$BUNDLE_DIR /summary.txt"
echo "" >> "$BUNDLE_DIR /summary.txt"
echo "--- Runtime Environment ---" >> "$BUNDLE_DIR /summary.txt"
node --version >> "$BUNDLE_DIR /summary.txt" 2>&1 || echo "Node.js: not found" >> "$BUNDLE_DIR /summary.txt"
npm --version >> " 2>&1 || $BUNDLE_DIR
echo
"npm: not found"
"$BUNDLE_DIR /summary.txt"
"$BUNDLE_DIR /summary.txt"
echo
"Python: not found"
"$BUNDLE_DIR /summary.txt"
echo
""
"$BUNDLE_DIR /summary.txt"
echo
"--- Adobe SDK Versions ---"
"$BUNDLE_DIR /summary.txt"
"$BUNDLE_DIR /summary.txt"
echo
"PDF Services SDK: not installed"
"$BUNDLE_DIR /summary.txt"
"$BUNDLE_DIR /summary.txt"
echo
"Firefly APIs: not installed"
"$BUNDLE_DIR /summary.txt"
"$BUNDLE_DIR /summary.txt"
echo
"Photoshop APIs: not installed"
"$BUNDLE_DIR /summary.txt"
"$BUNDLE_DIR /summary.txt"
echo
"Lightroom APIs: not installed"
"$BUNDLE_DIR /summary.txt"
"$BUNDLE_DIR /summary.txt"
echo
"AIO SDK: not installed"
"$BUNDLE_DIR /summary.txt"
echo
""
"$BUNDLE_DIR /summary.txt"
echo
"--- Credential Status ---"
"$BUNDLE_DIR /summary.txt"
echo
"ADOBE_CLIENT_ID: ${ADOBE_CLIENT_ID:+[SET, length=${#ADOBE_CLIENT_ID} ]} "
"$BUNDLE_DIR /summary.txt"
echo
"ADOBE_CLIENT_ID: ${ADOBE_CLIENT_ID:-[NOT SET]} "
"$BUNDLE_DIR /summary.txt"
echo
"ADOBE_CLIENT_SECRET: ${ADOBE_CLIENT_SECRET:+[SET]} "
"$BUNDLE_DIR /summary.txt"
echo
"ADOBE_CLIENT_SECRET: ${ADOBE_CLIENT_SECRET:-[NOT SET]} "
"$BUNDLE_DIR /summary.txt"
echo
"ADOBE_SCOPES: ${ADOBE_SCOPES:-[NOT SET]} "
"$BUNDLE_DIR /summary.txt"
echo
"ADOBE_IMS_ORG_ID: ${ADOBE_IMS_ORG_ID:-[NOT SET]} "
"$BUNDLE_DIR /summary.txt"
echo
""
"$BUNDLE_DIR /summary.txt"
echo
"--- OAuth Token Test ---"
"$BUNDLE_DIR /summary.txt"
if
"${ADOBE_CLIENT_ID:-} "
"${ADOBE_CLIENT_SECRET:-} "
then
"\nHTTP_CODE:%{http_code}"
'https://ims-na1.adobelogin.com/ims/token/v3'
"client_id=${ADOBE_CLIENT_ID} &client_secret=${ADOBE_CLIENT_SECRET} &grant_type=client_credentials&scope=${ADOBE_SCOPES:-openid} "
echo
"$TOKEN_RESPONSE "
"HTTP_CODE:"
cut
echo
"IMS Token Endpoint: HTTP $HTTP_CODE "
"$BUNDLE_DIR /summary.txt"
if
"$HTTP_CODE "
"200"
then
echo
"$TOKEN_RESPONSE "
"HTTP_CODE:"
"import sys,json; d=json.load(sys.stdin); print(f'Error: {d.get(\"error\",\"unknown\")} - {d.get(\"error_description\",\"no description\")}')"
"$BUNDLE_DIR /summary.txt"
echo
"Could not parse error response"
"$BUNDLE_DIR /summary.txt"
fi
else
echo
"Skipped: credentials not set"
"$BUNDLE_DIR /summary.txt"
fi
echo
""
"$BUNDLE_DIR /summary.txt"
echo
"--- API Endpoint Connectivity ---"
"$BUNDLE_DIR /summary.txt"
for
in
"ims-na1.adobelogin.com"
"firefly-api.adobe.io"
"image.adobe.io"
"pdf-services.adobe.io"
"developer.adobe.com"
do
"%{http_code}"
"https://$endpoint "
echo
"UNREACHABLE"
echo
"$endpoint : $STATUS "
"$BUNDLE_DIR /summary.txt"
done
echo
""
"$BUNDLE_DIR /summary.txt"
echo
"--- DNS Resolution ---"
"$BUNDLE_DIR /summary.txt"
for
in
"ims-na1.adobelogin.com"
"firefly-api.adobe.io"
"image.adobe.io"
do
"$host "
tail
"$BUNDLE_DIR /summary.txt"
done
if
env
then
echo
""
"$BUNDLE_DIR /summary.txt"
echo
"--- Config (values redacted) ---"
"$BUNDLE_DIR /summary.txt"
's/=.*/=***REDACTED***/'
env
"$BUNDLE_DIR /config-redacted.txt"
fi
"$BUNDLE_DIR .tar.gz"
"$BUNDLE_DIR "
rm
"$BUNDLE_DIR "
echo
""
echo
"Bundle created: $BUNDLE_DIR .tar.gz"
echo
"Review contents before sharing with Adobe Support."
Step 2: Run the Bundle chmod +x adobe-debug-bundle.sh
./adobe-debug-bundle.sh
Step 3: Review Before Sharing ALWAYS review the bundle before sending to Adobe Support:
tar -tzf adobe-debug-*.tar.gz
tar -xzf adobe-debug-*.tar.gz
cat adobe-debug-*/summary.txt
ADOBE_CLIENT_SECRET valuesPrivate keys or certificates
PII (customer emails, names, IDs)
Full .env files
Error messages and HTTP status codes
SDK and runtime versions
Connectivity test results
Redacted configuration keys
Output
adobe-debug-YYYYMMDD-HHMMSS.tar.gz archive containing:
summary.txt — Environment, SDK versions, credential status, connectivityconfig-redacted.txt — Configuration keys with values masked
Error Handling Item Purpose Collected Node/Python versions SDK compatibility Yes SDK package versions Version-specific bugs Yes OAuth token test Auth validation Status code only DNS resolution Network issues Yes API connectivity Firewall/proxy issues HTTP status codes
Examples Start with the smallest applicable command or code example already provided in this guide, using a non-production Adobe environment and credentials. Confirm the documented response or validation result before applying the pattern to production.
Resources
Next Steps For rate limit issues, see adobe-rate-limits.
