Sanity Studio Upgrade
Produces a tailored Sanity Studio upgrade plan by inspecting the repository's installed versions, config, and source, then reporting only the breaking changes that actually apply. Covers Studio v3 and later; v2 projects are identified and redirected, not planned. Use this skill whenever someone wants to upgrade, migrate, or modernize a Sanity Studio across one or more major versions from v3 onward, asks what will break if they bump the `sanity` package, asks why their Studio broke after an upgrade, or asks how far behind their Studio is. Triggers on "upgrade sanity studio", "migrate our studio
Install
/plugin marketplace add sanity-io/agent-toolkitThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sanity-io/agent-toolkit --skill sanity-studio-upgradegit clone --depth 1 https://github.com/sanity-io/agent-toolkit.git /tmp/agent-toolkit
mkdir -p ~/.claude/skills
cp -r /tmp/agent-toolkit/skills/sanity-studio-upgrade ~/.claude/skills/sanity-studio-upgradePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Sanity Studio upgrade planner Generate an upgrade plan for the Sanity Studio in the current repository. The plan's value is **subtraction**. A list of every breaking change between two versions already exists; it is called the changelog, and it is not useful to someone mid-upgrade. This skill produces the much shorter list of changes that apply to *this* repository, plus the questions only a human can answer. ## Three rules that determine whether the output is trustworthy **1. Never state a version number from memory. Look it up, and confirm it exists.** Package versions change weekly. Every version in the report must come from either the repository's lockfile (for current state) or a live registry query (for targets). If a lookup is not possible, say so in the report rather than guessing. A plan that names a stale "latest" is worse than no plan, because the reader will act on it. There is a second, worse version of this failure: a version number that was never published at all, arrived at by assuming one package tracks another's numbering. That one fails at install. Any version you are about to describe as "lockstep" or "matches core" needs an existence check first.
Details
- Skill name
sanity-studio-upgrade- Repository
- sanity-io/agent-toolkit
- Path
skills/sanity-studio-upgrade/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
- Listed in
- heilcheng/awesome-agent-skills
FAQ
What does the Sanity Studio Upgrade skill do?
Produces a tailored Sanity Studio upgrade plan by inspecting the repository's installed versions, config, and source, then reporting only the breaking changes that actually apply. Covers Studio v3 and later; v2 projects are identified and redirected, not planned. Use this skill whenever someone wants to upgrade, migrate, or modernize a Sanity Studio across one or more major versions from v3 onward, asks what will break if they bump the `sanity` package, asks why their Studio broke after an upgrade, or asks how far behind their Studio is. Triggers on "upgrade sanity studio", "migrate our studio
How do I install the Sanity Studio Upgrade skill?
Claude Code plugin: /plugin marketplace add sanity-io/agent-toolkit. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Sanity Studio Upgrade popular?
It lives in sanity-io/agent-toolkit, which has 200 GitHub stars and 32 forks, and is included in 1 curated skill list.
Related skills
Content Experimentation Best Practices
200sanity-io/agent-toolkit
Content experimentation and A/B testing guidance covering experiment design, hypotheses, metrics, sample size, statistical foundations, CMS-managed variants, and common analysis pitfalls. Use this skill when planning experiments, setting up variants, choosing success metrics, interpreting statistical results, or building experimentation workflows in a CMS or frontend stack.
Content Modeling Best Practices
200sanity-io/agent-toolkit
Structured content modeling guidance for schema design, content architecture, content reuse, references versus embedded objects, separation of concerns, and taxonomies across Sanity and other headless CMSes. Use this skill when designing or refactoring content types, deciding field shapes, debating reusable versus nested content, planning omnichannel content models, or reviewing whether a schema is too page-shaped or presentation-driven.
Portable Text Conversion
200sanity-io/agent-toolkit
Convert HTML and Markdown content into Portable Text blocks for Sanity. Use when migrating content from legacy CMSs, importing HTML or Markdown into Sanity, building content pipelines that ingest external content, converting rich text between formats, or programmatically creating Portable Text documents. Covers @portabletext/markdown (markdownToPortableText), @portabletext/block-tools (htmlToBlocks), custom deserializers, and the Portable Text specification for manual block construction.
Mckinsey Consultant
330fleurytian/awesome-claude-skills
McKinsey顾问式问题解决系统。从商业问题出发,通过假设驱动的结构化分析方法,生成McKinsey风格研究报告和PPT。融合Problem Solving方法论、MECE原则、Issue Tree拆解、Hypotheses形成、Dummy Page设计、智能数据收集和专业PPT生成能力。
China Teaser
896jwangkun/claude-for-financial-services-cn
Draft anonymous one-page company teasers for A-share sell-side M&A processes. Creates compelling blind profiles without revealing the company's identity, adapted for Chinese market conventions. Triggers on "A股Teaser", "盲审材料", "blind profile China", "anonymous teaser A-share", or "sell-side teaser".
IDA Skill
239miunasu/IDA-Skill
IDA Pro 逆向分析。通过 IDAPython 脚本获取反汇编、反编译、字符串、导入表、交叉引用等信息。
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.