Agent skill

Notion Upgrade Migration

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Upgrade a Notion integration across SDK or API contracts with inventory, compatibility tests, staged rollout, and rollback.

MITAuto-check passedDevOps & Cloud

Install Notion Upgrade Migration

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill notion-upgrade-migration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace notion-upgrade-migration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/notion-upgrade-migration .claude/skills/notion-upgrade-migration && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
notion-upgrade-migration
GitHub stars
2.8k
Token cost
~1k tokens
SKILL.md length
428 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Upgrade a Notion integration across SDK or API contracts with inventory, compatibility tests, staged rollout, and rollback.

  • Works in 6 steps: Inventory every client, explicit or… → Read both intervening first-party… → Replace database-query assumptions with… → …
  • Adopting current data-source
  • SKILL.md covers Overview, Prerequisites, Current Contract and Authentication, plus 8 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Notion Upgrade Migration is an agent skill from jeremylongshore/tons-of-skills-marketplace. 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".

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/official-docs.md`). Compatibility notes: Designed for Claude Code; live Notion actions require network access and explicit approval

It sits in DevOps & Cloud, covering API design. It works with Notion. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Adopting current data-source
  • With upgrade Notion API
  • Migrate Notion SDK
  • Update Notion version

Example prompts

  • “upgrade Notion API”
  • “migrate Notion SDK”
  • “update Notion version”
  • “/notion-upgrade-migration”

Requirements

  • Compatibility (from SKILL.md): Designed for Claude Code; live Notion actions require network access and explicit approval
  • Pre-approved tools (allowed-tools): Read, Glob, Grep, Write, Edit

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  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.

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep
    • Write
    • Edit

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code; live Notion actions require network access and explicit approval

    From compatibility in the SKILL.md frontmatter.

Context cost

Notion Upgrade Migration loads about 1k tokens when it runs, and up to ~1.5k if it reads all its reference files. Until then it costs about 76 tokens; SKILL.md has 428 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~76
When it runs · the whole SKILL.md, loaded when a task matches
~1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 428 words, ~1,002 tokens.

Download SKILL.mdSave it as .claude/skills/notion-upgrade-migration/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
notion-upgrade-migration
description
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".
allowed-tools
Read, Glob, Grep, Write, Edit
compatibility
Designed for Claude Code; live Notion actions require network access and explicit approval
argument-hint
<current-contract> <target-contract> <repository>
version
1.40.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, notion, upgrade
model
inherit
effort
high

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. Invocation alone does not authorize network access, credentials, workspace content, user data, file transfer, deployment, capability or sharing changes, writes, spend, or deletion.

Show full SKILL.md (151 more words)Show less

Approval Boundaries

Require release approval for version or SDK promotion and content-owner approval for any live compatibility write or migration.

Error Handling

  • Do not update the SDK and silently inherit a new API contract.
  • Do not cast old fixtures into new types to make tests pass.
  • Rollback on object-identity, trash-state, or reconciliation divergence.

Output

Return the inventory, contract delta, code and fixture changes, compatibility matrix, canary evidence, decision, and rollback package. Identify assumptions, owners, expirations, and evidence gaps explicitly.

Examples

  • Migrate a database query to a data-source query using the resolved data-source ID.
  • Verify current trash and block-position behavior in a reversible sandbox.

Validation

Exercise and record these paths with expected and observed results:

  • multiple data sources
  • search filter
  • block position
  • trash state
  • unknown field
  • rollback

Resources

  • Current first-party evidence map — recheck dated sources before relying on mutable behavior.
  • Treat observed tenant behavior as environment-specific evidence, never a universal Notion guarantee.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/.curated/notion-upgrade-migration of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/official-docs.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Notion Upgrade Migration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Notion Upgrade Migration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Notion Upgrade Migration this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1kAutomated safety check: PassMIT
Code PatternsAedelon/claude-code-blueprint120—~1.2kAutomated safety check: PassCustom licence
One Way Doorjamditis/claude-skills-journalism416—~5kAutomated safety check: NotesMIT
Service Catalog Entrymohitagw15856/pm-claude-skills1.4k—~3.7kAutomated safety check: PassMIT
Production Gradenagisanzenin/production-grade181—~16kAutomated safety check: NotesNone
Data Scraper Agentaffaan-m/ECC277k5 repos~6.3kAutomated safety check: NotesMIT

Similar skills

  • Code Patterns

    Aedelon/claude-code-blueprint

    Reference patterns for REST APIs, pytest/vitest testing, Docker multi-stage builds, GitHub Actions CI/CD, PostgreSQL, TypeScript generics, Python async, and React Server Components.

    120 GitHub stars~1.2k tokensUpdated 7 mo ago
    DevOps & CloudAuto-check passed
  • One Way Door

    jamditis/claude-skills-journalism

    Flags irreversible decisions before commit. An agent skill from jamditis/claude-skills-journalism.

    416 GitHub stars~5k tokensUpdated 6 days ago
    DevOps & CloudAuto-check: notes
  • Service Catalog Entry

    mohitagw15856/pm-claude-skills

    Write a service catalog entry for a microservice or internal platform service — covering service identity, purpose, architecture context, SLAs, API contract summary, data classification…

    1.4k GitHub stars~3.7k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Production Grade

    nagisanzenin/production-grade

    A skill your agent uses when the user wants to build, create, or develop anything — websites, apps, APIs, services, platforms.

    181 GitHub stars~16k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check: notes
  • Data Scraper Agent

    affaan-m/ECC

    Build a fully automated AI-powered data collection agent for any public source — job boards, prices, news, GitHub, sports, anything.

    277k GitHub starsUsed in 5 repos~6.3k tokens
    DevOps & CloudAuto-check: notes
  • Build, refactor, or review Effect v4 HttpApi services on Cloudflare Workers.

    105 GitHub stars~1.4k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Works with

Questions about Notion Upgrade Migration

What does Notion Upgrade Migration do?

Upgrade a Notion integration across SDK or API contracts with inventory, compatibility tests, staged rollout, and rollback. Notion Upgrade Migration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Upgrade a Notion integration across SDK or API contracts with inventory, compatibility tests, staged rollout, and rollback.

When should I use Notion Upgrade Migration?

Notion Upgrade Migration fits situations like: adopting current data-source; with upgrade Notion API; migrate Notion SDK; update Notion version.

How do I install Notion Upgrade Migration in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill notion-upgrade-migration -a claude-code`. Or copy the skill folder (skills/.curated/notion-upgrade-migration in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/notion-upgrade-migration in your project. Claude Code loads it when a task matches its description.

How do I install Notion Upgrade Migration in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill notion-upgrade-migration -a codex`. Or copy the skill folder (skills/.curated/notion-upgrade-migration in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/notion-upgrade-migration in your project. Codex loads it when a task matches its description.

Can I use Notion Upgrade Migration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill notion-upgrade-migration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/notion-upgrade-migration, .gemini/skills/notion-upgrade-migration, .github/skills/notion-upgrade-migration and .opencode/skills/notion-upgrade-migration in your project.

What does Notion Upgrade Migration need to run?

SKILL.md names no scripts, command-line tools or credentials: Notion Upgrade Migration is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Glob, Grep, Write, Edit. Compatibility (from SKILL.md): Designed for Claude Code; live Notion actions require network access and explicit approval.

Does Notion Upgrade Migration access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Notion Upgrade Migration safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Notion Upgrade Migration use?

Notion Upgrade Migration is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Notion Upgrade Migration use?

About 1k tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 544 tokens, read only when the agent opens those files.

What are the alternatives to Notion Upgrade Migration?

Skills that share tags, products or a category with Notion Upgrade Migration: Code Patterns (Aedelon/claude-code-blueprint, 120 stars), One Way Door (jamditis/claude-skills-journalism, 416 stars), Service Catalog Entry (mohitagw15856/pm-claude-skills, 1.4k stars) and Production Grade (nagisanzenin/production-grade, 181 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Notion Upgrade Migration?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.