Agent skill · software engineering · jeremylongshore
ramp-performance-tuning
Analyze and tune Ramp pagination, concurrency, batching, webhooks, deferred tasks, and local persistence while preserving complete ordered reconciliation. Use when seeds are slow, syncs lag, or workloads encounter 504 responses. Trigger with "speed up Ramp sync" or "Ramp performance".
Why this skill is useful
Provides specific API integration patterns and error handling for Ramp's corporate card management that the AI wouldn't reliably generate on its own.
What it needs
Requires ramp account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Ramp API Throughput and Sync Performance Overview Measure first, then tune by endpoint and object lifecycle. Maximize useful work per request while staying below shared limits and keeping checkpoints at durable commit boundaries. Prerequisites Identify the Ramp application, environment, business entities, affected data and workflows, accountable owner, and rollback boundary. Read references/official-docs.md and re-check endpoint schemas, scopes, limits, and support status before a live operation. Use synthetic fixtures or Ramp sandbox until production access and business effects are explicitly approved. Prepare approved secret storage and a sanitized evidence location. Current Contract Ramp's default rate limit is 200 requests per rolling 10-second window per source IP, subject to current documentation and approved increases. API requests exceeding 60 seconds return 504; pagination and smaller work units are the primary controls for large reads. Most list endpoints support cursor-style pagination, but page sizes and incremental filters are endpoint-specific. Accounting batch endpoints may have explicit item caps and all-or-nothing behavior; current schema controls each batch. Instructions 1. Benchmark request latency, response bytes, records per page, pages per entity, retries, 429/504 rate, queue lag, database time, and reconciliation duration. 2. Separate initial full seed, incremental reads, webhook-driven fetches, periodic reconciliation, writes, and deferred tasks into independent budgets. 3. Increase page size only within the endpoint schema, bound concurrency below the shared IP window, add jitter, and persist after each downstream commit. 4. Use webhooks to trigger targeted reads, batch only where documented, and poll deferred tasks with bounded schedules rather than holding API requests open. 5. Load-test with synthetic or sandbox data, compare p50/p95/p99 plus completeness, then canary and retain rollback thresholds. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/ramp-performance-tuning