Agent skill · software engineering · jeremylongshore
onenote-debug-bundle
Assemble a reproducible, content-safe OneNote diagnostic bundle for engineering or Microsoft support. Use when an incident needs portable evidence. Trigger with "collect OneNote debug bundle", "redact OneNote diagnostics", or "prepare OneNote support case".
Why this skill is useful
Adds executable TypeScript middleware for automatic diagnostic logging and JWT token inspection for OneNote API calls, which are not covered in public documentation.
What it needs
Requires @microsoft/microsoft-graph-client, node installed locally. 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 Redacted Diagnostic Bundle Overview Assemble a reproducible, content-safe OneNote diagnostic bundle for engineering or Microsoft support.. 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 useful bundle separates runtime, SDK, location, delegated identity, consent, request, response, throttling, and deployment evidence. Raw notebook HTML and bearer tokens are not diagnostic defaults. Recheck the dated evidence map before relying on mutable permissions, limits, SDK behavior, supported resources, or cloud availability. Authentication Record credential provenance, tenant and user aliases, granted scope names, expiry class, and a one-way fingerprint only. Never include access or refresh tokens. Instructions 1. Define the incident window, affected operation, data classification, audience, and retention period. 2. Collect dependency locks, sanitized configuration keys, deployment revision, and location type. 3. Capture redacted request method, route class, response status, Graph code, request identifier, latency, and retry count. 4. Scan all artifacts for tokens, secrets, user identifiers, titles, HTML bodies, and binary content. 5. Reproduce with a synthetic or read-only fixture and record observed versus expected behavior. 6. Seal the manifest with file hashes, redaction evidence, custodian, expiry, and approved transfer channel. 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-debug-bundle--8c237d