Agent skill · software engineering · jeremylongshore
clari-rate-limits
Analyze and schedule Clari exports, ingestion jobs, and Copilot reads within provider concurrency and quota controls. Use when preventing 429 responses or coordinating workers. Trigger with: "handle Clari rate limits", "schedule Clari jobs", "recover from Clari 429".
Why this skill is useful
Adds executable scripts for handling Clari API rate limits and scheduling exports that are not publicly documented.
What it needs
Requires requests installed locally. Requires clari account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Clari Quota-Aware Request Scheduling Overview Model each Clari surface as its own constrained queue. Revenue exports consume organization-level concurrent and rolling quota capacity, ingestion can reject excess concurrent async jobs, and Copilot has documented per-second and weekly ceilings. Prerequisites Request inventory split by Revenue export, ingestion, and Copilot Priority classes, latency objectives, and retry budget Durable job IDs, cursors, and deduplication keys Instructions Step 1: Read the applicable limits Use /admin/limits for Revenue export capacity and record the Copilot 10-per-second and 100,000-per-week ceilings from the current contract. Step 2: Allocate capacity Reserve headroom for interactive or recovery work and assign explicit concurrency to each scheduler rather than letting every worker retry independently. Step 3: Make work resumable Persist export job IDs, ingestion job IDs, Copilot cursors, and request fingerprints before polling or retrying. Step 4: Apply bounded backoff Honor provider retry guidance when present; otherwise use capped exponential backoff with jitter and a maximum elapsed time. Step 5: Prevent duplicate mutations Before replaying a queue or ingestion request, reconcile retained state and provider jobs. Reads may resume from checkpoints; writes require an explicit idempotency decision. Step 6: Measure and tune Track queue delay, attempts, 429 rate, quota remaining, terminal latency, and abandoned work by surface. Authentication Limit reads and job polling still require the correct surface credential. Redact authentication headers and keep scheduler state free of secret values and customer payloads. Tool Discipline Use Read and Grep to inspect configuration, provider contracts, fixtures, logs, schemas, and existing tests before proposing a change. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/clari-rate-limits--29fde9