Agent skill · software engineering · jeremylongshore
notion-load-scale
Plan and test Notion workload capacity within observed limits without evading per-connection controls. Use when scaling exports, syncs, workers, or high-volume reads. Trigger with "scale Notion integration", "capacity plan Notion", or "load test Notion safely".
Why this skill is useful
Adds full runnable TypeScript and Python implementations for high-volume Notion API usage that aren't available in public documentation.
What it needs
Requires @notionhq/client, notion-client, p-queue 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 Capacity and Backpressure Planning Overview Plan and test Notion workload capacity within observed limits without evading per-connection controls.. 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 request rate and payload limits but may change quotas. Capacity planning must honor Retry-After, response latency, page size, pagination depth, downstream pressure, and tenant fairness. Recheck the dated evidence map before relying on mutable fields, endpoints, versions, limits, or delivery behavior. Authentication Use synthetic non-production content and one approved test connection. Additional tokens are not a sharding mechanism for bypassing limits. Instructions 1. Define volume, freshness, concurrency, burst, payload, tenant, and recovery objectives. 2. Measure a low-rate baseline by operation using synthetic fixtures. 3. Model request amplification from pagination, block recursion, retries, reconciliation, and downstream failures. 4. Introduce queue rate control, tenant fairness, bounded concurrency, and backpressure. 5. Increase load in approved stages while observing 429, Retry-After, latency, errors, queue age, and completeness. 6. Set safe operating limits, saturation alarms, degradation behavior, and rollback thresholds. 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-load-scale--c6e2f5