Move your team from Claude to Claude Code.
Each person gets a short interview, then a personalized step-by-step guide showing exactly where their saved work, prompts, and projects land in Claude Code — and the few things that need a manual step, walked through. You send one invite; nobody becomes the help desk, and nothing in Claude is changed or cancelled. Want to see where you’re paying for both first? Run the free audit.
Skills follow the Agent Skills open standard (agentskills.io) and work in both products with the same SKILL.md shape: YAML frontmatter (`name`, `description`, `when_to_use`, etc.) plus Markdown instructions and optional scripts. On Claude.ai you install a skill by uploading the zipped folder under Settings → Capabilities → Skills (Team/Enterprise can publish to an org directory). In Claude Code you place the skill folder at `~/.claude/skills/<name>/` (personal) or `.claude/skills/<name>/` (project, checked in) and invoke with `/<name>` or via auto-trigger. Same skill artifact, different distribution: Claude.ai uses upload-to-account, Claude Code uses files-on-disk.
- Warning: Claude Code-only frontmatter keys (`allowed-tools`, `disallowed-tools`, `context: fork`, `agent`, `hooks`, `shell`, etc.) may be ignored or behave differently on claude.ai — the more agentic surface area on Claude Code lets skills do more.
- Warning: Bundled Claude Code skills (`/code-review`, `/debug`, `/loop`, `/batch`, `/claude-api`, `/run`, `/verify`) are not auto-present on claude.ai; the reverse is also true for chat-flavored skills.
- Warning: On Team/Enterprise Claude.ai, org admins publish skills to a directory; in Claude Code, project skills are shared via git and enterprise skills via managed settings — set the right scope.
- Warning: Claude.ai surfaces skills inside chat and Cowork; Claude Code surfaces them inside CLI/IDE sessions — the same skill folder usually works in both, but always test.