Agent skill · software engineering · jeremylongshore
onenote-deploy-integration
Deploy a OneNote integration with delegated-user lifecycle, environment isolation, staged rollout, and rollback evidence. Use when promoting a service or client that calls Microsoft Graph OneNote. Trigger with "deploy OneNote integration", "promote OneNote worker", or "review OneNote release".
Why this skill is useful
Adds production-ready Dockerfile, Kubernetes manifests, and executable scripts for MSAL token management and health checks that aren't in public docs.
What it needs
Requires docker, docker-compose, node, python, redis 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 Delegated Integration Deployment Overview Deploy a OneNote integration with delegated-user lifecycle, environment isolation, staged rollout, and rollback evidence.. 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 OneNote's service-specific contract requires a signed-in user context. A deployment must model interactive authorization, consent, token-cache protection, reauthentication, and user-bound work ownership instead of silently substituting client credentials. Recheck the dated evidence map before relying on mutable permissions, limits, SDK behavior, supported resources, or cloud availability. Authentication Bind encrypted delegated token state to the correct environment, tenant, app registration, and user. Keep deployment identity separate from the user identity that authorizes OneNote work. Instructions 1. Verify the immutable artifact, dependency locks, configuration schema, tests, and rollback target. 2. Map environment, tenant, app registration, redirect URI, signed-in user, Notes scopes, and approved roots. 3. Confirm token-cache encryption, rotation, revocation, reauthentication, and operator ownership. 4. Deploy dark, run offline checks, then perform one approved read-only synthetic smoke test. 5. Canary a bounded user cohort and monitor auth failures, 429s, latency, queue age, and reconciliation. 6. Promote or roll back from declared thresholds and retain the release and cleanup receipt. 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-deploy-integration