October DealsAmazon USOctober deal check: compare before you payAmazon US: current deals, useful picks and tech finds.Check DealsSlow PC?RecommendedPC slow today? Run a repair scan before it gets worseResolve common Windows issues and optimize system performance.Scan NowOctober DealsAmazon USDeal season is back - check today's better picksAmazon US: current deals, useful picks and tech finds.See Picks×
Skip to content
World desk4 min

Create a Claude Code Skill: Personal vs. Project Setup and Automatic Selection

Create a Claude Code skill by adding a described SKILL.md file at a personal or repository path, then test automatic selection and its slash command.
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

To create a Claude Code skill, make a folder for it, add a SKILL.md file with a clear description, then test it both with a matching request and its slash command. Claude may select a skill automatically when it judges the request relevant; it is not guaranteed to load for every wording.

Where should you put a SKILL.md file?

Choose the location based on who should use the skill. Anthropic’s Claude Code skills guide documents these two common choices:

As an Amazon Associate I earn from qualifying purchases.

Scope Path Who can use it Sharing
Personal ~/.claude/skills/<skill-name>/SKILL.md Your Claude Code work across projects on this machine Machine-local; it is not shared with teammates just by creating it
Repository .claude/skills/<skill-name>/SKILL.md Claude Code sessions in that repository Share it by committing the skill directory to the repository

For example, a personal skill named pr-summary belongs at ~/.claude/skills/pr-summary/SKILL.md. A repository version belongs at .claude/skills/pr-summary/SKILL.md. The folder name supplies the slash command name unless the frontmatter sets a different name.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

The official guide also describes other locations and configurations, including nested directories, added directories, plugins, enterprise setups, and claude.ai-synced skills. If you use one of those, follow the current documentation for that deployment rather than assuming the two beginner paths cover it.

How do you create a Claude Code skill?

  1. Choose the scope. Use ~/.claude/skills/ for a personal skill across your projects on this machine, or .claude/skills/ in a repository if you want to share the skill with collaborators.
  2. Create a directory for the skill. For the example below, name it pr-summary and create ~/.claude/skills/pr-summary/ or .claude/skills/pr-summary/, depending on scope.
  3. Add SKILL.md. Put it directly inside that directory. Start with YAML frontmatter bounded by --- lines, include a useful description, and follow it with concise Markdown instructions.
  4. Write a specific description and instructions. Say what task the skill handles and when it is useful. The description helps Claude decide whether the skill is relevant to a request; the instructions tell it what to do after the skill is used.
  5. Open Claude Code in the relevant project and test it. First give it a request that closely matches the description. Then invoke the skill directly with its slash command and check whether the response follows the instructions.

Anthropic describes the basic model this way: “Create a SKILL.md file with instructions, and Claude adds it to its toolkit.” See the official skills guide for current details on supported frontmatter and additional skill behavior.

What should a minimal skill file contain?

This example asks Claude to prepare a pull request summary from the current changes:

---
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.

Save the file as SKILL.md inside the pr-summary directory. With no custom frontmatter name, the expected direct invocation is /pr-summary, based on the folder name. The example is a practical starting point, not a guarantee that Claude will select the skill for every request about a pull request.

What’s actually slowing this PC down?

Pick the symptom - the matching free tool is one click away.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

How do you make a Claude Code skill load automatically?

Automatic selection depends on whether Claude considers the current request a match for the skill’s description. A precise description makes the intended use clearer, but it cannot ensure activation for every phrasing or session. You can always request the skill explicitly with its slash command.

To test the example, ask for a concise summary of the current diff or a draft PR description. Then enter /pr-summary to test explicit invocation. Check that the response follows the three-bullet instruction and does not claim tests passed without results.

What if the skill does not activate as expected?

  • It does not appear to be available: Check that SKILL.md is spelled and placed correctly at <skill-name>/SKILL.md, under a supported location.
  • The slash command works, but a matching request does not select it: Refine the description to name the actual tasks and wording you expect to use, then repeat both the matching-request test and direct invocation. This is a troubleshooting step based on the documented role of the description, not a guaranteed fix.
  • Teammates cannot use a personal skill: A file under ~/.claude/skills/ is personal to that machine. Put a shared version in the repository’s .claude/skills/ directory and commit it.
  • Your setup uses a different deployment or configuration: Check Anthropic’s current guide for nested, added-directory, plugin, enterprise, and synced-skill behavior; those configurations may use options beyond this basic setup.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Do you need a paid plan to use Claude Code?

Anthropic’s Claude Code setup guide lists Anthropic Console, Claude App Pro or Max plans, and enterprise platforms as access options. The right route depends on your account and deployment; the setup information does not establish that every user needs a particular paid subscription.

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.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Leave a Reply

Your email address will not be published. Required fields are marked *

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

More from the Wire

  1. World desk4 min
    How to Spot an AI Voice Scam Before Sending MoneyDon’t rely on how a caller sounds. Pause, call back through a known number, and verify the emergency with another trusted person before sending money.
  2. Mountain View desk4 min
    Google’s SynthID Detector: How to Check AI-Generated Images, Video and AudioGoogle’s SynthID Detector looks for an embedded watermark in supported images, video and audio. Here is what its results do—and do not—show.
  3. Redmond desk20 min
    How to create a link to File or Folder in Windows 11Windows 11 gives you several ways to point to a file or folder without moving or duplicating it. You can create a desktop shortcut,…
Recommended PC Tool
Recommended PC Tool
Outdated Drivers Are Slowing You DownFree scan - exact matches
PC Slower Than It Used to Be?Free scan - under a minute

Two free Windows tools

One Free Minute Could Fix That PC

Before you go - each of these free tools takes about a minute and tackles what quietly slows a Windows PC down.

Special offer. View Outbyte info, uninstall instructions, EULA, and Privacy Policy.