Agent skill · software engineering · jeremylongshore
notion-upgrade-migration
Upgrade a Notion integration across SDK or API contracts with inventory, compatibility tests, staged rollout, and rollback. Use when adopting current data-source, block, trash, or SDK behavior. Trigger with "upgrade Notion API", "migrate Notion SDK", or "update Notion version".
Why this skill is useful
Adds detailed upgrade and migration scripts for the Notion SDK that are not widely documented.
What it needs
Requires git, npm, pip installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Notion SDK and API Upgrade Control Overview Upgrade a Notion integration across SDK or API contracts with inventory, compatibility tests, staged rollout, and rollback.. This workflow produces an auditable decision or artifact before any live action. Prerequisites Current first-party Notion documentation and the selected integration's tested API-version contract. A named workspace owner, content or data owner, and operation owner. Synthetic or approved non-production fixtures with secrets and workspace content removed. Current Contract Recent contracts separated databases from data sources and changed search filters; the current contract also changes block placement, trash state, and a meeting-note block identity. SDK support and API opt-in are related but separate choices. Recheck the dated evidence map before relying on mutable fields, endpoints, versions, limits, or delivery behavior. Authentication Run upgrade tests with a dedicated non-production connection and synthetic content. Never rotate production credentials merely to test compatibility. Instructions 1. Inventory every client, explicit or default API version, SDK pin, operation, object type, fixture, and webhook subscription version. 2. Read both intervening first-party upgrade guides and build a before/after contract matrix. 3. Replace database-query assumptions with data-source identities and update search and schema operations. 4. Update current block position, trash-state, and meeting-note handling plus unknown-field tolerance. 5. Run offline fixtures, dual-read comparisons, denied paths, reversible sandbox writes, and rollback tests. 6. Canary one bounded workload, reconcile results, and promote only with a retained rollback artifact. 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/notion-upgrade-migration