Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
sanity-io avatar

Plugin Transfer

  • 1 installs
  • 17 repo stars
  • Updated August 2, 2026
  • sanity-io/plugins

Helps with ai & agent building tasks during AI-assisted development.

About

plugin-transfer is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted coding.

  • plugin-transfer
  • AI & Agent Building
  • AI-coding skill

Plugin Transfer by the numbers

  • 1 all-time installs (skills.sh)
  • Ranked #14,103 of 16,556 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 3, 2026 (Skillselion catalog sync)
npx skills add https://github.com/sanity-io/plugins --skill plugin-transfer

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1
repo stars17
Last updatedAugust 2, 2026
Repositorysanity-io/plugins

What it does

Helps with ai & agent building tasks during AI-assisted development.

Files

SKILL.mdMarkdownGitHub ↗

Plugin Transfer

Use this skill when migrating an existing plugin repository into sanity-io/plugins.

Start Here

Always start with:

pnpm generate "copy plugin"

This is the canonical transfer flow and scaffolds monorepo-compatible files, test-studio wiring, and migration TODOs.

Required vs Unnecessary Config

Keep and maintain these monorepo config files in the transferred plugin:

  • package.json
  • package.config.ts
  • tsconfig.json
  • tsconfig.build.json
  • vitest.config.ts

Do not copy standalone-repo-only setup such as custom root CI/build/lint/test configs that are already handled by this monorepo.

Required Transfer Checks

1. Keep the original plugin README.md in the new plugin workspace. 2. Add and verify the generated test-studio example under dev/test-studio/src/<plugin-example>/index.tsx. 3. Confirm the plugin is wired in dev/test-studio/sanity.config.ts. 4. Do not update .github/CODEOWNERS during transfer unless explicitly requested. 5. Add a changeset with a major bump for the transferred plugin. 6. Update the root README.md plugins table with the transferred plugin.

Anything Else To Consider

  • Review copied dependencies and peer dependencies carefully.
  • Run pnpm build, pnpm test, and pnpm dev to verify migration quality.

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.