adobe-common-errors
Diagnose and fix common Adobe API errors across Firefly Services, PDF Services, Photoshop API, and Adobe I/O Events. Use when encountering Adobe errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "adobe error", "fix adobe", "adobe not working", "debug adobe", "adobe 403", "adobe 429". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill adobe-common-errors --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Adobe Common Errors ## Overview Quick reference for the most common errors across Adobe APIs with real error messages, root causes, and verified fixes. ## Prerequisites - Adobe SDK or API credentials configured - Access to Adobe Developer Console (https://developer.adobe.com/console) - Access to error logs or API responses ## Instructions ### Step 1: Identify the HTTP Status Code and Error Body
What does the adobe-common-errors skill do?
Diagnose and fix common Adobe API errors across Firefly Services, PDF Services, Photoshop API, and Adobe I/O Events. Use when encountering Adobe errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "adobe error", "fix adobe", "adobe not working", "debug adobe", "adobe 403", "adobe 429". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill adobe-common-errors --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
