Guides
Does ChatGPT have skills like Claude? A 3D artist's comparison
Does ChatGPT have skills like Claude? How ChatGPT and Claude skills differ, who gets them, and how to write one for Blender and 3D work.
8 min read

Quick answer
Does ChatGPT have skills like Claude?
Yes. Reusable instruction folders, with optional scripts and examples, now exist in both assistants. ChatGPT skills live under Plugins for eligible Business, Enterprise, Healthcare and Edu users, and Codex reads them too. Claude skills work in claude.ai, Claude Code and the API. Both follow the open Agent Skills format built around a SKILL.md file.
At a glance
| Feature | ChatGPT skills | Claude skills |
|---|---|---|
| Plans | Business, Enterprise, Healthcare, Edu | Pro, Max, Ultra, Team, Enterprise (claude.ai) |
| Where | ChatGPT Plugins tab, Codex, API | claude.ai, Claude Code, API, Agent SDK |
| Create | Chat, editor or upload | Upload, or a SKILL.md folder on disk |
| Team sharing | Built-in sharing and admin roles | Team plans, or a git repo for Claude Code |
| Reads local files | Codex only | Claude Code only |
The short version
For about a year, "skills" was a Claude word. You wrote a folder with a SKILL.md file, and Claude read it when your request matched. OpenAI then added skills to Codex and to ChatGPT, and both companies now point at the same open format, Agent Skills. So the honest answer to "does ChatGPT have skills like Claude?" is yes. The real differences are in who can use them, where they run, and how you install them.
That matters if you do 3D work. A skill is where you write down the rules you keep retyping: your export scale, your naming scheme, your polygon budget, how your Blender scenes are organised. Write them once and either assistant follows them without being reminded.
What a skill actually is
Strip away the branding and a skill is three things:
- A short description that tells the assistant when the skill applies. "Use when the user exports a model for Unity or asks about FBX settings."
- Instructions that load when the skill triggers. These are the steps, rules and checks.
- Optional files: example prompts, reference sheets, small scripts. The assistant reads them only when it needs them.
Claude's documentation calls this progressive disclosure. Only the name and description (about 100 tokens per skill) sit in context all the time. The body of SKILL.md loads when the skill triggers, and bundled files load only when read. Scripts run in a sandbox, and only their output enters the conversation. That's why you can install a dozen skills without crowding out your actual conversation about a mesh.
Where ChatGPT skills live
From OpenAI's help article, as of November 2026:
- Who gets them: eligible ChatGPT Business, Enterprise, Healthcare and Edu users, subject to workspace settings. Codex supports skills as well, and the API supports skills that follow the Agent Skills standard.
- Where to find them: in the sidebar, select Plugins, then the Skills tab in the Plugin Directory. You'll see Installed, Created by me, Shared with me and skills shared by your workspace.
- How to make one: Create with chat (ChatGPT asks follow-up questions and uses its built-in skill-creator skill), Create with editor, or Upload from your computer.
- Safety: uploaded skills are scanned. Some get marked Needs Review, and risky ones are Blocked.
- Plugins vs skills: a plugin can bundle skills, apps or both. Skills are instructions; apps connect ChatGPT to outside services through MCP.
If you're on a personal Plus or Free plan and can't find skills, that's the reason: the article lists business and education plans.
Where Claude skills live
From Anthropic's docs:
- claude.ai: custom skills on Pro, Max, Ultra, Team and Enterprise, with code execution turned on.
- Claude Code: skills are folders on disk. Personal skills go in
~/.claude/skills/<name>/SKILL.md, project skills in.claude/skills/<name>/SKILL.mdinside the repo, and plugins can ship their own. You call one with/skill-name, or Claude loads it on its own when the description matches. - API and Agent SDK: skills run in the code execution container.
- No sync: a skill you upload to claude.ai doesn't appear in Claude Code, and the reverse is true too. Copy it to each place you use it.
The name field allows up to 64 characters of lowercase letters, numbers and hyphens, and it can't include "claude" or "anthropic". The description can be up to 1,024 characters. Spend those characters on when to use the skill. That's what decides whether it fires.

