Agent skill · data analytics · jeremylongshore
onenote-performance-tuning
Improve OneNote read and write latency from measured evidence while preserving completeness and service limits. Use when an integration misses a latency or throughput objective. Trigger with "tune OneNote performance", "reduce OneNote calls", or "optimize OneNote paging".
Why this skill is useful
Provides specific patterns and optimizations for handling OneNote Graph API performance issues that the AI wouldn't reliably generate on its own.
What it needs
Requires node, python installed locally. Requires azure account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
OneNote Measured Performance Tuning Overview Improve OneNote read and write latency from measured evidence while preserving completeness and service limits.. 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 recommends selecting only required properties, expanding safe hierarchy relationships, enumerating pages per section, and overriding the default last-modified ordering when that sort is unnecessary. Every response page still requires completeness accounting. Recheck the dated evidence map before relying on mutable permissions, limits, SDK behavior, supported resources, or cloud availability. Authentication Measure under delegated user and location aliases without content labels. Use synthetic or approved non-sensitive workloads. Instructions 1. Define the operation, service-level objective, location, volume, and completeness requirement. 2. Measure latency, calls, response pages, bytes, concurrency, 429s, retries, and downstream time. 3. Attribute cost to hierarchy fan-out, all-pages scans, unnecessary fields, default sorting, content fetches, and writes. 4. Test selected fields, safe expansion, section-scoped enumeration, caching, and bounded batching independently. 5. Canary one change within documented concurrency and request budgets. 6. Compare percentile latency and completeness, then retain only verified gains with 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/onenote-performance-tuning