Custom GPT vs a Claude skill you can share

A custom GPT lives in ChatGPT. A Claude skill is a folder with a SKILL.md that Claude loads for one job, and a kit is how you share that job so Claude, ChatGPT, and Codex run the latest version from one link.

OpenAI says custom GPTs retire on 11 December 2026. An Enterprise workspace with an approved deferral has until 11 February 2027. Existing GPTs keep working until that date. OpenAI's planned date for ending creation of new custom GPTs is 26 October 2026.

What each one is

A custom GPT is instructions, knowledge files, and connected apps inside ChatGPT. OpenAI's migration turns the instructions into a skill inside a plugin, copies the knowledge files into the plugin's reference files, and adds the connected apps. The GPT's custom actions do not transfer. The selected model does not carry over.

A Claude skill is a directory of instructions, scripts, and resources. Claude's docs say skills are on Pro, Max, Team, and Enterprise, and that they run in Claude's code sandbox, so Code execution and file creation have to be on.

A kit on CloneKit is the expert's process for one job. A read kit is files your AI reads. A run kit is steps your AI follows, then checks. Free read kits also download as a SKILL.md folder. CloneKit sends the steps. It does not run the kit's code. The buyer's AI does the work in the buyer's own accounts.

When the ChatGPT plugin is the better path

Stay with OpenAI's plugin when the people who need the GPT already work in one ChatGPT workspace. The migration copies the instructions, the files, and the connected apps for you. You stay inside ChatGPT. In an Enterprise workspace, sharing that plugin with the team needs the Share plugins permission. It is separate from the migration.

Today, a custom GPT is also easier to pass around than a skill file. You send a link. Sharing a Claude skill usually means the other person uploads the folder, unless you are on a Team or Enterprise plan that can deploy skills for the org. That GPT link has a scheduled end. OpenAI says the migrated plugin starts private, sharing settings do not carry over, and making the plugin public is a separate submission.

Keep the skill in Claude when the job needs Claude's code sandbox. A kit does not give you that sandbox.

When a kit is the one to share

Use a kit when the same process has to run in Claude, ChatGPT, Codex, Cursor, VS Code, Grok, or Claude Code, or when you need a link that is not a ChatGPT plugin submission.

You choose public, unlisted, or private. On the free plan you can keep 5 private kits. Public and unlisted kits are not capped. The other person connects CloneKit once, then asks their AI for the kit by name. You fix the kit once. Their next run gets the update.

Sharing is free. Using a kit is free. They pay for the AI they already use. A custom connector in ChatGPT needs a paid ChatGPT plan, and on some plans it can only read. If ChatGPT cannot save a kit, use Claude.

Selling is optional. A paid kit is a one-time price on Pro (US$12 a month) or Max (US$39 a month). On Pro you keep 90% of a sale from your own link and 75% when CloneKit found the buyer. On Max those shares are 95% and 80%, before any affiliate share and Stripe's fee. Selling works in the United States only. A buyer who has not read or run the kit can get a refund within 7 days. The plan details are on pricing.

A Team plan is US$20 per member, with at least 2 members. Members get Pro for their own kits. The organization's kits are free, and private team kits stay with the team.

How to move a GPT's job into a kit

1. Read the notice on your GPT. The date depends on the account that created it.
2. If everyone who needs it is in one ChatGPT workspace, use OpenAI's migration and test the plugin before you tell them to switch.
3. If they use Claude, Codex, or their own ChatGPT, make a kit. Connect your AI with the steps in how to use a kit in Claude, ChatGPT, or Codex.
4. Open @francisco/make-a-kit and tell your AI: "Interview me and write my CloneKit kit." It asks one question at a time, shows you a preview, and publishes when you say yes. You can also start from Make a kit.
5. Choose public or unlisted, or keep it private. Set a price only if you want to sell, then connect Stripe from Earnings.
6. Send the kit link. They add CloneKit once and ask for the kit. Browse kits to see the shape of a kit page. Setup for every app is in the docs.

There is no import from a custom GPT. You put the process in yourself, through the interview or your own files.

Gemini Gems

Google is replacing Gems with skills. On 30 September 2026 Google wrote that it will remove support for Gems starting in November 2026 for personal accounts, in March 2027 for Workspace business, enterprise, and nonprofit customers, and in June 2027 for Workspace education. Google says it will migrate existing Gems into skills.

Questions about a purchase go to support.