--- name: onenote-local-dev-loop-a40c6654de65 description: >- 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". allowed-tools: Read,Glob,Grep,Write,Edit argument-hint: " " version: 1.7.0 license: MIT author: Jeremy Longshore tags: [saas, onenote, development] model: inherit effort: high compatibility: "Designed for Claude Code; live OneNote actions require network access, delegated authentication, and explicit approval" --- # 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. Invocation alone does not authorize network access, delegated credentials, tenant or notebook content, consent, file transfer, deployment, writes, spend, sharing changes, or deletion. ## Approval Boundaries Require the sandbox user before live access and explicit content-owner approval for writes, uploads, copies, sharing, or deletion. ## Error Handling - Fail closed if environment or user binding is absent. - Do not snapshot live page bodies into source control. - Do not make tests depend on undocumented search, delta, or webhook behavior. ## Output Return the dependency contract, fixture manifest, test commands, sandbox binding, live receipt, cleanup, and residual risks. Identify assumptions, owners, expirations, and evidence gaps explicitly. ## Examples - Test three pages across two opaque response pages. - Update one synthetic target and verify normalized output before restoring it. ## Validation Exercise and record these paths with expected and observed results: - production guard - secret canary - opaque paging - HTML normalization - 429 - sandbox cleanup ## Resources - [Current first-party evidence map](references/official-docs.md) — recheck dated sources before relying on mutable behavior. - Treat observed tenant behavior as environment-specific evidence, never a universal OneNote guarantee. --- Source attribution: jeremylongshore Original project: https://github.com/jeremylongshore/claude-code-plugins-plus-skills/blob/ab85a061f7bcc039dac13ee193de7a4cd4388571/plugins/saas-packs/onenote-pack/skills/onenote-local-dev-loop/SKILL.md License: MIT License information: https://opensource.org/license/mit Original upstream instructions; downloaded from Dave AI. ## Upstream license notice MIT License Copyright (c) 2025 Jeremy Longshore Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. # Dave AI resource metadata Creator / publisher: jeremylongshore Original project: https://github.com/jeremylongshore/claude-code-plugins-plus-skills/blob/ab85a061f7bcc039dac13ee193de7a4cd4388571/plugins/saas-packs/onenote-pack/skills/onenote-local-dev-loop/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering, Product Management Roles: Backend Developer, DevOps / SRE, Frontend Developer, Product Manager, Technical Product Manager Specialties: API, Backend, Design, DevOps, Word Documents, Frontend, Testing Tools: Graph Api, Msw, Onenote Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: b6402b06a50975ef68e185f1f2060fdbf627356b3c92794886997682c0dc8e87