Skip to main content
adobe-advanced-troubleshooting Apply advanced debugging techniques for Adobe API issues: IMS token
introspection, Firefly job failure analysis, PDF Services error
codes, and network-layer diagnostics for Adobe endpoints.
Trigger with phrases like "adobe hard bug", "adobe mystery error",
"adobe impossible to debug", "difficult adobe issue", "adobe deep debug".
跳到安装 Skills Marketplace 发现并探索由社区构建的 Agent Skills
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills --skill adobe-advanced-troubleshooting命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
下载 Zip 下载中... 同仓库更多 Skills 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".
jeremylongshore
jeremylongshore/claude-code-plugins-plus-skills
打开 GitHub 仓库 name adobe-advanced-troubleshooting description Apply advanced debugging techniques for Adobe API issues: IMS token
introspection, Firefly job failure analysis, PDF Services error
codes, and network-layer diagnostics for Adobe endpoints.
Trigger with phrases like "adobe hard bug", "adobe mystery error",
"adobe impossible to debug", "difficult adobe issue", "adobe deep debug".
allowed-tools Read, Grep, Bash(kubectl:*), Bash(curl:*), Bash(tcpdump:*) version 1.6.0 license MIT author Jeremy Longshore <jeremy@intentsolutions.io> tags ["saas","design","adobe"] compatibility Designed for Claude Code
Adobe Advanced Troubleshooting
Overview
Deep debugging techniques for complex Adobe API issues that resist standard troubleshooting: IMS token problems, Firefly async job failures, PDF Services edge cases, and network-layer diagnostics.
Prerequisites
Access to production logs and metrics
curl with verbose mode for HTTP debuggingUnderstanding of OAuth 2.0 token flows
Network capture tools (tcpdump, openssl s_client)
Instructions
Technique 1: IMS Token Introspection
When auth issues occur, decode the access token to check claims:
TOKEN=$(curl -s -X POST 'https://ims-na1.adobelogin.com/ims/token/v3' \
-d "client_id=${ADOBE_CLIENT_ID} &client_secret=${ADOBE_CLIENT_SECRET} &grant_type=client_credentials&scope=${ADOBE_SCOPES} " | jq -r '.access_token' )
echo "$TOKEN " | cut -d. -f2 | tr '_-' '/+' | base64 -d 2>/dev/null | python3 -m json.tool
Technique 2: Verbose HTTP Request Tracing
curl -v -X POST 'https://firefly-api.adobe.io/v3/images/generate' \
-H "Authorization: Bearer ${TOKEN} " \
-H "x-api-key: ${ADOBE_CLIENT_ID} " \
-H "Content-Type: application/json" \
-d '{"prompt":"test","n":1,"size":{"width":512,"height":512}}'
tee
Technique 3: Firefly Async Job Failure Analysis
async function diagnoseFireflyJob (jobId : string , statusUrl : string const token = await getAccessToken ();
const response = await fetch (statusUrl, {
headers : {
'Authorization' : `Bearer ${token} ` ,
'x-api-key' : process.env .ADOBE_CLIENT_ID !,
},
});
const status = await response.json ();
console .log ('=== Firefly Job Diagnosis ===' );
console .log ('Job ID:' , jobId);
console .log ('Status:' , status.status );
if (status.status === 'failed' ) {
console .log ('Error code:' , status.error ?.code );
console .log ('Error message:' , status.error ?.message );
console .log ('Error details:' , JSON .stringify (status.error ?.details , null , 2 ));
}
console .log ('Response headers:' , Object .fromEntries (response.headers .entries ()));
}
Technique 4: PDF Services Error Code Mapping
const PDF_ERROR_MAP : Record <string , { cause : string ; action : string ; retryable : boolean }> = {
'DISQUALIFIED' : { cause : 'File is encrypted/password-protected' , action : 'Decrypt PDF first' , retryable : false },
'BAD_PDF' : { cause : 'Corrupted or invalid PDF' , action : 'Validate with pdfinfo/pdftk' , retryable : false },
'BAD_PDF_CONTENT' : { cause : 'PDF content is malformed' , action : 'Re-export from source' , retryable : false },
'UNSUPPORTED_MEDIA_TYPE' : { cause : 'Wrong file format for operation' , action : 'Check MimeType matches file' , retryable : false },
'FILE_SIZE_EXCEEDED' : { cause : 'File exceeds size limit' , action : 'Compress or split PDF' , retryable : false },
'PAGE_LIMIT_EXCEEDED' : { cause : 'Too many pages for operation' , action : 'Split into smaller PDFs' , retryable : false },
'QUOTA_EXCEEDED' : { cause : 'Monthly transaction limit hit' , action : 'Upgrade plan or wait for reset' , retryable : false },
'INTERNAL_ERROR' : { cause : 'Adobe server error' , action : 'Retry with backoff' , retryable : true },
'TIMEOUT' : { cause : 'Processing timeout' , action : 'Try smaller file or fewer pages' , retryable : true },
};
export function diagnosePdfError (errorCode : string string {
const info = PDF_ERROR_MAP [errorCode];
if (!info) return `Unknown PDF Services error: ${errorCode} ` ;
return `${errorCode} : ${info.cause} \nAction: ${info.action} \nRetryable: ${info.retryable} ` ;
}
Technique 5: Layer-by-Layer Isolation #!/bin/bash
echo "=== Layer 1: DNS Resolution ==="
nslookup ims-na1.adobelogin.com
nslookup firefly-api.adobe.io
nslookup image.adobe.io
echo ""
echo "=== Layer 2: TCP Connectivity ==="
for host in ims-na1.adobelogin.com firefly-api.adobe.io image.adobe.io; do
timeout 5 bash -c "echo > /dev/tcp/$host /443" 2>/dev/null && echo "$host :443 OPEN" || echo "$host :443 BLOCKED"
done
echo ""
echo "=== Layer 3: TLS Handshake ==="
for host in ims-na1.adobelogin.com firefly-api.adobe.io; do
echo | openssl s_client -connect "$host :443" -servername "$host " 2>/dev/null | grep -E "subject|issuer|Verify return"
done
echo ""
echo "=== Layer 4: IMS Authentication ==="
HTTP_CODE=$(curl -s -o /dev/null -w "%{http_code}" -X POST \
'https://ims-na1.adobelogin.com/ims/token/v3' \
-d "client_id=${ADOBE_CLIENT_ID} &client_secret=${ADOBE_CLIENT_SECRET} &grant_type=client_credentials&scope=${ADOBE_SCOPES} " )
echo "IMS Token: HTTP $HTTP_CODE "
echo ""
echo "=== Layer 5: API Endpoint ==="
if [ "$HTTP_CODE " = "200" ]; then
TOKEN=$(curl -s -X POST 'https://ims-na1.adobelogin.com/ims/token/v3' \
-d "client_id=${ADOBE_CLIENT_ID} &client_secret=${ADOBE_CLIENT_SECRET} &grant_type=client_credentials&scope=${ADOBE_SCOPES} " | python3 -c "import sys,json; print(json.load(sys.stdin)['access_token'])" )
API_CODE=$(curl -s -o /dev/null -w "%{http_code}" -X POST \
'https://firefly-api.adobe.io/v3/images/generate' \
-H "Authorization: Bearer $TOKEN " \
-H "x-api-key: $ADOBE_CLIENT_ID " \
-H "Content-Type: application/json" \
-d '{"prompt":"test","n":1,"size":{"width":512,"height":512}}' )
echo "Firefly API: HTTP $API_CODE "
fi
Technique 6: Extract x-request-id for Adobe Support
async function debugAdobeCall (url : string , options : RequestInit const response = await fetch (url, options);
const debugInfo = {
url,
status : response.status ,
requestId : response.headers .get ('x-request-id' ),
retryAfter : response.headers .get ('Retry-After' ),
contentType : response.headers .get ('content-type' ),
date : response.headers .get ('date' ),
};
if (!response.ok ) {
const body = await response.text ();
console .error ('Adobe API Error:' , { ...debugInfo, body : body.slice (0 , 500 ) });
}
return { response, debugInfo };
}
Support Escalation Template Adobe Support Ticket
Severity: P[1-4]
x-request-id: [from response header]
Timestamp: [ISO 8601]
Client ID: [first 8 chars only]
API: [Firefly / PDF Services / Photoshop]
Endpoint: [full URL]
HTTP Status: [status code]
Issue Summary: [1-2 sentences]
Steps to Reproduce:
1. [Step]
2. [Step]
Evidence:
- Layer test results attached
- Verbose curl output attached
- JWT token claims (non-sensitive fields only)
Workarounds Attempted:
1. [What you tried] - [Result]
Output
IMS token decoded and claims inspected
HTTP request/response fully traced
Error codes mapped to recovery actions
Network layers tested independently
Support escalation with x-request-id
Resources
Next Steps For load testing, see adobe-load-scale.
