Agent skill · software engineering · jeremylongshore
notion-rate-limits
Implement adaptive Notion request throttling and bounded retry behavior from observed responses. Use when handling 429s, queue pressure, or bursty workloads. Trigger with "handle Notion rate limits", "throttle Notion requests", or "fix Notion 429".
Why this skill is useful
Provides specific implementation patterns and scripts for managing Notion API rate limits that the AI wouldn't reliably generate on its own.
What it needs
Requires npm installed locally. Requires notion account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Notion Rate-Limit and Retry Control Overview Implement adaptive Notion request throttling and bounded retry behavior from observed responses.. This workflow produces an auditable decision or artifact before any live action. Prerequisites Current first-party Notion documentation and the selected integration's tested API-version contract. A named workspace owner, content or data owner, and operation owner. Synthetic or approved non-production fixtures with secrets and workspace content removed. Current Contract Notion documents an average per-connection request rate, allows some bursts, returns 429 for rate pressure, and supplies Retry-After. Limits may change, so the runtime response is authoritative. Recheck the dated evidence map before relying on mutable fields, endpoints, versions, limits, or delivery behavior. Authentication Throttle by approved connection and tenant boundary; never log tokens or create extra credentials to bypass a limit. Instructions 1. Measure requests by operation, tenant, outcome, Retry-After, latency, retry, and queue age. 2. Classify retryable rate and transient service failures separately from permanent input or access failures. 3. Use a shared limiter with bounded concurrency, tenant fairness, jitter, and a strict attempt and elapsed-time budget. 4. Honor Retry-After as the minimum wait and reduce future pressure after repeated limits. 5. Preserve idempotency and acknowledgement state before retrying writes. 6. Test recovery, saturation, cancellation, restart, and downstream backpressure. Tool Discipline Use Read, Glob, and Grep to inspect documentation, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, workspace content, user data, file transfer, deployment, capability or sharing changes, writes, spend, or deletion. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/notion-rate-limits--b34fff