Agent skill · software engineering · jeremylongshore
adobe-rate-limits
Implement service-specific Adobe admission control, Retry-After handling, bounded retries, and spend-aware queues. Use when scaling workloads or handling 429 responses. Trigger with "Adobe rate limit", "Adobe 429", or "Adobe backoff".
Why this skill is useful
Provides specific implementation patterns for handling Adobe API rate limits that the AI wouldn't reliably generate on its own.
What it needs
Requires adobe-sdk installed locally. Requires adobe account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Adobe Throttling and Backpressure Overview Implement service-specific Adobe admission control, Retry-After handling, bounded retries, and spend-aware queues. This workflow produces a reviewable artifact and evidence before any live side effect. Prerequisites Current first-party Adobe documentation for every selected service, API version, auth flow, limit, and lifecycle. Named product, identity, security, data, budget, release, and operations owners appropriate to the scope. Synthetic or approved non-production fixtures with secret and content canaries. Current Contract Adobe limits differ by service, operation, entitlement, and contract. Recheck first-party limits at execution. A valid Retry-After response is authoritative; absence requires conservative capped exponential backoff with jitter, not a remembered universal rate. Recheck the dated evidence map before relying on mutable product behavior. Authentication Partition control by approved credential, organization, service, operation, and tenant without exposing tokens or multiplying credentials to evade policy. Instructions 1. Inventory traffic, operations, concurrency, queues, retry chains, job durations, transactions, and downstream acknowledgements. 2. Read current service limits and capture observed 429 headers and error bodies from sanitized evidence. 3. Set conservative token buckets, concurrency, queue size, and spend ceilings below verified constraints. 4. Retry only classified transient, idempotent work; honor valid server delay and cap attempts plus elapsed time. 5. Quarantine ambiguous writes/jobs and propagate backpressure rather than recursively retrying. 6. Load-test with synthetic data, publish the safe envelope, and assign an emergency reduction switch. Tool Discipline Use Read, Glob, and Grep to inspect current documentation, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/adobe-rate-limits--f73c92