adobe-rate-limits
Implement Adobe API rate limiting, backoff, and quota management across Firefly, PDF Services, Photoshop, and I/O Events APIs. Use when handling rate limit errors, implementing retry logic, or optimizing API request throughput for Adobe. Trigger with phrases like "adobe rate limit", "adobe throttling", "adobe 429", "adobe retry", "adobe backoff", "adobe quota". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill adobe-rate-limits --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 Rate Limits ## Overview Handle Adobe API rate limits gracefully with exponential backoff, `Retry-After` header support, and proactive quota management. Each Adobe API has different rate limits. ## Prerequisites - Adobe SDK installed and authenticated - Understanding of async/await patterns - Awareness of your API tier and entitlements ## Instructions ### Step 1: Know Your Rate Limits by AP
What does the adobe-rate-limits skill do?
Implement Adobe API rate limiting, backoff, and quota management across Firefly, PDF Services, Photoshop, and I/O Events APIs. Use when handling rate limit errors, implementing retry logic, or optimizing API request throughput for Adobe. Trigger with phrases like "adobe rate limit", "adobe throttling", "adobe 429", "adobe retry", "adobe backoff", "adobe quota". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill adobe-rate-limits --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.
