How to Add Skills to Claude Code and Verify Setup

Start with one practical task

Install one skill in the intended scope and open the project where you expect it to appear. Run a task that matches its description and check that it follows the documented steps.

Installing and authoring solve different needs

Installing adds an existing workflow maintained by its publisher. Authoring creates instructions specific to your project. A plugin can distribute skills alongside other components, while a local skill folder keeps a focused workflow close to the code it serves.

Choose personal or project scope

Current Claude Code documentation lists ~/.claude/skills for personal skills and .claude/skills inside a repository for project skills. Personal scope suits work reused across projects; repository scope keeps a shared workflow versioned with the application.

Give the skill a recognizable identity

SKILL.md combines metadata with workflow instructions. The name identifies the skill, while its description helps Claude determine when it applies. A focused description tied to an actual task is easier to distinguish from other skills than a broad claim to handle every development job.

Confirm availability in the intended session

The skill must be available where the task runs. Local folders, cloud sessions and synced resources can have different loading behavior. A representative task helps separate a discovery problem from missing files, unavailable tools or instructions that do not fit the job.

A few more details

Sources & maker notes

This guide is based on the cited documentation and maker sources. vibeforthat has not run an independent installation or end-to-end product test for this article.

• code.claude.com