S Claude Has Skills Tools

Product surfaces

Claude.ai and API Skills

What changes when Claude Skills are used in Claude.ai or the Claude API instead of local Claude Code.

Updated 2026-07-06 8 min T4 source-backed

Primary source takeaway: Claude.ai, Claude Code, and API workflows share the skill concept, but each surface has its own activation and management flow.

Why the surface matters

The same skill idea travels across Claude products, but installation is not universal. A local folder path matters in Claude Code. A UI upload matters in Claude.ai. An API upload and identifier matter in a Messages API workflow.

When documenting a skill for users, say which surface you tested. "Works as a Claude Code project skill" is more useful than a vague "works with Claude" claim.

Claude.ai

In Claude.ai, skills are aimed at end-user workflows such as files, documents, design artifacts, and custom organizational procedures. The Help Center is the right source for plan availability, upload instructions, and product limitations because those rules can change faster than the portable file format.

For teams, Claude.ai custom skills are useful when the user experience should remain inside the chat app. If the workflow needs local repo access, shell commands, or codebase-specific automation, Claude Code may be the better surface.

Claude API

In the API, a skill is part of an application workflow. The developer uploads or references a package and then controls how the model call uses it. This is the right surface when you are building a product or internal system rather than asking an interactive agent to work in a local repository.

API usage raises additional concerns: package versioning, tenant isolation, file retention, audit logs, and explicit testing around tool calls or generated outputs. Those concerns belong in ordinary application engineering, not only in the skill text.

Portability expectations

Portable skill design still helps even when product-specific packaging differs. A clear SKILL.md, named references, deterministic scripts, and small assets are easier to adapt across surfaces than a giant prompt pasted into one product.

If a skill depends on a Claude Code-only path, a local executable, or a private service, document that dependency in the first screen of the skill so API and Claude.ai users do not assume it is portable.

FAQ

Is this site affiliated with Anthropic?

No. Claude Has Skills is an independent editorial guide. It links to Anthropic and Agent Skills primary sources so readers can verify product details directly.

Does a skill replace normal prompting?

No. A skill packages repeatable instructions and resources so the agent can load them when a task matches. The user still asks for a task, and the agent still decides what to read and run.

Can a skill work in every Claude product?

Conceptually yes, but practically only if its dependencies and packaging match the product surface. Always verify the target surface.

Where should API-specific behavior live?

Keep API lifecycle, authentication, and tenant behavior in application code and docs. Let the skill carry the task procedure and resources.

Primary Sources

Skills API guide

Anthropic Docs

Primary source for uploading and using skills with the Claude API.