How to Use Skills in Claude Code (Teach It Once, Never Again)

Be honest: how many times have you explained the same thing to your AI? “This is my format — greeting first, then WINS, then IN PROGRESS, then NEXT WEEK. Short sentences. And my sign-off goes like this.” Every. Single. Time.

Here’s the thing — by Module 3, Claude already had a brain, a memory, and hands. But knowing you is not the same as knowing your job. Memory means it remembers facts about you. It still doesn’t know your process.

That’s what we fix in Module 4 of the free Claude Code course (Taglish), using Skills.

The analogy: a VA you only had to train once

If you’ve ever trained a new VA — or been the new VA — you know that exhaustion of explaining the same process again and again. A Skill is your SOP, written down once, that Claude never forgets. Like a VA you trained one time — except this one never resigns and never forgets.

And the rule for what deserves to be a skill is simple: doing or explaining something for the third time? That’s a skill.

What’s inside Module 4

• You don’t write the skill file — Claude does. We do the task together once (a weekly client update, corrections and all), then say: “Turn what we just did into a skill called client-update.” Claude writes the SKILL.md itself. Open it and you’ll see: it’s not code — a name, a description, and instructions in plain language, like a note to a new VA.
• One command forever — from then on, /client-update plus this week’s notes gives you a client-ready update in your format, your tone, your sign-off.
• Auto-invoke — the part that feels like magic: paste new notes and just say “make an update for my client” — no slash command — and Claude picks the right skill by itself. The description line in the file is how it “smells” when to step in.
• Personal vs project skills — if you freelance for multiple clients, this is the most important 30 seconds: a skill in the client folder’s .claude/skills/ stays in that folder — Client A’s format can never leak into Client B’s work. Your own processes go in ~/.claude/skills/ and follow you everywhere.
• And the proof: close the session. Open a fresh one — zero memory of the conversation. New notes, one command — perfect output. I never taught it again.

Teach it once, own it forever

That’s the whole promise of Skills: your process stops living in your head (and in your repeated explanations) and starts living in a small file you can read, edit, and even share.

Speaking of share-able: I made a ready-made example — a Proposal Writer skill that reads a job post and drafts a proposal in plain, human-sounding English.

New to the course? Start with Module 2 (setup + memory) and Module 3 (MCP), then follow the free Beginner Roadmap checklist — now updated with the Skills steps.

Less manual work, more lakwatsa. 🌴