Agent skill · software engineering · jeremylongshore
onenote-sdk-patterns
Build a testable Microsoft Graph OneNote client boundary with delegated auth, opaque pagination, HTML operations, errors, and throttling. Use when writing or reviewing integration code. Trigger with "design OneNote client", "review OneNote SDK", or "update OneNote patterns".
Why this skill is useful
Adds middleware patterns and retry logic scripts for OneNote Graph API that enhance error handling and reliability in production integrations.
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 Versioned Client Boundary Overview Build a testable Microsoft Graph OneNote client boundary with delegated auth, opaque pagination, HTML operations, errors, and throttling.. 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 SDK versions change independently from Graph v1.0. Keep stable REST semantics behind typed operations, preserve opaque next links, retain Graph error and request identifiers, and treat generated snippets as starting evidence rather than a pinned package contract. Recheck the dated evidence map before relying on mutable permissions, limits, SDK behavior, supported resources, or cloud availability. Authentication Inject a delegated credential provider bound to app, tenant, user, environment, and scopes. Application credentials and token logging are forbidden for OneNote operations. Instructions 1. Inventory runtime, installed SDK, target v1.0 operations, locations, and generated-code assumptions. 2. Define typed read hierarchy, page-content, create, update, and operation-result contracts. 3. Centralize delegated auth, request IDs, error classification, throttling, timeouts, and redaction. 4. Model opaque next links and semantic HTML normalization without leaking transport details to callers. 5. Add offline contract fixtures for additive fields, paging, errors, 429 without Retry-After, and ambiguous writes. 6. Canary the boundary against one approved synthetic root and record the compatibility matrix. 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-sdk-patterns