Agent skill · data analytics · jeremylongshore
notion-performance-tuning
Improve Notion integration latency and throughput while preserving completeness, fairness, and limit compliance. Use when measured operations miss performance objectives. Trigger with "tune Notion performance", "reduce Notion latency", or "optimize Notion pagination".
Why this skill is useful
Provides specific caching, batching, and parallel request strategies for optimizing Notion API performance that the AI wouldn't reliably generate on its own.
What it needs
Requires @notionhq/client, lru-cache, 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 Evidence-Driven Performance Tuning Overview Improve Notion integration latency and throughput while preserving completeness, fairness, and limit compliance.. 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 Performance depends on operation type, pagination and recursion, response size, rate pressure, network latency, queueing, downstream processing, and cache behavior. The observed bottleneck must select the optimization. Recheck the dated evidence map before relying on mutable fields, endpoints, versions, limits, or delivery behavior. Authentication Use redacted telemetry and synthetic benchmarks. Content caches require classification, encryption, tenant isolation, expiry, and deletion behavior. Instructions 1. Record latency distributions, requests per business operation, pages, bytes, errors, retries, and queue wait. 2. Identify whether the constraint is Notion calls, pagination, block recursion, transformation, cache, queue, or destination. 3. Choose one intervention: narrower query, checkpoint, concurrency bound, cache, batch, webhook signal, or downstream optimization. 4. State consistency, freshness, completeness, fairness, and memory tradeoffs. 5. Canary against a representative synthetic or approved non-production workload. 6. Compare before and after, exercise rollback, and reject regressions hidden by averages. Tool Discipline Use Read, Glob, and Grep to inspect documentation, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/notion-performance-tuning--1c76c1