PaddySpeaks · AI for Everyone · Part 1 of 2

What Are Claude Skills?

No jargon. No assumptions. A plain-language guide with actual files opened up and explained, so you can see exactly what's happening when Claude creates things for you.

March 2026·14 min read·paddyspeaks.com

Have you ever asked Claude to "create a PowerPoint presentation" or "read this PDF" — and it actually gave you a real downloadable file? That wasn't Claude improvising. Behind the scenes, it opened a set of specialized instructions, followed a procedure, and used real software tools to build that file.

Those instructions are called Skills. And you've been using them without knowing it.

This two-part guide explains everything — in plain language, with zero technical prerequisites. Part 1 (this article) covers what Skills are, shows you the actual files inside them, and explains how they work. Part 2 walks through real-life scenarios step by step.

I
The Big Idea

Think of Claude as a Restaurant

The Analogy That Makes It Click

Imagine Claude is a very talented chef. Without Skills, this chef can cook — but they're improvising every dish from memory. Sometimes brilliant. Sometimes inconsistent.

Skills are the recipe books, the specialized tools, and the prep instructions. When you order a specific dish (ask Claude to make a spreadsheet), the kitchen doesn't wing it — it pulls out the exact recipe, grabs the right pans, and follows a proven procedure.

The menu at the front? That's the Skill descriptions — short, one-line summaries. Claude glances at every menu item to figure out which recipe matches your order. The recipe book only gets opened after you order. And the ingredients (specialized code, templates) only get grabbed when the chef is ready to cook.

That's the whole idea. Skills give Claude specialized knowledge for specific tasks. When your request matches a Skill, Claude uses it. When it doesn't, Claude just talks to you normally — which is still very good, but it's the difference between "here are some ideas for slides" and "here's your actual PowerPoint file."

II
Open the Box

What's Actually Inside a Skill?

This is where most explanations get abstract. Not this one. Let's open up a real Skill and look at every file. Below is an interactive file explorer showing the actual contents of Claude's Word Document Skill — the Skill that activates when you ask Claude to create a .docx file.

Click any file in the sidebar to see what's inside and why it matters:

skills / docx /
📄 SKILL.md
🏷 ↳ frontmatter (top)
📖 ↳ body (instructions)
📁 scripts/
🔧 validate.py
🔧 unpack.py
🔧 pack.py
📁 templates/
📜 LICENSE.txt

That's a real Skill. It's just a folder with text files and code scripts. The SKILL.md is the brain — the instructions Claude follows. The scripts are the hands — the tools Claude runs to build actual files. The templates help with advanced operations like tracked changes.

The Three Layers — Every Skill Works This Way

No matter which Skill you look at — PDFs, spreadsheets, presentations — they all follow the same pattern:

Layer 1 — The Menu Item (Always Visible)

The name and description at the top of SKILL.md. Claude reads these for every installed Skill at the start of every conversation. This is how it knows what's available. Takes up very little memory — like a one-line menu entry.

Layer 2 — The Recipe (Loaded When Needed)

The full instructions in SKILL.md. Only loaded when Claude decides your request matches. This tells Claude how to approach the task — what libraries to use, what formatting standards to follow, what common mistakes to avoid.

Layer 3 — The Ingredients (Grabbed On Demand)

The scripts, templates, and reference files in subfolders. Only loaded when the instructions specifically call for them. These are the actual tools Claude runs — Python scripts that validate files, JavaScript code that builds documents, templates for complex formatting.

This is why Skills don't slow Claude down. Most of the time, Claude only carries Layer 1 (the menu). It only loads the heavier layers when you actually need them.

III
More Examples

Peeking Inside Other Skills

Let's look at how different Skills are organized. Each one is tailored to its job — some are simple, some are complex, but they all follow the same folder-with-SKILL.md pattern.

The PDF Skill — Two Skills Working Together

PDFs are complex enough that Anthropic split the work into two Skills: one for reading PDFs and one for creating/editing them. Here's what each contains:

skills / pdf/ & pdf-reading/
📋 pdf-reading/SKILL.md
📋 pdf/SKILL.md
📚 pdf/REFERENCE.md
📝 pdf/FORMS.md
📁 pdf/scripts/

The File Reading Skill — The Traffic Cop

This is the most interesting Skill to understand, because it solves a problem most people don't think about: not all files can be opened the same way. If Claude tried to read a PDF the way it reads a text file, it would get garbled nonsense. The File Reading Skill is a routing table — it looks at the file type and tells Claude which tool to use:

skills / file-reading /
🚦 Dispatch Table
Why It Exists

The Internal Comms Skill — A Different Shape

Not all Skills create files. The Internal Comms Skill is a writing guide — it teaches Claude how to write company-style updates, newsletters, and FAQs. Instead of scripts, it has example documents that show Claude the expected format:

