Agent skill · research science · jeremylongshore
onenote-common-errors
Classify Microsoft Graph OneNote failures from redacted response evidence and choose a bounded recovery path. Use when handling authentication, permission, provisioning, validation, throttling, or content errors. Trigger with "fix OneNote error", "classify OneNote 403", or "debug OneNote request".
Why this skill is useful
Provides detailed diagnostic steps and fixes for specific OneNote Graph API errors that the AI wouldn't reliably generate on its own.
What it needs
Requires onenote account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
OneNote Error Triage and Recovery Overview Classify Microsoft Graph OneNote failures from redacted response evidence and choose a bounded recovery path.. 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 HTTP status, Graph error code, inner error, request identifier, target location, auth context, and operation are separate evidence. OneNote 429 responses do not promise a Retry-After header, and a user, group, or site root can fail for different access or provisioning reasons. Recheck the dated evidence map before relying on mutable permissions, limits, SDK behavior, supported resources, or cloud availability. Authentication Record a delegated token alias, tenant alias, signed-in user alias, granted Notes scope, and target ownership. Never paste or decode bearer tokens into an incident artifact. Instructions 1. Capture one redacted response envelope and the exact read or write operation. 2. Classify the failure as transport, authentication, authorization, provisioning, identity, validation, throttling, conflict, or service state. 3. Check the user, group, or site root and the notebook, section, page, or resource identity separately. 4. Apply the smallest class-specific correction without broadening permissions by default. 5. Retry only retryable classes within a strict attempt and elapsed-time budget. 6. Verify recovery with the least-privilege read or synthetic fixture that reproduces the original path. 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-common-errors--cd3a8e