Agent skill · marketing growth · jeremylongshore
onenote-cost-tuning
Reduce OneNote integration waste across requests, workers, storage, and downstream processing without inventing API pricing. Use when a polling or synchronization workload is expensive or noisy. Trigger with "reduce OneNote cost", "audit OneNote request waste", or "tune OneNote polling".
Why this skill is useful
Provides specific strategies for optimizing OneNote Graph API usage that the AI wouldn't reliably generate on its own.
What it needs
Requires node, python installed locally. Requires microsoft account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
OneNote Workload Cost and Waste Review Overview Reduce OneNote 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 Microsoft Graph OneNote documentation and the selected integration's tested contract. Named identity, content, workload, security, and operations owners appropriate to the requested scope. Synthetic or approved non-production fixtures with secrets and real notebook content removed. Current Contract Microsoft publishes service limits, not a universal per-request OneNote price. Cost analysis must separate Microsoft licensing from application compute, queues, storage, observability, retries, and downstream processors. Recheck the dated evidence map before relying on mutable permissions, limits, SDK behavior, supported resources, or cloud availability. Authentication Use aggregated content-free telemetry under a delegated-user alias. Do not export page titles, bodies, tokens, or tenant identifiers to a cost tool without data-owner approval. Instructions 1. Define the owner, measurement window, freshness objective, and cost allocation boundaries. 2. Measure requests by operation, outcome, location, page count, bytes, retry, and worker time. 3. Find all-pages scans, unused fields, redundant hierarchy calls, duplicate retries, and overlapping pollers. 4. Model savings from section scoping, field selection, expansion, caching, batching, and slower polling. 5. Canary one change while measuring completeness, latency, throttling, and downstream backlog. 6. Adopt only verified savings with rollback thresholds and a recurring regression owner. 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/onenote-cost-tuning--664892