Skills: Your Process, Automated

You know those tasks you do the same way every time?

Writing client proposals. Formatting meeting notes. Prepping a weekly report. Running through a checklist before you ship something. Drafting a certain type of email.

You have a process. Maybe it's in your head. Maybe it's in a doc somewhere. Either way, you follow roughly the same steps every time.

What if Claude could learn that process and execute it the same way you do - automatically - every time the task comes up?

That's Skills. And this is where Claude stops being a tool you use and starts becoming a system that works for you.

Skills vs Projects: the difference that matters

On Day 3, you set up a Project. Projects give Claude knowledge - the reference materials, background docs, and context it needs to understand your work.

Skills are different. Skills give Claude a process.

Think of it this way:

• Project = "Here's everything you need to know about my client." (Knowledge)
• Skill = "Here's exactly how I write a client proposal, step by step." (Process)

They work together. A project holds the client's brand guidelines. A skill encodes how you structure proposals. When you ask Claude to write a proposal in that project, it draws on both.

What a skill actually looks like

A skill is a package of instructions, steps, and sometimes scripts that Claude loads when it's relevant. You don't have to trigger it manually - Claude recognizes when a task matches a skill and applies it automatically.

Claude already has built-in skills. If you've ever asked Claude to create an Excel spreadsheet, a PowerPoint deck, a Word doc, or a PDF, you've seen skills in action. Those file creation capabilities are powered by skills running in the background.

But the real power is in custom skills. The ones you create for your specific workflows.

Creating a custom skill (it's easier than you think)

Here's the part that surprises people: you create skills by having a conversation with Claude. No coding. No configuration files. You just talk.

Here's how:

Step 1: Start a new chat and tell Claude what you want to build.

"I want to create a skill for writing weekly status reports. Every Friday I send my team a summary of what we accomplished, what's in progress, and what's blocked."

Step 2: Claude interviews you.

It'll ask things like: What sections should the report have? What tone? How long? Who's the audience? Can you show me an example of a good one?

Answer honestly. The more detail you give, the better the skill works.

Step 3: Upload examples if you have them.

Got a status report you were proud of? A template you've been using? Drop it in. Claude learns from your actual work, not abstract descriptions.

Step 4: Claude generates the skill.

It packages everything into a downloadable ZIP file. Instructions, structure, rules - all encoded.

Step 5: Upload it to your settings.

Go to Settings > Capabilities, scroll to Skills, click "Upload skill." Done.

From that point on, whenever you ask Claude to write a weekly status report, it automatically uses your skill. Your structure. Your tone. Your sections. Every time.

Skills that are worth building

Not every task needs a skill. A one-off question doesn't need a repeatable process. But anything you do more than twice a month with a consistent structure? That's a skill candidate.

Meeting notes. You probably have a format: attendees, key decisions, action items, next steps. Teach Claude your format and every set of meeting notes comes out the same way.

Client communications. The way you structure update emails, the sections in your proposals, the format of your project kickoff docs. All of these have patterns. Encode them once.

Content creation. Your blog post structure. Your newsletter format. The way you outline presentations. If you follow a repeatable approach, that's a skill.

Analysis frameworks. How you evaluate a vendor. How you assess a new market opportunity. How you review a budget proposal. The framework is the skill.

Onboarding docs. If you regularly create documentation for new hires, new clients, or new projects, the template and approach can be a skill.

The compounding effect

Here's why skills matter beyond the obvious time savings.

Every skill you create makes Claude slightly more "you." Not in a creepy way - in a practical way. Your proposals sound like your proposals. Your meeting notes follow your format. Your analysis uses your framework.

Over time, you're not just using an AI tool. You're building a system that encodes how you work. And that system gets better every time you refine a skill based on what's working.

This is the shift from "I use Claude" to "Claude runs parts of my business."

Try this today

Think about the task you do most frequently that follows a repeatable pattern. Start a new Claude conversation and say:

"I want to create a custom skill for [your task]. Can you help me build one?"

Claude will walk you through it. Upload an example of your best work if you have one. In 10 minutes, you'll have a skill that saves you time every single week.

Note: Custom skills require a Pro, Max, Team, or Enterprise plan with Code Execution enabled in your settings. Skills is currently a feature preview, which means it's available but still being refined. If you're on the free plan, this is one of the features worth upgrading for.

Projects give Claude knowledge about your work. Skills give Claude your process. Together, they turn Claude into a system that works the way you work.