Vi3W
Skip to content

Guides

Can you use Claude skills in claude.ai, or only in Claude Code?

Where Claude skills work: claude.ai, Claude Desktop, Claude Code and the API. Plans, install paths, syncing and which suits Blender and 3D work.

6 min read

Two glowing orbs: one holding a rolled blueprint scroll, the other holding a small hammer and building a low-poly tower
Illustration. The chat apps suit planning and one-off jobs; Claude Code suits repeatable project work.

Quick answer

Can I use Claude skills in claude.ai or only in Claude Code?

Both. Skills work in claude.ai, Claude Desktop, Claude Code and the API, but they don't sync. In the claude.ai apps you upload custom skills on a paid plan with code execution enabled. In Claude Code a skill is a folder on disk, per project or personal. For Blender work, Claude Code is usually the better home.

Skills work on four surfaces

Anthropic's Agent Skills overview lists four places a skill can live:

  1. claude.ai (and the Claude Desktop app), where you upload custom skills.
  2. Claude Code, where a skill is a folder on disk.
  3. The Claude API, where skills run in the code execution tool's container.
  4. The Agent SDK, for agents you build yourself.

The format is the same everywhere: a folder with a SKILL.md holding a name, a description and instructions. The catch is that custom skills don't sync between surfaces. A skill in your repo isn't in claude.ai, and a skill uploaded through the API isn't in either. (One exception: Claude Code can load skills enabled on your claude.ai account.) Keep one source copy, ideally in version control, and install it where you need it.

Skills in claude.ai and Claude Desktop

Who can use them

Custom skills in claude.ai are available on the Pro, Max, Ultra, Team and Enterprise plans, with code execution enabled. Skills rely on it, because a skill's scripts run in that environment. If you can't find skills, check that setting first.

How you add one

You upload the skill folder as a custom skill. After that, Claude decides when to use it based on the description, just as in Claude Code.

What it's good for in 3D work

  • Planning and briefs: a skill that turns a rough idea into a production brief or a set of prompts for a 3D generator.
  • Reviewing: a skill that checks a pasted Blender script for risky calls, or reviews an export settings screenshot.
  • Remote tools: claude.ai can use custom connectors, which are remote MCP servers added under Customize > Connectors. A skill there can sequence a hosted tool such as the Vi3W MCP server (live from today) to generate, rig, retexture or clean up models, without anything installed locally.

Where it's weaker

Local tools. Blender MCP servers run on your machine, so Claude Desktop needs them added to its local config, and the claude.ai website can't reach them at all. Claude Desktop works with local servers. See Blender MCP with Claude.

Skills in Claude Code

Where they go

From the Claude Code skills docs:

  • Project skills: .claude/skills/<skill-name>/SKILL.md inside the repository. Everyone who clones the project gets them.
  • Personal skills: ~/.claude/skills/<skill-name>/SKILL.md, available in every project you open.
  • Plugin skills: <plugin>/skills/<skill-name>/SKILL.md, installed from a marketplace.
  • Nested skills: in a subfolder's own .claude/skills/, loaded the first time Claude works on a file there.
  • Enterprise: managed by your organisation's settings.

Claude Code can also use skills enabled on your claude.ai account.

How you call them

  • Type /skill-name at the start of a message to run it directly.
  • Or just ask. Claude loads the skill when your request matches its description, unless you set disable-model-invocation: true in the frontmatter.

Claude Code's frontmatter has extra fields the plain format doesn't need: allowed-tools, arguments, argument-hint, model, paths and more. For Blender work, disable-model-invocation: true on any skill that writes or exports files is a sensible default.

Why it suits Blender work

  • Your files are right there. Claude Code runs in your project folder, so it can read your .blend exports, textures and engine project, and edit scripts on disk.
  • Local MCP is first-class. Add a Blender MCP server with Claude Code's MCP configuration, keep Blender open, and Claude Code works on the live scene from your terminal.
  • Skills live in version control. Commit .claude/skills/, and your team's export rules change through pull requests like any other code. See Sharing Claude skills across a 3D team.
A puppet linked to floating control rings
Illustration. A project skill is a control rig for Claude: set once, reused every session.

Which one to use

Use claude.ai or Claude Desktop when

  • you're planning, writing briefs or reviewing, with no files to change
  • your tools are hosted, such as a remote 3D generation MCP server

Use Claude Code when

  • you're working on a project with real files: a game repo, a Blender asset library, an engine project
  • you're driving Blender through a local MCP server
  • the skill has to be the same for everyone on the team

Many 3D artists use both: Claude Desktop with connectors for quick generation and planning, and Claude Code for the project work.

Moving a skill between surfaces

  1. Keep the skill folder in a git repository.
  2. For Claude Code, it lives at .claude/skills/<name>/ in that repo, so nothing more is needed.
  3. For claude.ai, upload the same folder as a custom skill.
  4. When you change it, re-upload. There is no automatic sync, so put a version line in the description or body so you can tell copies apart.

Check two things that behave differently between surfaces:

  • Claude Code-only frontmatter (such as allowed-tools) may be ignored elsewhere, so don't rely on it for safety outside Claude Code.
  • Paths. A script that reads ../assets/ works in your repo, not in a claude.ai upload.

A worked example: one skill, both surfaces

Say your team has a skill called prop-brief that turns a loose idea into a brief and a generator prompt. It's useful to the concept artist in claude.ai and to the technical artist in Claude Code.

  1. The skill lives in the game repo at .claude/skills/prop-brief/. The technical artist's Claude Code picks it up automatically.
  2. The concept artist downloads the same folder and uploads it as a custom skill in claude.ai.
  3. In claude.ai, the concept artist writes "brief for a mossy stone well, stylised", gets the brief, and, with the Vi3W connector added, generates the first version.
  4. In Claude Code, the technical artist runs the import and QA skills on the downloaded GLB, inside the project.

Same instructions, two surfaces, and a clear hand-off. When the brief format changes, the change lands in git first and the concept artist re-uploads.

What doesn't work

  • The claude.ai website reaching local Blender. It connects to remote MCP servers from Anthropic's cloud, not from your computer. Use Claude Desktop or Claude Code for local servers.
  • Custom skills on the Free plan in claude.ai. They need a paid plan with code execution.
  • One upload covering everywhere. Skills don't sync. Plan for two installs.

Next step

Write your first Blender skill with How to write a SKILL.md for Blender, and put it in a repo from day one. To give it models to work with, create a Vi3W account and connect the Vi3W MCP server to whichever Claude you use.

Frequently asked questions

is claude skills free

Skills carry no separate fee, but in claude.ai custom skills need a Pro, Max, Ultra, Team or Enterprise plan with code execution turned on. When a skill runs, its instructions count toward your normal usage.

claude skills not showing up

Check the surface first: a skill in your Claude Code project won't appear in claude.ai, and API uploads are separate. In claude.ai, confirm code execution is on. In Claude Code, confirm the path is .claude/skills/<name>/SKILL.md and that the frontmatter is valid.

how to install claude skills from github

In Claude Code, add the repository as a plugin marketplace (for Anthropic's repo: /plugin marketplace add anthropics/skills) and install from it, or copy a skill's folder into .claude/skills/. For claude.ai, download the folder and upload it as a custom skill. Read the files first.

Last reviewed