Agent skill · software engineering · jeremylongshore
onenote-local-dev-loop
Create a repeatable local OneNote development loop using synthetic fixtures, mocks, and an explicitly approved delegated sandbox. Use when implementing or debugging without touching real notebooks. Trigger with "develop OneNote locally", "mock OneNote API", or "set up OneNote sandbox".
Why this skill is useful
Adds a local development setup for OneNote integrations with mock Graph API responses, which the AI wouldn't reliably generate on its own.
What it needs
Requires node, python installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
OneNote Isolated Development Loop Overview Create a repeatable local OneNote development loop using synthetic fixtures, mocks, and an explicitly approved delegated sandbox.. 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 Offline fixtures should model v1.0 roots, opaque next links, constrained input HTML, normalized output HTML, generated update IDs, Graph error envelopes, and OneNote 429 responses without Retry-After. Recheck the dated evidence map before relying on mutable permissions, limits, SDK behavior, supported resources, or cloud availability. Authentication Use a dedicated sandbox user and encrypted delegated cache. Production tokens, tenant IDs, notebook IDs, titles, bodies, and binary resources never become fixtures. Instructions 1. Pin runtime and Graph SDK dependencies and place OneNote calls behind a narrow client boundary. 2. Create synthetic hierarchy, paging, HTML, update-target, error, and throttling fixtures with secret canaries. 3. Implement offline unit and contract tests before any network call. 4. Add a production-target guard based on explicit environment, tenant alias, user alias, and fixture IDs. 5. Run one approved read and optionally one reversible write in the delegated sandbox. 6. Reset the fixture, scan for production identifiers, and preserve the test 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-local-dev-loop