onenote-prod-checklist

Production readiness checklist for OneNote Graph API integrations covering auth, rate limits, and failure modes. Use when preparing a OneNote integration for production deployment or conducting a launch review. Trigger with "onenote production checklist", "onenote launch review", "onenote prod ready".

Ir para a instalação

Repositório: jeremylongshore/claude-code-plugins-plus-skills
Última atividade na origem: 17 de julho de 2026 às 22:18
Idioma detectado do SKILL.md: inglês
Estrelas: 2.604
Forks: 378

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills --skill onenote-prod-checklist

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Explorador de arquivos

2 arquivos

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

name	onenote-prod-checklist
description	Production readiness checklist for OneNote Graph API integrations covering auth, rate limits, and failure modes. Use when preparing a OneNote integration for production deployment or conducting a launch review. Trigger with "onenote production checklist", "onenote launch review", "onenote prod ready".
allowed-tools	Read, Write, Edit, Grep
version	1.6.0
license	MIT
author	Jeremy Longshore <jeremy@intentsolutions.io>
tags	["saas","onenote","microsoft"]
compatibility	Designed for Claude Code

OneNote Production Checklist

Overview

OneNote integrations that work perfectly in development break in production in predictable ways: SharePoint document libraries exceed the 5,000-item view threshold and stop returning notebooks, image uploads silently truncate above 4MB, rate limits compound across users during business hours, and MSAL token caches lose state across container restarts. This skill is a comprehensive go/no-go checklist organized by failure category. Each item references the specific Graph API behavior that causes the production failure and provides the fix. Use this checklist during launch reviews — every unchecked item is a production incident waiting to happen.

Prerequisites

A functional OneNote integration that works in development/staging
Azure AD app registration with delegated permissions configured
Access to production monitoring infrastructure (logging, alerting)
Familiarity with your deployment environment (containers, VMs, serverless)
Completed onenote-security-basics and onenote-rate-limits skills

Instructions

1. Authentication Checklist

#	Check	Why it matters
1.1	Using delegated auth (DeviceCodeCredential or InteractiveBrowserCredential)	App-only auth (ClientSecretCredential) deprecated for OneNote March 31, 2025
1.2	MSAL token cache serialized to persistent storage	Container restarts lose in-memory cache; users forced to re-authenticate
1.3	Silent token renewal tested (call `acquire_token_silent` before every request)	Access tokens expire in 1 hour; without silent renewal, users hit 401 hourly
1.4	Refresh token 90-day expiry monitored	Inactive users' refresh tokens expire silently; need re-auth flow
1.5	Token cache file permissions set to 0600 (owner-only)	Cache contains refresh tokens — world-readable is a credential leak
1.6	Multi-tenant: `tid` claim validated on every token	Prevents cross-tenant data leakage from token reuse

Verification test:

import os, time

 ():
    
    
    response = client.me.onenote.notebooks.get()
     response.value   , 

    
    cache_path = os.path.expanduser()
     os.path.exists(cache_path), 
    stat = os.stat(cache_path)
     (stat.st_mode)[-:] == , 

    
    response2 = client.me.onenote.notebooks.get()
     response2.value   , 
    ()

#	Check	Why it matters
2.1	Retry-After header parsed and honored on 429 responses	Ignoring Retry-After escalates throttling duration
2.2	Exponential backoff implemented (not fixed delay)	Fixed delays waste time on short throttles, not enough on long ones
2.3	Per-user call tracking in place	One power user can consume the entire 600/min budget
2.4	Tenant-level rate tracked (10,000/10min across all users)	Dev testing per-user never reveals the tenant ceiling
2.5	Queue-based throttling for batch operations	Bursting 200 requests fails; queuing 20/second succeeds
2.6	429 alert configured (threshold: >1% of requests)	Early warning before users notice degradation

#	Code	Handler required
3.1	`400 Bad Request`	Validate XHTML before sending; log request body for debugging
3.2	`403 Forbidden`	Check scope in token; detect app-only auth usage; surface to user as "permissions needed"
3.3	`404 Not Found`	Handle deleted notebooks/sections/pages gracefully; clear local cache entry
3.4	`429 Too Many Requests`	Retry with Retry-After header (see section 2)
3.5	`500 Internal Server Error`	Retry with exponential backoff; log `request-id` header for Microsoft support
3.6	`502 Bad Gateway`	Retry once; if persistent, check for expired token edge case
3.7	`507 Insufficient Storage`	Section page limit hit; alert admin; suggest archival

