onenote-local-dev-loop
/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".
- Author
- jeremylongshore ↗
- Repository
- tons-of-skills-marketplace ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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".
Triggers from the description
Arguments
/onenote-local-dev-loop <repository> <feature> <sandbox-user>
Original author 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".
How it works
- Overview
- Prerequisites
- Current Contract
- Authentication
- Instructions
- Tool Discipline
- Approval Boundaries
- Error Handling
- Output
- Examples
SKILL.md preview
--- name: onenote-local-dev-loop 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: "<repository> <feature> <sandbox-user>" version: 1.7.0 license: MIT author: Jeremy Longshore <jeremy@intentsolutions.io> 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.
Files in this package (2)
- SKILL.md 4 KB
- references/official-docs.md 3 KB
Versions
The database has no other skills named onenote-local-dev-loop.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version ca84c62757f1 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100notion-local-dev-loop
Create a repeatable local Notion development loop using fixtures, mocks, and an explicitly shared sandbox. Use when implementing or debugging without touching production content. Trigger with "develop Notion locally", "mock Notion API", or "set up Notion sandbox". - 100onenote-sdk-patterns
Build a testable Microsoft Graph OneNote client boundary with delegated auth, opaque pagination, HTML operations, errors, and throttling. Use when writing or reviewing integration code. Trigger with "design OneNote client", "review OneNote SDK", or "update OneNote patterns". - 100onenote
Create, read, and manage OneNote notebooks, sections, and pages via Microsoft Graph API. Use when someone asks to "create OneNote pages", "read OneNote notes", "automate OneNote", "save to OneNote", "extract OneNote content", "organize OneNote notebooks", or "OneNote API".… - 98onenote-desktop
Control Microsoft OneNote desktop through direct Windows PowerShell COM automation, including raw one-off COM scripts. Use when an agent needs to inspect OneNote installation state, list notebooks/sections/pages, read or write page XML, create or update pages, navigate OneNote,… - 100customerio-local-dev-loop
Configure Customer.io local development workflow. Use when setting up local testing, development environment, or offline development for Customer.io integrations. Trigger with phrases like "customer.io local dev", "test customer.io locally", "customer.io development… - 95one-note
OneNote API integration with managed OAuth via Microsoft Graph. Access notebooks, sections, section groups, and pages. Use this skill when users want to create or manage OneNote notebooks, organize notes, or work with page content. For other third party apps, use the api-gateway…