Agent skill · software engineering · jeremylongshore
onenote-ci-integration
Build deterministic CI gates for a OneNote integration without exposing delegated credentials or mutating real notebooks. Use when testing client, HTML, pagination, or migration changes. Trigger with "test OneNote in CI", "gate OneNote contracts", or "add OneNote fixtures".
Why this skill is useful
Adds executable CI/CD pipeline scripts for OneNote integrations with Graph API that are not available in public documentation.
What it needs
Requires node, npm installed locally. Requires azure, github account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
OneNote Contract-Safe CI Overview Build deterministic CI gates for a OneNote integration without exposing delegated credentials or mutating real notebooks.. 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 Pull requests can prove request construction, constrained HTML, pagination, errors, and retry behavior offline. A live test requires a trusted branch, a dedicated user-bound sandbox, synthetic content, and an explicit read or write boundary. Recheck the dated evidence map before relying on mutable permissions, limits, SDK behavior, supported resources, or cloud availability. Authentication Keep delegated test credentials in an approved secret store. Fork jobs receive no secrets; logs record only tenant and user aliases, operation classes, status codes, and request identifiers. Instructions 1. Inventory OneNote calls, SDK versions, request builders, fixtures, and existing CI trust boundaries. 2. Define offline tests for service roots, paging, HTML normalization, update targets, errors, and throttling. 3. Separate untrusted pull-request jobs from protected trusted-branch smoke tests. 4. Scope any live lane to a synthetic notebook and one named delegated test user. 5. Make live writes opt-in, reversible, serialized, and followed by exact cleanup verification. 6. Gate promotion on negative cases, secret canaries, deterministic fixtures, and named rollback ownership. 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-ci-integration