#	Check	Why it matters
4.1	HTML validated as XHTML before POST (all tags closed, UTF-8)	Graph API silently strips invalid HTML — pages render incorrectly with no error
4.2	Page content size checked (< 4MB per page)	Oversized content silently truncates or returns 400
4.3	Image format validated (PNG, JPEG, GIF only)	Unsupported formats (WebP, AVIF) silently fail
4.4	Image size checked (< 10MB per image)	Large images cause timeout during page creation
4.5	Embedded file count checked (< 10 per page)	Too many attachments cause 507 errors

#	Check	Why it matters
5.1	Site-id resolved via Graph API (not hardcoded)	Site-ids change when sites are recreated or migrated
5.2	Document library item count monitored	Libraries exceeding 5,000 items hit SharePoint view threshold — API returns partial results
5.3	SharePoint throttling handled separately	SharePoint has its own throttling on top of Graph API limits
5.4	Site URL-to-ID resolution cached	Avoid repeated `GET /sites/{hostname}:/{path}` lookups

#	Check	Why it matters
6.1	429 rate dashboard with alerting	Detect throttling before users report issues
6.2	P95 latency tracked per endpoint	Identify slow endpoints before timeout cascades
6.3	Error rate per error code	Distinguish auth failures (401/403) from service issues (500/502)
6.4	Request-id logged for every failed call	Microsoft support requires this for incident investigation
6.5	Token refresh success rate tracked	Detect MSAL cache issues before users get logged out
6.6	Per-user call volume visible	Identify users driving disproportionate load

onenote-prod-checklist

Opções de instalação

Revise os arquivos de origem

OneNote Production Checklist

Overview

Prerequisites

Instructions

1. Authentication Checklist

OneNote Production Checklist

Overview

Prerequisites

Instructions

1. Authentication Checklist

2. Rate Limit Checklist

3. Error Handling Checklist

4. Content Validation Checklist

5. SharePoint-Specific Checklist

6. Monitoring Checklist

7. Health Check Endpoint

8. Go/No-Go Decision Matrix

Output

Error Handling

Examples

Resources

Next Steps

Category	Must-Have (blocks launch)	Should-Have (launch with plan)
Delegated auth working	1.1, 1.2, 1.3	1.4, 1.5, 1.6
Rate limits handled	2.1, 2.2	2.3, 2.4, 2.5, 2.6
Error codes handled	3.1, 3.2, 3.3, 3.4	3.5, 3.6, 3.7
Content valid	4.1, 4.2	4.3, 4.4, 4.5
Monitoring	6.1, 6.4	6.2, 6.3, 6.5, 6.6

Error	Cause	Fix
Health check returns "degraded"	OneNote API reachable but auth check failed	Token may be expired; trigger MSAL silent renewal; check cache persistence
Health check returns "unhealthy"	Both auth and OneNote checks failed	Service outage or network issue; check Microsoft 365 Service Health dashboard
`507 Insufficient Storage` in production	Section accumulated too many pages over time	Implement page archival (move old pages to archive section); monitor page counts
Silent HTML truncation	Invalid XHTML passed validation but Graph stripped content	Tighten validator; test with Graph Explorer before automated POST
SharePoint returns partial notebook list	Document library exceeded 5,000-item view threshold	Use `$filter` to narrow results; paginate with `$top` and `$skip`; or restructure library

onenote-prod-checklist

Informações da origem

Opções de instalação

Revise os arquivos de origem

Mais deste repositório

Mais deste repositório

OneNote Production Checklist

Overview

Prerequisites

Instructions

1. Authentication Checklist

OneNote Production Checklist

Overview

Prerequisites

Instructions

1. Authentication Checklist

2. Rate Limit Checklist

3. Error Handling Checklist

4. Content Validation Checklist

5. SharePoint-Specific Checklist

6. Monitoring Checklist

7. Health Check Endpoint

8. Go/No-Go Decision Matrix

Output

Error Handling

Examples

Resources

Next Steps