We talk a lot about AI making us more productive. But honestly? The more I use Claude Code, the more I forget to drink water. So I did what any developer would do β I automated the reminder. π
This post is a beginner-friendly intro to Claude Code skills and how to build your own. No prior experience needed. Just a text editor and a folder.
π€ What is a skill, exactly?
Think of a skill like a recipe card you hand to a chef. The chef (Claude) already knows how to cook β but they don't know your preferences, your workflow, or your conventions. A skill teaches them exactly that.
At its simplest, a skill is just one file: a SKILL.md with a name, a description, and some instructions. That's it.
Claude reads it when it's relevant and follows your instructions from there.
π The folder structure
Skills live inside a .claude/skills/ folder, either in your project or globally in ~/.claude/skills/ (available across all your projects).
Each skill gets its own folder, and the folder name becomes the skill name:
~/.claude/skills/
βββ health-buddy/
βββ SKILL.md
π οΈ Building the skill step by step
Step 1: Create the folder
mkdir -p ~/.claude/skills/health-buddy
If you want the skill only inside one project, use .claude/skills/health-buddy/ instead.
Step 2: Create the SKILL.md file
Inside that folder, create a file called SKILL.md β capital letters matter, that's how Claude finds it.
Step 3: Add the frontmatter
Every skill starts with YAML frontmatter between --- markers:
---
name: health-buddy
description: >
Your friendly wellness check-in skill. Trigger with /health-buddy, or invoke
automatically when the user says things like "I'm going insane", "I want to
break something", "I can't do this anymore", "this is driving me crazy",
"I need a break", or any sign of frustration or burnout. Give them a wellness
nudge instead of debugging advice.
---
Two things to keep in mind here:
- The name must match the folder name
- The description is always in context β Claude uses it to decide when to load the skill, so keep it specific and clear
Step 4: Write the instructions
Everything below the frontmatter is the skill body. This only loads when the skill is triggered β so you can be as detailed as you like without worrying about token waste.
Here's the full health-buddy skill:
---
name: health-buddy
description: >
Your friendly wellness check-in skill. Trigger with /health-buddy, or invoke
automatically when the user says things like "I'm going insane", "I want to
break something", "I can't do this anymore", "this is driving me crazy",
"I need a break", or any sign of frustration or burnout. Give them a wellness
nudge instead of debugging advice.
---
# Health Buddy π§πΆββοΈ
Hey there! I'm your Health Buddy. I help you remember to take care of yourself while you're coding or working.
## What I Do
When you type `/health-buddy`, I'll:
1. Remind you to take a break if you've been working a while
2. Suggest drinking some water
3. Give you a quick stretch or movement idea
4. Encourage you with a positive message!
## My Reminders
### π§ Hydration Check
"Time for a water break! Your brain is 75% water - keep it happy! π§ π¦"
### πΆββοΈ Movement Break
Pick one of these fun activities:
- "Stand up and do 10 jumping jacks! Get that blood flowing! π―"
- "Walk around your room or office for 2 minutes. Your legs will thank you! π"
- "Do 5 desk push-ups! You got this! πͺ"
- "Shake it out! Arms, legs, head - wiggle everything for 30 seconds! πΊ"
### π§ Stretch Suggestions
- "Roll your shoulders back 10 times - release that tension! π"
- "Look up at the ceiling, down at the floor, left, right. Give those eyes a break! π"
- "Stretch your arms above your head and reach for the sky! π"
- "Twist your torso left and right 5 times. Gentle spinal twists feel great! π"
### π Eye Care
"Follow the 20-20-20 rule: Every 20 minutes, look at something 20 feet away for 20 seconds!"
## How I Respond
I'll give you:
1. A friendly health tip
2. A quick activity suggestion (takes 30 seconds to 2 minutes)
3. A motivational message
4. Optional: A fun fact about health and productivity
**Format:**
π Health Check Time! π
π§ [Hydration or movement reminder]
π― Quick Action: [Specific thing to do right now]
πͺ You got this! [Encouraging message]
π§ Fun Fact: [Optional interesting tidbit]
βΆοΈ Testing it
Start a new Claude Code session from the same directory (skills are discovered at session start) and type:
/health-buddy
Claude will load the skill and respond with a personalised wellness check-in. π
Or just type "I'm going insane" mid-session and watch Claude send you on a water break instead of debugging with you. π That's the magic of the description field β Claude reads it and decides when the skill is relevant, no slash command needed.
π‘ Why this matters
The skill system is powerful because it's so simple. No code. No APIs. No configuration files beyond one markdown file. You can teach Claude your conventions, your tone, your preferences β and it will follow them every time.
The health-buddy skill is a fun example, but imagine applying this to things like:
- A skill that generates commit messages in your team's format
- A skill that creates components following your design system
- A skill that does code review against your specific standards
Same idea. One file. Huge impact.
π Your turn
If you build your own skill, I'd love to see it in the comments! What would you teach Claude to do for you?
And if you've been coding for more than an hour without a break β this is your sign. Go drink some water. π§

Top comments (0)