Agent skill · software engineering · jeremylongshore
onenote-upgrade-migration
Migrate a OneNote integration across auth, SDK, request, or unsupported-feature assumptions with canaries and rollback. Use when replacing app-only access, upgrading dependencies, or removing undocumented polling shortcuts. Trigger with "upgrade OneNote integration", "migrate OneNote auth", or "remove OneNote delta".
Why this skill is useful
Adds detailed migration scripts and strategies for handling breaking changes in OneNote integrations that are not publicly documented.
What it needs
Requires git, node 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 Contract Migration Overview Migrate a OneNote integration across auth, SDK, request, or unsupported-feature assumptions with canaries and rollback.. 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 A safe migration distinguishes Graph v1.0 from SDK version, delegated auth from obsolete app-only paths, supported hierarchy paging from undocumented search or delta, and scheduled reconciliation from unsupported OneNote change notifications. Recheck the dated evidence map before relying on mutable permissions, limits, SDK behavior, supported resources, or cloud availability. Authentication Replace application credentials with an approved delegated lifecycle. Preserve tenant, user, scopes, redirect, consent, encrypted cache, revocation, and reauthentication evidence throughout rollout. Instructions 1. Inventory every OneNote auth flow, SDK call, REST route, location, paging loop, HTML operation, event assumption, and fixture. 2. Trace each behavior to current first-party documentation and classify supported, contradicted, undocumented, or environment-observed. 3. Define the target client boundary and compatibility fixtures without changing live state. 4. Migrate app-only, reconstructed paging, search, delta, webhook, fixed-limit, and Retry-After assumptions. 5. Canary one delegated user and synthetic root with rollback and dual-read comparison where safe. 6. Reconcile results, remove obsolete credentials and dead paths, and publish the final compatibility receipt. Tool Discipline Use Read, Glob, and Grep to inspect documentation, configuration, code, fixtures, and evidence. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/onenote-upgrade-migration