What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
To create a Claude Code skill, make a folder for it, add a SKILL.md file with a clear description, and save it in the personal or project skills location. Claude may select the skill when a request matches its description; it is not guaranteed to load for every wording. You can also invoke it directly with a slash command.
How do I create a Claude Code skill?
A skill is a directory containing SKILL.md. The file combines YAML frontmatter—which can describe the skill and its trigger situations—with Markdown instructions for Claude. Anthropic’s Claude Code skills documentation describes the pattern: “Create a SKILL.md file with instructions, and Claude adds it to its toolkit.”
![Claude AI for Beginners Bible: [5 in 1] The Ultimate Guide to Automate Your Work, Save Hours Every Week, and Use AI for Real-World Results](https://m.media-amazon.com/images/I/415+fSJacsL._SL160_.jpg)
First choose whether the skill is just for you or should travel with a repository:
| Choice | Directory | Scope and sharing |
|---|---|---|
| Personal skill | ~/.claude/skills/<skill-name>/SKILL.md |
Available across projects for your user on that machine; it is not shared with teammates just by being there. |
| Repository skill | .claude/skills/<skill-name>/SKILL.md |
Applies to sessions for that repository. Commit the directory to share it with teammates. |
These are the two straightforward locations for a beginner setup. Anthropic documents additional arrangements for nested directories, plugins, enterprise settings, added directories, and claude.ai-synced skills; use the current official guide if your deployment uses one of those.
Where do I put a SKILL.md file?
Put the file inside its own skill folder—not directly in ~/.claude/skills/ or .claude/skills/. For example, a personal pull-request summary skill belongs at ~/.claude/skills/pr-summary/SKILL.md. To make it repository-scoped instead, use .claude/skills/pr-summary/SKILL.md.
Open Claude Code in the project where you want to work when testing a repository skill. A personal skill is machine-local; the project location makes sharing through the repository possible.
Rank #2
What should the skill file contain?
Start with a description in YAML frontmatter, then give Claude concise instructions in Markdown. The folder name supplies the slash command unless frontmatter name overrides it. Make the description specific about both the task and the situations in which the skill is useful; Claude uses it to help decide whether the skill is relevant.
---
description: Creates a concise pull request summary from the current changes. Use when asked to summarize a diff or draft a PR description.
---
Summarize the current changes in three bullets. Mention user-visible changes and any risks. Do not claim tests passed unless test results are available.This example would be saved as SKILL.md in the pr-summary folder. The instructions define what the skill should do; the description helps Claude identify when it fits.
How do I make a Claude Code skill load automatically?
Automatic selection depends on whether Claude judges the current request relevant to the skill’s description. It does not mean the skill is guaranteed to activate for every phrasing or in every session. A description such as “helps with code” gives less guidance than one naming the concrete task—such as summarizing a diff or drafting a pull-request description—and when to use it.
Test automatic selection with a request that plainly matches the description. For the example above, ask Claude to summarize the current diff or draft a PR description. Then test explicit invocation by entering /pr-summary. The slash command comes from the folder name unless the skill’s frontmatter supplies another name.
What should I check if the skill does not trigger?
- Check the path and file level. Confirm the folder is under one of the supported personal or repository locations and that
SKILL.mdis inside the named skill folder. - Check direct invocation. Enter the slash command, such as
/pr-summary, to see whether Claude Code recognizes the skill by name. - Check automatic selection separately. If the slash command works but a natural-language request does not select the skill, revise the description to name the actual tasks and wording you expect, then try both tests again. This can improve clarity but does not guarantee selection.
- Check your deployment. If you use a plugin, enterprise configuration, nested skills, an added directory, or claude.ai syncing, consult the official guide for that setup rather than assuming the simple paths cover it.
Do I need a paid plan to use Claude Code?
Claude Code access depends on account and deployment context. Anthropic’s setup documentation lists Anthropic Console, Claude App Pro or Max plans, and enterprise platforms among the access options. The appropriate route varies; a paid Claude App plan is not a universal requirement.
Recommended Free Tools
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
