Agent skill · data analytics · jeremylongshore
notion-cost-tuning
Reduce Notion integration waste across requests, workers, storage, and downstream processing without inventing API pricing. Use when a workload is noisy, slow, or infrastructure-heavy. Trigger with "reduce Notion cost", "audit Notion request waste", or "tune Notion polling".
Why this skill is useful
Provides specific optimization patterns and caching strategies for the Notion API 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 Workload Cost and Waste Review Overview Reduce Notion integration waste across requests, workers, storage, and downstream processing without inventing API pricing.. 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 publishes operational limits, not a universal per-request price contract. Measure application infrastructure, queue, storage, observability, and downstream processor costs separately from Notion plan terms. Recheck the dated evidence map before relying on mutable fields, endpoints, versions, limits, or delivery behavior. Authentication Use read-only telemetry and redacted request classes. Do not expose content or tokens to cost-analysis systems. Instructions 1. Establish the workload owner, measurement window, freshness objective, and current cost allocation. 2. Count requests by operation, outcome, tenant, retry, page, and bytes without high-cardinality content labels. 3. Identify full scans, duplicate reads, unused fields, failed retries, polling overlap, and repeated transformations. 4. Model filtered queries, cursor checkpoints, webhook signals plus reconciliation, caching, and batching. 5. Rank changes by saved work, correctness risk, implementation effort, and rollback speed. 6. Pilot one change with freshness, completeness, error, and cost guardrails. 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-cost-tuning