Claude Skills: Stop Starting from Scratch with Every New Chat

If you've been using Claude for any length of time, you've probably experienced this: you open a new chat, and immediately you're re-explaining yourself or pasting in your tried and true prompt. Your role, your preferences, the way you like things formatted, the context behind the project you're working on. And here's the part most people don't think about: every time you paste that wall of context, Claude has to re-read it with every single message you send. It's inefficient, it burns through your tokens, and it's the AI equivalent of briefing the same person five times on the same project.

I get it. I use Claude constantly for content, work projects, planning, and drafting. And for a while I just accepted the "re-onboarding" tax as part of the deal. Copy and paste your context. Re-establish your preferences. Start from scratch, again.

That all changed when I discovered Claude Skills.

So, What Exactly Is a Skill?

Here's the non-technical version: a Skill is a set of instructions you write once that Claude automatically loads whenever it's relevant. Think of it like a saved playbook. Instead of re-explaining your preferences, your workflow, your style guide, and your context every single session, Claude already knows. It's loaded and ready to go.

Think of it this way: Claude has access to a professional kitchen, with all the ingredients, equipment, and tools. Skills are the recipes, the step-by-step instructions that tell Claude exactly how to use all of it. The difference between having a kitchen and actually knowing how to cook.

How I Actually Use Skills

Let me give you a concrete example from my day-to-day as a program manager. Whether I'm building out a project timeline, summarizing a meeting transcript, or drafting a stakeholder email, I was constantly re-explaining the same things. My communication style, the project context, how I like timelines structured, the tone I use with different audiences. Every. Single. Time.

With a skill, I defined that context once. Now Claude already knows how I like to communicate, what level of detail matters to me in a summary, and how to format a timeline so it actually matches the way my team works. I open a chat, drop in a transcript, and say "summarize this" and it comes back in exactly the format and voice I need. No setup required.

How to Call a Skill in a Chat

This is the part that surprised me. It's way easier than I expected.

Most of the time, you don't have to do anything special. Claude is smart enough to recognize when a task matches a skill you've set up and loads it automatically. You ask for a blog post, the blog-writing skill kicks in. You ask for a spreadsheet, the spreadsheet skill does its thing. It just works.

If for some reason Claude doesn't pick it up on its own (especially the first time you're testing something new), you can just tell it directly: "Use my /[skill name] to do this." After that first nudge, it tends to trigger automatically going forward.

Think of it like training a new team member. The first time you ask them to do something, you might need to point them to the right process. After that? They've got it.

How to Add or Update Your Skills

Skills live in your Claude settings under Settings > Capabilities > Skills. You can upload a skill as a simple folder (zipped up), and once it's in there, Claude starts using it.

Here's the part I find genuinely empowering: you write the skills. There's no app to buy, no configuration to code, no developer required. You're essentially writing a short instruction document, similar to a good creative brief or a process doc, and Claude follows it every time.

Updating a skill is just as simple. If your brand voice evolves, if you add a new project, if your preferences shift: open the skill file, update it, and re-upload. Done.

For people like me who live in a world of process documentation and stakeholder communication, this clicked immediately. It's project management logic applied to AI. Define the process once, run it consistently, update when things change.

Three Categories Where Skills Really Shine

Based on how I've seen them used (and how I use them myself), skills tend to fall into three buckets:

Content and document creation. Any time you're producing consistent output (blog posts, reports, brand copy, presentations), skills embed your style guides and quality standards so you don't have to re-paste them every time.

Repeatable workflows. Got a multi-step process you run regularly? A research pipeline, an onboarding checklist, a content review process? A skill can walk Claude through every step, in the right order, every time.

App and tool integrations. If you've connected Claude to outside tools like Google Drive, Gmail, or a project management system, skills layer on top to tell Claude how to work with those tools in a way that matches your actual workflow, not just a generic version of it.

A Trick That Made Skill Building So Much Easier

Okay, this is the one I wish someone had told me sooner.

If you've had a long, productive chat with Claude where you've already done a ton of back-and-forth, given feedback, corrected it, and gotten it dialed in exactly how you like, you don't have to start from scratch to build a skill out of it. Just say: "From the learnings and context you've had through this chat, create me a skill."

That's it. Claude will look back through the entire conversation, pull out everything it learned about your preferences, your style, your workflow, and draft a skill document for you on the spot. You review it, make any tweaks, and upload it.

It's honestly a great way to start. Instead of staring at a blank document trying to articulate your preferences from memory, you let the conversation do the work.

The Honest Reality Check

Skills aren't magic. They're only as good as the instructions you write. If you're vague ("help me with content"), the skill will be vague. The more specific you are about what you want and when to use it, the more reliably Claude will pick it up and run with it.

The first time I built one, I spent more time than I expected just figuring out how to describe what I wanted clearly enough for Claude to know when to use it. Once I got that down, everything else fell into place. Same principles you'd apply to any good process doc: be specific, give it clear steps, and tell it exactly what a good output looks like.

If you've ever written a solid SOP or a detailed project brief, you already know how to do this.

Why This Matters

Claude is only as useful as how well it understands how you work. Skills help to close that gap.

Once they're set up, you stop spending the first five minutes of every chat getting Claude up to speed. You just get to work. For anyone using Claude regularly for professional tasks, that adds up fast.

I wish someone had pointed me to Skills sooner. Once it clicked, it changed how I use Claude entirely. If you're already a heavy user, this is the thing that makes it actually feel like your tool.

xx Kristi