Agent skill · software engineering · jeremylongshore
persona-rate-limits
Analyze and control Persona request rate and product quotas from live headers, Dashboard limits, and durable retry state. Use when scaling or handling 429 responses. Trigger with: "Persona rate limit", "throttle Persona API", "handle Persona 429".
Why this skill is useful
Adds specific implementation details for handling Persona API rate limits with exponential backoff that the AI wouldn't reliably generate on its own.
What it needs
Requires persona account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Persona Environment Limit and Product Quota Controller Overview Replace invented fixed tables with two current signals: environment request limits and product-specific quotas. Production environments default to 300 requests per minute in current documentation, but Dashboard configuration and response headers govern the running integration. Prerequisites Endpoint and operation inventory with expected volume Current environment limits and product quotas from the Dashboard Durable operation, retry, and reconciliation state Instructions Step 1: Classify work Separate reads, idempotent POSTs, session operations, reconciliation, and product-consuming verification work. Assign independent worker lanes. Step 2: Read live signals Capture RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset, Quota-Limit, Quota-Remaining, and Quota-Reset where returned. Do not assume every endpoint exposes identical values. Step 3: Budget below the boundary Use token buckets per environment and constrained product. Persona recommends throttling when fewer than 15 percent of requests remain. Step 4: Back off on 429 Honor reset or retry guidance. Where no more specific instruction exists, use the documented exponential sequence of 5, 10, 20, and 40 seconds with jitter and a finite budget. Step 5: Protect mutations Use Idempotency-Key on POST and persist identical parameters. After timeout or throttle ambiguity, reconcile resource state before retry. Step 6: Escalate quota exhaustion Pause only the affected lane, surface renewal time and business impact, and require approval before changing a paid product or verification policy. Authentication Rate-control workers use the same environment-scoped bearer authentication and dated API version as the guarded request. Telemetry may record header values but never the bearer key or PII payload. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/persona-rate-limits