# Move a Custom GPT to a skill before custom GPTs retire on Dec 11, 2026

> Inventory your GPTs, export everything, migrate, rewrite the instructions as a SKILL.md that triggers at the right time, replace custom actions and test against the answers your GPT gives today.

- URL: https://paperchasewebb.ai/bots/marketplace/items/move-a-custom-gpt-to-a-skill/
- Type: Agent use case pack
- Category: Solo business
- By: PaperChaseWebb
- Works with: Claude Code, Codex, ChatGPT (named in the listing); Plain .md
- Price: $14 USD
- Difficulty: Beginner
- Setup time: 20 min
- Time to result: About one hour per simple GPT
- Format: Markdown (.md) file, move-a-custom-gpt-to-a-skill.md
- Version: 1.0, updated 2026-10-15
- License: Personal and commercial use by the buyer. No resale, redistribution or republishing as a competing pack. See Downloads in the terms.

## What you end up with

Each GPT you rely on becomes a tested skill with a precise description, its reference files and a plan for any custom action, before the retirement date.

## What you get

- One .md playbook with the dates and what transfers, sourced from OpenAI's help center (checked Oct 15, 2026)
- Inventory worksheet and an export checklist to run before anything becomes read-only
- SKILL.md template and rewrite rules for old GPT instructions
- Actions to apps or MCP decision table
- Test set template, user notice template and five prompts

## Who it is for

People who built Custom GPTs for themselves, a team or clients and need them working as skills before Dec 11, 2026, especially GPTs that use knowledge files or custom actions.

## Tools needed

- ChatGPT, with My GPTs and plugins available on your account: the migration itself
- Any chat model: rewrites instructions and compares answers
- Claude Code, Codex or other SKILL.md tools (optional): reuse the same skill elsewhere
- You need: At least one Custom GPT you created
- You need: Access to the account or workspace where it was created

Cost to run: No extra cost for the playbook. Plugin and app access depends on your ChatGPT plan.

## How it works

1. **Inventory.** List every GPT, where it was created, who uses it and whether it has custom actions. Decide move, merge or let go. Expected: A short move list ordered by risk.
2. **Export.** Save instructions, knowledge files, starters, action schemas and 5 to 10 real prompts with today's answers. Expected: A folder per GPT you can rebuild from.
3. **Publish and migrate.** Publish final edits, then use Migrate to plugin from My GPTs when it is available for your account. Expected: A private plugin with the GPT's instructions as a skill.
4. **Rewrite the skill.** Tighten the description, add a do-not-use line, move long facts into reference files and keep one worked example. Expected: A SKILL.md that triggers on the right requests only.
5. **Replace actions.** Use the decision table: app connector, vendor MCP server, custom MCP server or a manual step. Expected: Each action's operations covered or listed as dropped.
6. **Test and tell users.** Compare old and new answers on the saved prompts and one hard case, then send the notice. Expected: Passes recorded, users switched before the date.

## Sample prompt: Rewrite GPT instructions as a skill (Any chat model)

```
Below are the instructions from my Custom GPT [name]: [paste instructions.md].
Rewrite them as a SKILL.md with a header (name, description) and these sections: When to use, Inputs to collect, Steps, Output format, Rules, Example.
- Write the description so it triggers on: [list request types], and not on: [list nearby requests].
- Move long reference material out and tell me which file each part should go into.
- Keep every rule that prevents a real mistake. Delete persona and filler.
- List anything in the original you removed and why, so I can check.
```

The description decides when a skill runs. Test it with requests that should and should not trigger it.

## Free preview of move-a-custom-gpt-to-a-skill.md

````markdown
# Move a Custom GPT to a skill before custom GPTs retire on Dec 11, 2026

PaperChase agent use case pack (playbook), version 1.0. For creators of Custom GPTs moving to ChatGPT plugins and skills, with notes on reusing the same skill in other agents that read SKILL.md. Time: about one hour per simple GPT, longer for GPTs with custom actions.

## The dates (checked Oct 15, 2026)

OpenAI's help center says custom GPTs are scheduled to retire on Dec 11, 2026, and that creators can migrate a GPT to a plugin, where its instructions become a skill. Affected Enterprise workspaces with an approved deferral have until Feb 11, 2027. For Enterprise workspaces, creation of new custom GPTs is planned to end on Oct 26, 2026. OpenAI notes dates can change, so follow the notice in your own account.

Source: OpenAI Help Center, "Custom GPT retirement and migration FAQ", https://help.openai.com/en/articles/20001519-custom-gpt-retirement-and-migration-faq

## What carries over and what does not

According to that FAQ:

| Part of your GPT | In the migration |
|---|---|
| Instructions | Become a skill in the new plugin |
| Knowledge files | Copied into the plugin's reference files |
| Connected apps | Added to the plugin as apps |
| Custom actions | Do not transfer. Rebuild with an available app or a custom MCP server |
| Selected model | Does not carry over |
| Sharing settings and users | Do not carry over. The plugin starts private |
| Drafts and unpublished edits | Do not transfer. Migration uses the latest published version |
| The original GPT | Becomes read-only after migration, usable until retirement |

## Why a straight migration is not enough

GPT instructions were written to be read on every message by one model. A skill is picked up when its description matches the request and may run alongside other skills and apps. Instructions that worked as a GPT can be ignored, triggered at the wrong time or clash with other skills unless you rewrite them a little.

## The plan

1. Inventory your GPTs and decide which to move
2. Export everything before you touch anything
3. Publish final edits, then migrate
4. Rewrite the instructions as a clear skill
5. Replace custom actions
6. Test against saved prompts and one hard case
7. Tell your users and reuse the skill elsewhere

## Contents

1. Inventory worksheet
2. Export checklist
3. Migration steps
4. SKILL.md template and rewrite rules
5. Actions to apps or MCP decision table
6. Test set template
7. User notice template
8. Prompts for each stage
````

## Worth knowing

- Dates and migration details come from OpenAI's help center as of Oct 15, 2026. OpenAI says they can change; your account notice takes priority.
- Not affiliated with or endorsed by OpenAI.
- Custom actions do not transfer. Rebuilding them can need technical setup and, in workspaces, admin permissions.

## Questions

**Where does the Dec 11, 2026 date come from?** OpenAI's help center article Custom GPT retirement and migration FAQ, checked on Oct 15, 2026. It also gives Feb 11, 2027 for Enterprise workspaces with an approved deferral. The playbook links the source.

**Can I reuse the skill outside ChatGPT?** Often, yes. The SKILL.md format is supported by several agents, including Claude Code and Codex. Folder locations and limits differ, so check each tool's docs.

## How to buy

$14 one time at https://paperchasewebb.ai/bots/marketplace/items/move-a-custom-gpt-to-a-skill/. Stripe checkout, then an instant download page; the download link is also in your emailed receipt.

Seller: PaperChaseWebb Inc., mgmt@paperchasewebb.com