Agent skill · data analytics · jeremylongshore
onenote-core-workflow-b
Create or update OneNote page content with an HTML preview, stable targets, read-back verification, and compensation. Use when an approved workflow must write a page. Trigger with "create OneNote page", "update OneNote content", or "append OneNote HTML".
Why this skill is useful
Provides specific OData query patterns and pagination techniques for OneNote that are not commonly known.
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 Controlled Page Change Overview Create or update OneNote page content with an HTML preview, stable targets, read-back verification, and compensation.. 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 Page creation accepts constrained input HTML and uses multipart content when binary parts are present. Updates target elements by data-id or generated IDs returned by an includeIDs read; output HTML is normalized and is not a byte-for-byte echo of input. Recheck the dated evidence map before relying on mutable permissions, limits, SDK behavior, supported resources, or cloud availability. Authentication Use delegated Notes.ReadWrite for the signed-in user only after the target section or page is approved. Keep credential values and notebook bodies out of logs. Instructions 1. Resolve the exact location, section or page ID, current content revision, and content owner. 2. Build well-formed UTF-8 input HTML and a semantic preview of every intended change. 3. Choose direct HTML or multipart creation, or resolve update targets from an includeIDs content read. 4. Validate supported elements, binary parts, request size, and idempotency behavior offline. 5. Apply one approved mutation and persist the returned page identity before downstream work. 6. Read back the page, compare semantic state, and preserve a compensation or quarantine plan. 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-core-workflow-b