Skills — The Visual Guide (For Everyone)

What Are Skills?

Skills are slash-command shortcuts that expand into full workflows. One word in, a complete process out.

😵

Without Skills

You type long instructions every single time
"Check my inbox, summarize the important emails, draft replies to the urgent ones, and format everything as bullet points..."
You forget steps or miss details
Different team members handle it differently
Repetitive tasks eat your morning

⚡

With Skills

Type /morning-briefing — done
Inbox summarized, urgent items flagged, draft replies ready
Same thorough process every time
Everyone on the team gets the same quality output
30-minute routines become one-liners

Think of it this way: Skills are like speed-dial on a phone. Instead of dialing a 10-digit number every time you call your biggest client, you press one button. Instead of typing 5 paragraphs of instructions about how to prepare your morning report, you type /morning-briefing.

Simulation: Without vs With Skills

Watch the same task — "prepare a weekly client report" — play out without and with a skill.

🔴 Without Skills

🟢 With Skills

How Skills Work

Three simple steps — from one word to a complete result.

⚡

You Type a Slash Command

You type something like /morning-briefing, /weekly-report, or /client-proposal. That's it. One phrase triggers the whole thing.

📜

The Skill Expands

Behind the scenes, the slash command expands into a detailed set of instructions — like unfolding a paper airplane back into its full sheet of paper. Claude receives the complete workflow.

🤖

Claude Executes

Claude follows the expanded instructions step by step: gathering information, applying templates, formatting the output, and delivering the result. You just watch (or go get coffee).

Think of it this way: A skill is like a recipe card. You say "make lasagna" (the slash command) and the recipe card unfolds with all the steps, ingredients, and timing. You don't need to remember anything — the card has it all.

Simulation: A Skill in Action (/client-proposal)

Watch the /client-proposal skill handle a complete proposal workflow — from gathering client info to a polished, ready-to-send document.

⚡ /client-proposal Workflow

Types of Skills

Skills come from different places — some are built in, some are shared, and some you build yourself.

Type	Who Makes It	Example	Think of It As...
Built-in	Comes with Claude Code	/help, /clear	Pre-installed apps on your phone
Community Skills	Created by other users	/meeting-notes, /expense-report, /social-post	Apps from the App Store
Custom Skills	You or your team	/client-onboarding, /quarterly-review	Custom shortcuts you built yourself

Think of it this way: It's like apps on your phone. Some come pre-installed (built-in). Some you download from the App Store (community). And some your company built just for your team (custom).

What Makes a Great Skill?

The difference between a skill that saves your team hours and one that causes headaches.

✓ DO

Automate repetitive reporting and formatting tasks
Encode your team's templates and brand guidelines
Handle the boring parts (pulling data, applying styles, structuring content)
Include review steps (always show a draft before sending)
Do one job well — focused and predictable

✗ DON'T

Try to handle every possible scenario in one skill
Skip review steps to save time
Replace human judgment on sensitive decisions
Hardcode details that change between clients or projects
Forget to update the skill when your process changes

Common Pitfalls

Mistakes that make your skills cause more problems than they solve.

⚠ The Swiss Army Knife

A skill that tries to write the weekly report, email it to the client, post a summary to Slack, update the CRM, AND schedule a follow-up meeting. It breaks constantly because it's doing too much.

Fix: One skill, one job. Chain simple skills together instead of building one mega-skill.

⚠ The Blind Runner

A /send-proposal skill that emails the proposal directly to the client without letting you review it first. Fast? Yes. Dangerous? Absolutely.

Fix: Good skills include review steps. Draft before sending. Preview before publishing. Verify before acting.

⚠ The Mystery Box

Nobody on the team knows what /process actually does. Does it update the CRM? Send an email? Create an invoice? Who knows!

Fix: Name skills clearly and document what they do. /send-proposal should send a proposal. /meeting-notes should create meeting notes.

⚠ The Fossil Skill

The skill was created when BrightPath's pricing had three tiers. You switched to four tiers six months ago. The skill still uses the old pricing template and leaves out the Enterprise tier.

Fix: Update skills when your process or information changes. They're living documents — maintain them like any other team resource.

Simulation: Building a Custom Skill

Watch a team create a custom /client-onboarding skill from scratch — from idea to finished workflow.

🛠 Building /client-onboarding

Quick Reference

Everything at a glance.

⚡

Trigger

Type / + skill name.
That's it.

📜

Expands

Into full instructions.
Claude gets the whole workflow.

🔁

Consistent

Same quality every time.
No steps forgotten.

👥

Shareable

Whole team uses the same skills.
Consistent results across people.

🛡

Review Built In

Skills include checkpoints.
You approve before anything goes out.

🔧

Customizable

Build your own skills.
Tailored to your team's process.

TL;DR

Skills are slash-command shortcuts that turn one phrase into a complete workflow.

Three types: built-in (pre-installed), community (shared by others), custom (built by your team).

They expand behind the scenes into full instructions that Claude executes step by step.

Best skills are focused — one job, done well, with review steps built in.

Your team can share them — everyone gets the same process, same quality, zero guesswork.