Skip to content
Skills Library
Programming · Building & coding

onenote-sdk-patterns

/onenote-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".

Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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".

Triggers from the description

design OneNote clientreview OneNote SDKupdate OneNote patterns

Arguments

/onenote-sdk-patterns <language> <operations> <location-types>
Original author description

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".

How it works

  1. Overview
  2. Prerequisites
  3. Current Contract
  4. Authentication
  5. Instructions
  6. Tool Discipline
  7. Approval Boundaries
  8. Error Handling
  9. Output
  10. Examples
Original SKILL.md headings · 68 lines, 457 words
SKILL.md preview
---
name: onenote-sdk-patterns
description: >-
  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".
allowed-tools: Read,Glob,Grep,Write,Edit
argument-hint: "<language> <operations> <location-types>"
version: 1.7.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags: [saas, onenote, sdk]
model: inherit
effort: high
compatibility: "Designed for Claude Code; live OneNote actions require network access, delegated authentication, and explicit approval"
---
# OneNote Versioned Client Boundary

## Overview

Build a testable Microsoft Graph OneNote client boundary with delegated auth, opaque pagination, HTML operations, errors, and throttling.. 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

SDK versions change independently from Graph v1.0. Keep stable REST semantics behind typed operations, preserve opaque next links, retain Graph error and request identifiers, and treat generated snippets as starting evidence rather than a pinned package contract. Recheck the dated evidence map before relying on mutable permissions, limits, SDK behavior, supported resources, or cloud availability.

## Authentication

Inject a delegated credential provider bound to app, tenant, user, environment, and scopes. Application credentials and token logging are forbidden for OneNote operations.

## Instructions

1. Inventory runtime, installed SDK, target v1.0 operations, locations, and generated-code assumptions.
2. Define typed read hierarchy, page-content, create, update, and operation-result contracts.
3. Centralize delegated auth, request IDs, error classification, throttling, timeouts, and redaction.
4. Model opaque next links and semantic HTML normalization without leaking transport details to callers.
5. Add offline contract fixtures for additive fields, paging, errors, 429 without Retry-After, and ambiguous writes.
6. Canary the boundary against one approved synthetic root and record the compatibility matrix.

## 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 code-owner approval for implementation changes and the sandbox owner for live tests. Live writes need a separate content-owner approval.

## Error Handling

- Do not hardcode a remembered latest SDK version.
- Do not rebuild next links or silently retry ambiguous writes.
- Fail closed when delegated user or location binding is absent.

## Output

Return the client contract, dependency evidence, auth binding, operation types, fixtures, compatibility results, and migration notes. Identify assumptions, owners, expirations, and evidence gaps explicitly.

## Examples

- Paginate a synthetic section across multiple opaque links.
- Preserve a OneNote inner error and request identifier without returning page content.

## Validation

Exercise and record these paths with expected and observed results:

- additive field
- opaque link
- normalized HTML
- 429
- ambiguous write
- revoked session

## 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-sdk-patterns.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 061e7cc4a979 (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

  • 100onenote-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".
  • 100onenote-install-auth
    Establish a least-privilege delegated Microsoft Graph connection for OneNote with tested consent and lifecycle controls. Use when registering or repairing OneNote authentication. Trigger with "set up OneNote auth", "register OneNote app", or "review Notes permissions".
  • 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,…
  • 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…
  • 100msgraph-sdk
    Integrate Microsoft Graph SDK into any project — .NET, TypeScript/JavaScript, or Python. Covers auth patterns (client credentials, OBO, managed identity), SDK setup, calling Graph APIs, batching, delta queries, change notifications, throttling, and permission scopes. Use when…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.