Agent skill · software engineering · jeremylongshore
fireflies-rate-limits
Monitor and enforce current Fireflies plan and operation-specific request limits with bounded concurrency, retryAfter handling, and cost-aware pagination. Use when preventing throttling or recovering from 429-style failures. Trigger with "Fireflies rate limit", "too_many_requests", or "budget Fireflies calls".
Why this skill is useful
Adds executable scripts for handling Fireflies.ai API rate limits with backoff and queuing that aren't in public docs.
What it needs
Requires p-queue installed locally. Requires fireflies account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Fireflies Request Budget and Backoff Overview Enforce current Fireflies plan and operation-specific request limits with bounded concurrency, retryAfter handling, and cost-aware pagination. Prerequisites The target repository or integration path and the requested operator outcome. The Fireflies principal, team, environment, and data classification for the work. Current Fireflies documentation, credentials only when needed, and an accountable approver. Current Contract General documented limits are 50 requests/day for Free and Pro and 60 requests/minute for Business and Enterprise. addToLiveMeeting is 3 requests per 20 minutes, shareMeeting is 10/hour, and deleteTranscript is 10/minute. Treat docs and retryAfter as authoritative over hard-coded assumptions. Authentication For authenticated operations, inject FIREFLIESAPIKEY from an approved secret manager and send it only as Authorization: Bearer REDACTEDKEY to https://api.fireflies.ai/graphql. Never print, commit, place in a URL, forward to a browser, or include the key in evidence. Webhook signing secrets are separate credentials and must not be reused as API keys. Instructions 1. Identify the plan and every operation-specific bucket used by the workload. 2. Set a conservative request budget and concurrency of one until measured. 3. Use pagination caps and field minimization to avoid unnecessary calls. 4. On toomanyrequests, honor retryAfter when supplied and add bounded jitter. 5. Do not retry auth, privilege, invalid-argument, object-not-found, or AI-credit errors. 6. Export per-operation usage, throttles, wait time, and exhausted-budget metrics. 7. Load-test only against synthetic or approved data within a separate budget. Tool Discipline Use Read, Glob, and Grep to inspect code, configuration, tests, and evidence. Use Write/Edit only for approved implementation or documentation changes. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/fireflies-rate-limits