Agent skill · software engineering · jeremylongshore
onenote-rate-limits
Implement bounded OneNote throttling, concurrency, retry, and queue backpressure from current service limits and observed responses. Use when handling 429s or scaling a delegated workload. Trigger with "handle OneNote throttling", "fix OneNote 429", or "limit OneNote concurrency".
Why this skill is useful
Adds a complete implementation of a token bucket rate limiter for OneNote API, including handling of 429 errors and request throttling.
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 Throttling and Backpressure Overview Implement bounded OneNote throttling, concurrency, retry, and queue backpressure from current service limits and observed responses.. 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 Current service-specific documentation defines per-app per-user delegated request windows and a small concurrency ceiling, and says OneNote resources do not return Retry-After on 429. Recheck mutable limits at execution time and use bounded exponential backoff with jitter when the server supplies no delay. Recheck the dated evidence map before relying on mutable permissions, limits, SDK behavior, supported resources, or cloud availability. Authentication Partition control by approved delegated user and application without exposing token values or multiplying users to evade service policy. Instructions 1. Inventory operations, user partitions, bursts, concurrency, queues, retries, and downstream acknowledgements. 2. Read the current OneNote service limits and set conservative token buckets and concurrency below them. 3. Honor a valid server delay if observed; otherwise apply capped exponential backoff with jitter. 4. Retry only idempotent reads or writes whose idempotency and reconciliation contract is proven. 5. Feed 429 rate and delay into queue admission, circuit state, and tenant-fair backpressure. 6. Load-test with synthetic content, then document the safe envelope and emergency reduction controls. 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-rate-limits