How to Install Claude Skills

Installing a Claude Skill usually means placing a skill folder somewhere Claude can load it. The exact path depends on whether you want the skill available globally or only inside one project.

Before you install anything

Do a quick safety check:

1. Read the SKILL.md file.
2. Check the source repository and author.
3. Look for scripts or commands.
4. Check whether the skill handles secrets, files, network calls, or shell execution.
5. Prefer skills with clear scope and a strong security grade.

If a skill asks for broad access or hides what it does, skip it.

Option 1: Install from a skill page

On Skills Directory:

1. Open a skill page.
2. Review the description, source, and security grade.
3. Copy the install command or source repository.
4. Install into your Claude skills directory.

A common manual pattern is:

mkdir -p ~/.claude/skills
cd ~/.claude/skills
git clone https://github.com/example/example-skill.git example-skill

The exact command depends on how the upstream author packages the skill.

Option 2: Install a project-local skill

Project-local skills are useful when a workflow applies to one repo only.

mkdir -p .claude/skills/my-project-skill
cat > .claude/skills/my-project-skill/SKILL.md <<'EOF'
---
name: my-project-skill
description: Use when working on this repository's release checklist.
---

# Release Checklist

1. Review pending changes.
2. Run tests.
3. Check docs.
4. Summarize risks.
5. Ask before deploying.
EOF

Project-local skills are easier to review with the rest of your code and can be shared with teammates.

Option 3: Create a simple global skill

Global skills are useful for workflows you use across many projects.

mkdir -p ~/.claude/skills/commit-helper
cat > ~/.claude/skills/commit-helper/SKILL.md <<'EOF'
---
name: commit-helper
description: Helps write clear conventional commit messages.
---

# Commit Helper

Use conventional commits:

- feat: new feature
- fix: bug fix
- docs: documentation
- refactor: internal code change
- test: tests
- chore: maintenance

Keep the subject line short and imperative.
EOF

Global vs project skills

Verify the install

After installing, ask Claude to list or use the skill:

What skills do you have available?

or:

Use the commit-helper skill to draft a commit message for these changes.

If Claude does not see the skill, check the folder name, SKILL.md filename, frontmatter, and the client-specific install path.

Keep your skill stack lean

Do not install every interesting skill you find. Too many overlapping skills can create noisy or conflicting behavior. Start with 3-5 high-trust skills and add more only when a repeated workflow needs them.

Next steps

• Browse Claude Skills
• Best Claude Code Skills
• Secure Claude Skills