No. Claude Code skills do not work in the Claude desktop app. Skills are a Claude Code feature and require the Claude Code CLI or a supported IDE extension. The Claude desktop app is a separate product with a different architecture that does not support SKILL.md files.
TL;DR: Claude Code skills require the Claude Code CLI or IDE extension. They do not transfer to the Claude desktop app. The desktop app's Projects feature is a partial substitute: it stores persistent context but cannot invoke tools, read files dynamically, or route to reference files on demand.
The desktop app is where conversations happen. Claude Code is where work happens. Skills belong in the second category. At AEM, this is the most common onboarding question we field: people arrive expecting a single Claude interface, find two, and wonder why their skills vanished.
Why Don't Skills Work in the Claude Desktop App?
Claude Code skills depend on three things the desktop app does not have: file system access, the tool-use loop, and SKILL.md resolution. Without all three, a skill cannot run. The desktop app handles conversations; skills execute structured workflows that read files, route through reference content, and enforce output contracts across multiple tool calls.
- File system access: Skills instruct Claude to read specific files at specific times. The desktop app cannot read files from your local machine without an MCP connection.
- The tool-use loop: Claude Code's agentic execution model runs skills as structured workflows across multiple tool calls. The desktop app handles conversations, not multi-step tool sequences.
- SKILL.md resolution: Claude Code resolves skill files from the directory hierarchy at session start. The desktop app has no concept of a project directory or a
.claude/skills/folder.
The Claude Code VS Code extension alone has over 12 million installs (Visual Studio Marketplace, May 2026). That is the gap in a single number: one environment has the infrastructure, the other does not.
"The single biggest predictor of whether an agent works reliably is whether the instructions are written as a closed spec, not an open suggestion." — Boris Cherny, TypeScript compiler team, Anthropic (2024)
Skills are closed specs that execute inside Claude Code's structured environment. Without that environment, the spec has nowhere to run.
What Is the Claude Desktop App Good For?
The Claude desktop app is a chat interface for general tasks: writing, analysis, summarization, and Q&A. It supports multi-turn conversations, document uploads, and the Projects feature for persistent context. With MCP connections configured, it can also access external tools and databases. No local file system access required.
74% of developers worldwide had adopted specialised AI tools by January 2026 (JetBrains, April 2026, n=24,534). The desktop app is where many of those developers start. For one-off tasks that do not involve your local codebase, it is fast and requires no project setup. For workflows that involve file editing, code generation, and multi-step tool sequences inside a project, Claude Code is the right tool.
Is There a Skill Equivalent in the Claude Desktop App?
Claude desktop's Projects feature is the closest analog. A Project stores a persistent system prompt that applies to every conversation in that project. You can write context, instructions, and behavioral rules in that system prompt, similar to what CLAUDE.md does in a Claude Code project.
The differences from a production Claude Code skill are significant:
- No on-demand reference files: Skills load specific reference files at specific steps. A desktop Project system prompt is a static block of text loaded once.
- No slash command invocation: Skills have named triggers. A desktop Project has one static context with no routing.
- No output contracts: Skills define exactly what Claude should and should not produce. A desktop system prompt can request this, but without the structured execution loop, adherence is substantially less reliable.
43% of developers use standalone chat AI tools for coding tasks at work, while IDE-embedded tools like Claude Code are used by 18% (JetBrains, April 2026). Both have a place. The question is which job you are doing.
We hear this question in consultation calls regularly. The honest answer: if you need the consistency of a production-grade skill, you need Claude Code. Desktop Projects work for personal context loading and simple behavioral guidelines. For complex, multi-step tasks that touch your local file system, they are not a replacement.
For more on what Claude Code skills can do, see What Is a Claude Code Skill?.
Can I Connect the Desktop App to Claude Code Skills via MCP?
MCP servers can give the Claude desktop app access to tools and data sources. In principle, you could build an MCP server that exposes your skill content to the desktop app. But this is a workaround, not native support, and the execution model remains different. There are now over 9,400 public MCP servers and the MCP SDK receives 97 million downloads per month (Anthropic, MCP registry snapshot April 2026). The protocol is maturing fast, but it bridges data access, not execution architecture.
The value of a Claude Code skill is not just the text inside SKILL.md. It is the combination of instructions, structured invocation, dynamic reference loading, and output contracts running inside Claude Code's agentic loop. An MCP connection can surface the text content of a skill. It cannot replicate the execution architecture.
What If I Want Skills But Don't Want to Use a Terminal?
Install the Claude Code extension for VS Code or JetBrains. Both IDEs provide a full Claude Code interface without requiring a standalone terminal. You get the same SKILL.md resolution, the same slash command invocation, and the same tool access. The skill layer works identically whether you launch from a terminal or from inside an IDE.
10% of developers in the Stack Overflow 2025 Developer Survey (65,000+ respondents) reported using Claude Code as their primary IDE, most of them through an IDE extension rather than a raw terminal.
For more on using Claude Code skills in VS Code, see Do Claude Code Skills Work in VS Code or Only in the Terminal?.
FAQ
Claude Code skills do not work in the Claude desktop app, and there is no workaround that replicates full skill execution. The desktop app's Projects feature covers static context and simple behavioral guidelines. For dynamic file access, structured invocation, and output contract enforcement, you need Claude Code. The questions below address the most common edge cases.
Will Claude Code skills ever work in the Claude desktop app?
Anthropic has not announced desktop app support for Claude Code skills as of 2026. The architecture gap between a chat interface and an agentic file-system-aware environment is significant. Partial support through the Projects feature or MCP integrations is more plausible than native SKILL.md resolution.
Can I copy a SKILL.md into a Claude desktop Project system prompt?
Yes. Copy the body of a SKILL.md (everything after the closing frontmatter ---) into a desktop Project's system prompt. This gives the desktop app access to the skill's instructions. The dynamic reference loading, structured invocation, and output contract enforcement that Claude Code provides are not available, but the core instructions work.
Is Claude Code available on mobile?
No. Claude Code requires a terminal or IDE extension. The Claude mobile app is a separate chat interface without SKILL.md support.
What's the difference between the Claude desktop app and Claude Code?
The Claude desktop app is a chat interface for general tasks. Claude Code is a developer-focused agentic system with file system access, tool use, and the skill layer. They run the same underlying models but operate differently. Many developers use both: the desktop app for quick Q&A and Claude Code for development workflows.
Can I use the same Claude subscription for both the desktop app and Claude Code?
Yes. A Claude Pro subscription includes access to both the desktop app and Claude Code. You do not need a separate subscription for each product.
Last updated: 2026-05-03