Agent skill · data analytics · jeremylongshore
onenote-webhooks-events
Design bounded OneNote change detection without claiming unsupported webhooks or delta queries. Use when a workflow must discover page changes on a documented polling schedule. Trigger with "monitor OneNote changes", "poll OneNote safely", or "reconcile OneNote pages".
Why this skill is useful
Provides specific implementation patterns for polling and delta queries in OneNote that are not widely documented.
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 Change Polling and Reconciliation Overview Design bounded OneNote change detection without claiming unsupported webhooks or delta queries.. 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 resources are absent from the current Microsoft Graph supported lists for change notifications and delta query. Use scheduled, section-scoped page metadata reads with complete next-link traversal, overlap windows, periodic full reconciliation, and an explicit freshness contract. Recheck the dated evidence map before relying on mutable permissions, limits, SDK behavior, supported resources, or cloud availability. Authentication Run as an approved delegated user bound to tenant, environment, and roots. Store checkpoints and metadata without page bodies unless content access is separately approved. Instructions 1. Define approved sections, freshness objective, overlap window, deletion strategy, and reconciliation cadence. 2. Capture an initial complete per-section page metadata manifest using selected fields and every next link. 3. Poll each section on a bounded schedule and compare stable page IDs plus documented modification metadata. 4. Use overlap and deduplication so clock skew or partial runs do not drop changes. 5. Checkpoint only after all pages and downstream acknowledgements for the cycle succeed. 6. Run periodic full reconciliation and surface deletions, moves, denied sections, and unsupported assumptions. 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-webhooks-events--9771c5