skills / internal-comms /
📄 SKILL.md
📝 examples/3p-updates.md
📰 examples/newsletter.md
examples/faq-answers.md

See the pattern? Every Skill is a folder. Every folder has a SKILL.md. But what's inside varies wildly — scripts for file creation, reference docs for complex tasks, example formats for writing. The Skill is whatever Claude needs to do the job well.

IV
In Action

What Happens When You Ask — Step by Step

Now that you've seen what's inside a Skill, let's watch it work. Click each step to expand:

You Type

"Create a 10-slide pitch deck for my bakery. Include slides for our story, menu highlights, financials, and next steps."

1
👀
Claude reads every Skill's menu entry
Scans the name + description of each installed Skill

Claude sees "pitch deck" + "slides" and matches it to the pptx Skill, whose description says: "Trigger whenever the user mentions deck, slides, presentation, or a .pptx filename." This takes a fraction of a second.

2
📖
Claude opens the full SKILL.md
Loads the presentation-building instructions into working memory

Now Claude knows: use PptxGenJS library, follow the layout guide in pptxgenjs.md, validate the file after creation, use thumbnail.py to check the visual output. All from the SKILL.md file we explored above.

3
🔧
Claude runs code in a private workspace
Executes JavaScript to build an actual .pptx file with real slides

Claude has access to a private computer (a virtual machine). It writes and runs real code — not a simulation. The output is a genuine PowerPoint file that opens in any presentation software.

4
📦
You get a downloadable file
A .pptx file appears in your conversation — preview or download it

You can preview it right in Claude, download it, open it in PowerPoint or Google Slides, add your own photos, and present it tomorrow. It's a real file you own.

V
Translations

Jargon Buster — Terms You'll See Online

Now that you understand what Skills are, here's a quick reference for the technical terms you'll encounter if you read more about them:

SKILL.md
The instruction file in every Skill folder. Written in Markdown (a simple text formatting language). Has a "name" and "description" at the top (the menu entry), and detailed instructions below (the recipe).
Like a recipe card — title at the top, steps below.
Frontmatter
The name and description section at the very top of SKILL.md, between two lines of dashes (---). This is what Claude reads to decide if the Skill matches your request.
The dish name and one-line description on a restaurant menu.
Triggering
When your request matches a Skill's description and Claude activates it. Happens automatically — you never need to say "use the PDF Skill."
Saying "I'll have the pasta" and the kitchen knowing which recipe to use.
MCP (Model Context Protocol)
A standard way for Claude to connect to outside apps — Google Drive, Slack, Salesforce. Think of it as a universal adapter. Instead of building a custom cable for every app, there's one plug standard that works with all of them.
A universal power adapter. One standard, plugs into anything.
Connector
A specific connection to a specific app, built using the MCP standard. "The Google Drive Connector" = Claude can read and write your Google Drive files.
The specific plug you bought for the Italian outlet. One adapter standard, many plugs.
Progressive Disclosure
Claude doesn't load all Skill instructions at once. It reads only the menu (Layer 1) first, then opens the recipe (Layer 2) if needed, then grabs ingredients (Layer 3) when it's time to cook. This keeps Claude fast.
A kitchen that doesn't prep every dish at opening. Cook what's ordered.
Context Window
Claude's working memory — the total amount of information it can hold at one time. Skills are designed to use as little of this as possible, so there's room for your actual conversation and files.
A desk. Skills are thin folders, not encyclopedias, so they don't crowd it.
VI
Try It

Which Skill Am I Using?

Pick a task. We'll tell you which Skill activates and what files inside it do the work:

Interactive
What would you ask Claude to do?

VII
The Takeaway

One Tip That Changes Everything

What most people type

"Give me some ideas for a presentation about my bakery"

Result: Text in chat. No file. No Skill activated.

What to type instead

"Create a 10-slide PowerPoint presentation about my bakery"

Result: Downloadable .pptx file. Presentation Skill activated.

The difference is asking for a file instead of text. When you say "PowerPoint," "Word document," "spreadsheet," "PDF" — those words trigger Skills. When you just ask for ideas or text, Claude stays in conversation mode.

Both are useful. But knowing the difference lets you choose which one you want.

You Don't Need to Be Technical

Everything in this article — the SKILL.md files, the scripts, the progressive disclosure — is what's happening behind the scenes. You don't need to understand any of it to benefit. Skills activate automatically. Just ask Claude for what you need. But if you ever wonder "how did Claude do that?" — now you know.

Part 2

Skills in Action — Real-Life Walkthroughs

A teacher making worksheets. A lawyer reading contracts. A bakery owner building a pitch deck. A freelancer designing a portfolio site. Four real scenarios with step-by-step breakdowns showing exactly which Skill files activate and what they produce.