alpaca-broker-rate-limits-resilience

What problem does it solve? Alpaca API clients that run bulk jobs, backfills, or reconciliation sweeps hit rate limits and transient failures; this Skill provides the transport-level patterns to handle HTTP 429 responses, rate-limit headers, and flaky connections without losing data or stalling workers. ## Core Features & Use Cases - Rate-limit header handling: Parse X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset on every response to warn proactively and wait precisely until the window resets on a 429. - Retry and backoff loops: Exponential backoff with optional jitter for 5xx and network errors, while surfacing non-retryable 4xx errors instead of retrying them. - Bounded concurrency and pagination: Fixed worker pools, per-run caching, token-based pagination loops for activities and market-data bars, timeouts, and chunked bulk writes. - Use Case: You are building a nightly reconciliation cron job against the Alpaca Broker API. Use this Skill to structure the job so it pages through all account activities, backs off correctly on 429s, and writes results idempotently in chunks. ## Quick Start Use the alpaca rate limits skill to design a retry and pagination wrapper for my Alpaca bulk data backfill job.