Skills
Build Your Own Skills
Ship your own slash commands as plain markdown files.
Ship your own slash commands as plain markdown files.
What it is
A skill in Claude Code is a plain markdown file that Claude runs as a slash command. Write it once, reuse it forever. Perfect for turning repetitive prompts into one-keystroke commands instead of retyping everything each time.
Install / Setup
Skills live here:
- Global (available everywhere):
~/.claude/commands/my-skill.md→/my-skill - Project-specific:
.claude/commands/skill.mdinside the project folder - Namespaces:
~/.claude/commands/git/commit.md→/git:commit
Option 1 — Terminal (manual):
mkdir -p ~/.claude/commands
nano ~/.claude/commands/my-skill.md
Option 2 — Prompt Claude Code:
Build me a skill called "my-skill" that [DESCRIPTION]. Write the markdown file directly to ~/.claude/commands/my-skill.md, follow Claude Code skill conventions, and show me how to invoke it at the end.
Claude already knows the skill format and writes the file correctly — you just describe what it should do.
Anatomy of a skill file
Markdown with clear instructions:
# My Skill
You're an expert on [topic].
Liking this?
Inside the community I show you how I run all of this day-to-day — live sessions, direct feedback on your setup, and my full configs.
What you do
- Step 1
- Step 2
Rules
- Answer in English
- No fluff, straight to the point
- Ask when something's unclear
## Use cases
- **Git commit** — Parse `git diff`, generate a conventional commit message.
- **Project setup** — Folder structure, dependencies, CLAUDE.md, first git commit for a new API service.
- **Bug-report triage** — Paste a user report in, Claude breaks it into repro steps, expected behavior, severity.
- **Content repurposing** — Blog post in, Twitter thread + LinkedIn post + newsletter out.
- **Code review** — Fixed review prompt with every check you care about (bugs, security, performance, readability).
## Pro tip
Changes to skill files load instantly — no restart needed. Work iteratively: write the skill, run the command, see the output, tighten the rules. Two or three passes and it's reliable. If it keeps making the same mistake → add explicit "do NOT do this" rules.
---
> 🚀 **Installing skills is step one. Knowing which ones to use when is what separates operators from tourists.**
Inside the community I show you my full skill stack and how I use it every day.
[**→ Join the Claude Code Mastery Community**](https://www.skool.com/claude-code-crash-course-5725?utm_source=notion&utm_medium=library&utm_campaign=skills-cta)
Updated regularly — follow @vine.codes for more.
Want more?