I Built a Health Buddy Skill for Claude Code (and You Can Too) 💧🧘‍♀️

Source: Dev.to

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.

Setting Up a Claude Skill

A skill is essentially a single markdown file (SKILL.md) that lives inside a .claude/skills/ directory. Claude reads the file when it’s relevant and follows the instructions you provide.

Where Skills Live

• Global location: ~/.claude/skills/ (available across all projects)
• Project‑specific location: .claude/skills/ inside the project folder

Each skill gets its own folder, and the folder name becomes the skill name.

# Example: create a global skill called health-buddy
mkdir -p ~/.claude/skills/health-buddy

If you prefer the skill to be limited to a single project, create .claude/skills/health-buddy/ instead.

The SKILL.md File

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

Things to keep in mind

1. The name must match the folder name.
2. The description is used by Claude to decide when to load the skill, so keep it specific and clear.

Everything below the frontmatter is the skill body. It only loads when the skill is triggered, so you can be as detailed as you like without worrying about token waste.

Example: Health Buddy Skill

Below is a complete SKILL.md for a simple wellness‑check 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

Reminders

💧 Hydration Check

“Time for a water break! Your brain is 75 % water – keep it happy! 🧠💦”

🚶‍♀️ Movement Break – Pick one:

• “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!”

Response 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]

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 personalized wellness check‑in. 🎉

Or just say “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.

Extending the Idea

The skill system is powerful because it’s so simple: no code, no APIs, just one markdown file. You can teach Claude your conventions, tone, and preferences, and it will follow them every time.

Here are a few ideas for other skills:

• Generate commit messages in your team’s format
• Create components that follow your design system
• Perform code reviews against your specific standards

If you build your own skill, feel free to share it in the comments! And if you’ve been coding for more than an hour without a break—this is your sign. Go drink some water. 💧