How to Install Skills in Claude Code: Every Method

Claude Code accepts skills through three installation paths: the built-in plugin browser, manual file placement, and the mdskills.ai marketplace. Each method targets different workflows, from quick experiments to production deployments.

Plugin browser installation

The plugin browser sits inside Claude Code's interface. Open it through the extensions panel or the command palette (Ctrl+Shift+P then "Browse Skills"). The browser pulls from mdskills.ai's curated collection.

Search filters narrow results by category, language, or functionality. Each skill shows its description, required dependencies, and user ratings. Click "Install" to download the SKILL.md file directly into your workspace.

The browser handles file placement automatically. Skills install to .claude/skills/ by default, though you can change this in settings. Dependencies get flagged before installation, so you know what external tools each skill needs.

One limitation: the browser only shows public skills. Private or company-internal skills require manual installation.

Manual installation process

Manual installation gives you complete control over skill placement and organization. Create a skill file or download one from external sources.

Place SKILL.md files anywhere in your project structure. Claude Code scans these locations during startup:

/project-root/.claude/skills/
/project-root/skills/
/project-root/.skills/

You can also nest skills in subdirectories for organization:

/.claude/skills/data/csv-parser.SKILL.md
/.claude/skills/web/api-client.SKILL.md
/.claude/skills/testing/mock-generator.SKILL.md

The file extension matters. Claude Code only recognizes files ending in .SKILL.md or SKILL.md. Other markdown files get ignored during skill discovery.

Restart Claude Code or run "Reload Skills" from the command palette after adding new files manually.

Marketplace integration

The mdskills.ai marketplace offers the largest skill collection. Access it through browse skills or directly from Claude Code's marketplace tab.

Skills on the marketplace include detailed documentation, usage examples, and community ratings. Many show real-world performance metrics from other users.

Download options vary by skill. Some provide direct .SKILL.md downloads. Others bundle multiple related skills in a zip archive. Premium skills might require authentication or payment processing.

The marketplace also hosts MCP servers and rules files alongside skills. Make sure you're downloading the right file type for your needs.

File structure and scoping

Claude Code treats skill files differently based on their location. Understanding this scoping helps with organization and debugging.

Global skills in your user directory affect all projects:

~/.claude/skills/

Project skills only apply to the current workspace:

/current-project/.claude/skills/

Local skills override global ones when names conflict. If you have csv-parser.SKILL.md in both locations, Claude Code uses the project-local version.

The SKILL.md spec defines the file format. Each skill needs specific metadata headers for proper recognition:

# Skill Name

**Type:** function
**Description:** Brief description
**Dependencies:** none

Missing metadata causes Claude Code to skip the skill during loading.

Troubleshooting common issues

Skills not appearing in the command palette usually means placement or naming problems. Check the file extension first. my-skill.md won't work, but my-skill.SKILL.md will.

Syntax errors in the skill file prevent loading. The SKILL.md spec requires specific markdown formatting. Common mistakes include missing required headers or malformed function signatures.

Dependency conflicts show up as runtime errors. Some skills expect specific Python packages, Node modules, or system tools. The skill's documentation should list requirements, but many authors forget to document everything.

Claude Code's output panel shows skill loading errors. Open it through View > Output, then select "Claude Code Skills" from the dropdown.

Permission errors happen when skill files lack read access. This affects Windows users more than others. Run chmod +r *.SKILL.md in your skills directory to fix it.

Version conflicts occur when multiple skills define the same function name. Claude Code uses the last-loaded version, which depends on alphabetical file ordering. Rename conflicting skills to avoid issues.

Performance considerations

Skills with heavy dependencies slow Claude Code's startup time. Python skills that import large libraries like pandas or tensorflow add several seconds to initialization.

The skill loading order affects performance. Claude Code processes files alphabetically within each directory. Frequently used skills should have names starting with early letters.

Consider skill size when organizing. Large skills (over 100KB) take longer to parse and index. Break complex skills into smaller, focused pieces when possible.

Best practices recommend keeping skills under 50 functions each. Smaller skills load faster and debug easier than monolithic ones.

Skill validation and updates

Claude Code validates skill syntax during loading but doesn't check runtime behavior. A skill might load successfully but fail when executed.

The validation process checks:

• Required metadata presence
• Markdown syntax correctness
• Function signature formatting
• Dependency declarations

Auto-updates work differently per installation method. Plugin browser skills update automatically when new versions appear. Manual installations require you to replace files yourself. Marketplace skills might offer update notifications depending on the author's configuration.

Version tracking happens through the skill's metadata. Authors should increment version numbers in the description when making changes. Claude Code doesn't enforce this, so consistency varies between skill creators.

Skills installed through different methods can coexist. You might have core utilities from the plugin browser, custom company skills installed manually, and specialized tools from the marketplace. Claude Code merges them into a single command palette.

The installation method affects how you share skills with teammates. Plugin browser skills work the same for everyone. Manual skills require sharing the actual files. Marketplace skills might have licensing restrictions on redistribution.