Agent skill · software engineering · jeremylongshore
onenote-reference-architecture
Define a production OneNote architecture for delegated access, multiple content locations, bounded workers, reconciliation, and evidence. Use when standardizing several OneNote workloads. Trigger with "design OneNote architecture", "standardize OneNote services", or "review OneNote topology".
Why this skill is useful
Provides detailed architecture and API path patterns for integrating with OneNote across different storage backends, which 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 Integration Reference Architecture Overview Define a production OneNote architecture for delegated access, multiple content locations, bounded workers, reconciliation, and 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 The architecture must distinguish user, Microsoft 365 group, and SharePoint-site roots; delegated user sessions; metadata versus page bodies; reads versus controlled HTML writes; queues; and reconciliation. OneNote does not provide documented change notifications or delta for these resources. Recheck the dated evidence map before relying on mutable permissions, limits, SDK behavior, supported resources, or cloud availability. Authentication Bind each authorization grant to app, tenant, user, environment, scopes, and approved roots. Encrypt token caches and separate deployment authority from content authority. Instructions 1. State workloads, sources of truth, locations, consistency, recovery, and data-classification objectives. 2. Map clients, auth broker, encrypted token store, OneNote gateway, per-user queues, workers, checkpoints, evidence, and destinations. 3. Define v1.0 request, hierarchy, paging, HTML, error, and throttling contracts at the gateway. 4. Design scheduled section-scoped polling and full reconciliation without undocumented delta or webhook endpoints. 5. Threat-model token theft, cross-user access, content leakage, replay, queue starvation, and unsupported cloud deployment. 6. Choose rollout stages, capacity envelope, observability, incident controls, and tested rollback. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/onenote-reference-architecture