The differences that matter for 3D work
Who can use it today
Claude skills reach individual paid plans (Pro and up). ChatGPT skills are, for now, a workspace feature. A freelancer on a personal plan will find Claude easier to start with. A studio already on ChatGPT Enterprise gets admin controls: the admin Skills page shows owner, access, users and 30-day invocation counts for each skill.
Sharing across a team
ChatGPT has sharing built in. You share a skill with people or groups, or publish it to the workspace library, and admins decide who may create, upload, share or install skills. On Claude, the cleanest team route is Claude Code project skills in a git repo: everyone who clones the repo gets the same .claude/skills/ folder, and changes go through review like any other file.
Files on disk
This is the big one for Blender users. A Claude Code skill can sit next to your .blend files and tell Claude how your project is laid out. ChatGPT's web skills run in OpenAI's environment and don't see your disk. Codex, which runs locally, does: per Simon Willison's write-up, it reads skills from ~/.codex/skills.
Acting, not just knowing
A skill on its own only changes how the assistant thinks. To change a scene you need a connection, and that's MCP. In Claude, you add a Blender MCP server (setup guide) and the skill tells Claude how to use it. In ChatGPT, MCP servers arrive as apps inside plugins. Full MCP with write actions is limited to Business and Enterprise/Edu workspaces on the web. More on that in connecting an MCP server to ChatGPT.
A skill worth writing first: your export checklist
Whichever assistant you use, the most useful first skill for 3D work is boring: an export checklist. Here is the content, written as plain instructions. It works in either assistant because both read Markdown.
- Name:
game-export-check - Description: "Use when the user is about to export a model from Blender or asks whether a model is ready for Unity, Unreal, Godot or Roblox."
- Instructions:
- Ask which engine, if the user hasn't said.
- Check that scale is applied and that one Blender unit is one metre.
- Check that the origin sits at the base of the object.
- Check the polygon count against the project budget: 5,000 triangles for props unless the user says otherwise.
- For FBX, remind the user that Blender is Y forward, Z up. Use Apply Transform, or set Forward and Up in the exporter.
- For glTF, prefer GLB so textures travel inside the file.
- List anything that fails, then the fix, in that order.
Swap the numbers for your own. A skill that states your budget is worth more than any generic best-practice list, because it stops the assistant guessing. For a Roblox flavour of the same idea, see Roblox Claude skills.
Example prompts once the skill is installed
- "I'm exporting the lantern for Unity. Run the export check."
- "Is this chest ready for Roblox? Here's the stat panel: 18,400 triangles, scale 1.0, origin at the centre."
- "Write me a second skill like this one, but for 3D printing: watertight, wall thickness, STL."
The last one is worth trying in both assistants. ChatGPT's skill-creator and Claude's own skill-writing guidance will both draft a usable first version, which you then edit.
What skills can't do
- They don't make models. A skill is text. It can tell the assistant how to judge a mesh, not produce one. For actual geometry you need a generator: Blender through MCP for code-built shapes, or an image-to-3D service for organic props.
- They don't see your viewport unless a connector or screenshot gives them something to look at.
- They aren't a security boundary. Anthropic and OpenAI both say to use skills only from sources you trust, and to read every bundled file. A downloaded skill with a script inside is software. Audit it like software.
- They don't travel by themselves. Claude skills don't sync between surfaces, and ChatGPT's availability, installation and syncing differ by product. Keep the master copy in a folder you control.
Which should you use?
If you work alone on a personal plan and your files live on your machine, Claude skills with Claude Code (or claude.ai on Pro and up) are the shorter path. If your studio runs on ChatGPT Business or Enterprise and wants admin-managed sharing, ChatGPT skills fit. Either way, write the skill in plain Markdown and keep it in git. Because both sides read the Agent Skills format, the same file mostly works in both. For a side-by-side on the actual Blender work, read ChatGPT vs Claude for Blender.
Give your assistant real models to work with
Skills make an assistant consistent. They don't give it a 3D model. Vi3W turns a prompt, sketch or photo into a mesh. Then Add bones rigs it, Make it move animates it, and New paint job retextures it, before you export GLB or FBX. Its MCP server brings the same tools into Claude and ChatGPT. Try Vi3W.
Frequently asked questions
does chatgpt have skills like claude
Yes. ChatGPT skills are reusable workflows with instructions, examples and code, and ChatGPT uses them automatically when they help. They're offered to eligible Business, Enterprise, Healthcare and Edu users, and Codex supports skills too. The format follows the same Agent Skills standard Claude uses.
chatgpt skills vs custom gpt
A custom GPT is a separate assistant you open and talk to. A skill is a set of instructions ChatGPT pulls into an ordinary chat when the task matches, and several skills can work in one conversation. For a repeatable 3D workflow, like checking an export, a skill fits better.
chatgpt skills not showing
Check your plan first: skills are for eligible Business, Enterprise, Healthcare and Edu workspaces. Then check with your workspace admin, who can switch off creating, uploading, sharing or installing skills under Permissions & roles.
Last reviewed

