Short answer
Claude Code does not currently document a dedicated “install skill from URL” workflow in the way Codex does. The current official customization primitives are slash commands in .claude/commands/ or ~/.claude/commands/, plus shared project instructions in CLAUDE.md and live integrations through MCP.
If an Aescut entry is a plain skill rather than an MCP server, the practical move is to port its instructions into a slash command or project memory file instead of looking for a hidden claude skill add command.
Recommended path
- 01
Decide whether the entry is a plain skill or an MCP server
If the registry entry exposes runtime tools, install it as an MCP server. If it is instruction-first, adapt it into a slash command or a CLAUDE.md workflow.
- 02
Store reusable instructions where Claude Code already looks
Project commands live in .claude/commands/. Personal commands live in ~/.claude/commands/. Shared project memory lives in ./CLAUDE.md.
- 03
Restart or reopen the session and test a narrow prompt
Use a simple task to make sure the command or memory is being picked up before you trust it in a production workflow.
What Claude Code officially supports today
Anthropic’s current docs emphasize three building blocks: slash commands, CLAUDE.md memory files, and MCP servers. That is the supported, current path. If you see older references online to "skill install" flows, treat them carefully and verify against the current docs before teaching users to rely on them.
Recommended pattern for Aescut entries
If the Aescut entry is a playbook, checklist, or prompt bundle, create a markdown command in .claude/commands/ and preserve the narrow scope of the original skill. If it relies on live tools, install the corresponding MCP server instead and keep the instructions in CLAUDE.md or the command description.
# .claude/commands/release-check.md
Review the current branch for release readiness.
Steps:
- confirm tests and lint targets
- inspect changelog changes
- call the approved GitHub MCP tools if they are available
Common mistakes
- Treating a plain markdown skill as if Claude Code will auto-install it from a repository.
- Putting team-shared instructions in a personal location, then wondering why colleagues do not get the same behavior.
- Forgetting that
CLAUDE.mdis a better place for persistent project rules than a one-off prompt pasted into chat.
Sources and further reading
Related questions
Installation
How do I install an MCP server on Claude Code?
Current Claude Code MCP setup, config locations, CLI shortcuts, and common verification steps.
Skills And MCP Basics
What is an AI skill?
A practical definition of AI skills, how they are packaged, and where they fit in an agent workflow.
Skills And MCP Basics
What is the difference between a skill and an MCP server?
A technical comparison of skills and MCP servers, with examples of when each is the better fit.