Agent skill · software engineering · jeremylongshore
fathom-rate-limits
Handle Fathom API rate limits (60 requests/minute per user).
Why this skill is useful
Adds an executable rate limiter and retry strategy for managing Fathom API requests, which are not covered in public documentation.
What it needs
Requires fathom account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Fathom Rate Limits Prerequisites Current provider limits, aggregate baseline, stable request/event IDs, synthetic test data, and a capacity owner. Instructions 1. Bound concurrency and preserve idempotency for meeting, sync, and follow-up operations. 2. Monitor throttling, queue age, errors, and duplicate-action risk using redacted aggregate metrics. 3. Back off with jitter on transient limits and reduce load before replaying failed work. Output A rate-aware workflow with bounded retry, idempotency, redacted monitoring, and safe recovery ownership. Examples Increase synthetic development workload gradually below approved limits, record aggregate 429s/latency/completion, and apply backoff on throttling. Do not retry meeting/CRM follow-up actions without checking stable IDs, consent, and current state. Overview Fathom's API enforces a strict 60 requests-per-minute cap per user across all API keys. Since meeting transcripts and action items are often fetched in bulk after a day of calls, this limit becomes a real constraint for teams processing large meeting backlogs. Transcript endpoints are especially heavy because they return full conversation text, making pagination and careful throttling essential for any integration that syncs meeting intelligence into CRMs or project trackers. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/fathom-rate-limits