Agent skill · product strategy · jeremylongshore
onenote-prod-checklist
Decide whether a OneNote integration is ready for production from evidence across delegated access, content safety, correctness, limits, operations, and rollback. Use when reviewing a launch or material change. Trigger with "review OneNote production readiness", "OneNote go-live checklist", or "approve OneNote launch".
Why this skill is useful
Adds a comprehensive production readiness checklist with specific Graph API behaviors and verification scripts for OneNote integrations.
What it needs
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 Production Readiness Decision Overview Decide whether a OneNote integration is ready for production from evidence across delegated access, content safety, correctness, limits, operations, and rollback.. 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 A launch is ready only when the actual user-bound auth lifecycle, approved content roots, supported v1.0 operations, pagination, HTML semantics, throttling, monitoring, and reconciliation are evidenced together. Recheck the dated evidence map before relying on mutable permissions, limits, SDK behavior, supported resources, or cloud availability. Authentication Verify delegated scope, consent owner, token-cache protection, tenant and user binding, revocation, and reauthentication. App-only fallback is a launch blocker. Instructions 1. Verify immutable artifact, dependency, configuration, migration, and test receipts. 2. Confirm account type, tenant, user, app registration, delegated scopes, and approved user, group, or site roots. 3. Review reads, writes, HTML, binary parts, paging, errors, limits, and unsupported-feature assumptions. 4. Review data classification, logs, retention, queues, monitoring, incidents, and support custody. 5. Exercise canary, failure, revocation, 429, rollback, and reconciliation paths. 6. Issue GO, CONDITIONAL GO, or NO-GO with owners, expirations, and rollback triggers. 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-prod-checklist--255311