Pro Tips

Turn Any Guide
Into a Claude Skill

See the Download as PDF button at the bottom of my free guides? Here is how to hand that PDF to Claude and have Claude build it into a skill you can run on command, anytime.

The Problem

You read a great guide. You think, “I am going to use this.” You save it. And then it sits there. A month later you cannot even find it, let alone follow the steps.

Saving good tips is not the same as using them. The win is when the steps run themselves. That is exactly what a skill does. You teach Claude the workflow once, and from then on you just ask for it.

Good news: every free guide on this site now has a Download as PDF button at the bottom. That PDF is all you need to build your first skill.

First, the basics What a Skill Actually Is

A skill is small and simple. It is a little folder with one main file inside called SKILL.md.

That file has two parts. At the top is a short header with a name and a description. Below that are the step-by-step instructions. A skill can also include a few extra helper files when it needs them.

Here is the part that makes it feel like magic: Claude reads the description, and when your request matches it, Claude loads the instructions and runs the workflow. You do not have to paste the steps again. You just ask.

One honest note up front. You do not drop a PDF and watch it turn into a skill on its own. The real flow is that you hand Claude the PDF and ask Claude to write the skill from it. Claude reads the guide and authors the SKILL.md for you. That is what the steps below walk you through.

Step By Step How to Build It

The whole thing takes about 5 minutes. You need a guide PDF and Claude open. That is it.

Step 01

Download the guide as a PDF

Scroll to the bottom of any free guide on this site and click the Download as PDF button. Save the file somewhere you can find it. This PDF is the source material Claude will learn from.

Step 02

Open Claude

Open Claude in your browser, the desktop app, or Claude Code. Any of them works. Start a fresh chat so the skill build has a clean space.

Step 03

Give Claude the PDF and the prompt below

Attach the guide PDF to the chat. Then paste the prompt from the next section. It tells Claude exactly what to do: read the guide and write a skill from it, with a clear name, a clear description, and numbered instructions. Claude will ask you a few questions first if it needs them. Answer those and let it write the SKILL.md.

Step 04

Save the skill where it lives

Claude gives you the skill back. Now you save it in the right place so Claude can find it later.

In Claude Code: skills are just folders on your computer. Put your skill folder in ~/.claude/skills/ to use it everywhere, or in .claude/skills/ inside a project to use it only there. No upload needed.

On claude.ai (web or desktop): on a paid plan with code execution turned on, zip your skill folder and upload it as a custom skill under Settings → Capabilities.

Step 05

Run it on command

You are done building. From now on you just ask. When your request matches the skill’s description, Claude loads the instructions and runs the workflow for you. The guide you almost forgot is now a button you can press anytime.

Copy & Paste The Prompt

Attach your guide PDF, then paste this in. It tells Claude everything it needs to author a clean, reusable skill.

Prompt: Turn This Guide Into a Skill
I have attached a PDF guide. I want you to turn it into a reusable skill that I can trigger on command later. Here is what I want you to do: 1. Read the whole guide first. Understand the workflow it teaches and the result it is meant to produce. 2. Write a SKILL.md file with two parts: - A short header at the top with a clear name and a clear description. The name should be simple and lowercase with hyphens. The description should say, in one or two plain sentences, what the skill does and when I would want to use it, so it gets matched to the right requests later. - Below the header, numbered step-by-step instructions that walk through the workflow from the guide so it runs the same way every time. 3. Keep the name clean. Do not put the words "claude" or "anthropic" anywhere in the skill name. 4. Add any helper files only if the skill truly needs them (like a checklist or a template). Keep it simple. If one file is enough, use one file. 5. Before you write anything, ask me anything you need to know first so the skill fits how I actually work. For example: what I want the end result to look like, anything specific to my situation, or any choices the guide leaves open. Ask your questions one at a time. Once I answer, write the full SKILL.md, show it to me, and tell me in plain words where to save it and how I will trigger it later.

Good To Know

A few honest notes so you go in clear. Skills do not sync across surfaces on their own. A skill you build on claude.ai is not automatically in Claude Code, and the other way around. If you want it in both places, save it in both. Also, uploading custom skills on claude.ai needs a paid plan with code execution turned on. And remember the name rule: no “claude” or “anthropic” in the skill name.

The Real Win Why This Changes Things

Every guide you love can become a skill you actually use. Instead of a folder full of PDFs you saved and forgot, you build a small library of workflows that run on command.

Start with one. Pick the guide you keep meaning to come back to, download it, and turn it into a skill today. Then do it again with the next one.

The Only AI Masterclass You Need

Build AI Systems That Run Your Work, Business, And Life

If this guide helped, but you’re looking to go deeper, I got you!! My 30-Day Challenge takes you from saving AI tips you never use to actually building with AI, step-by-step.

I show you exactly how I automated two e-commerce brands, my social media, and most of my personal life, then hand you the agents, workflows & systems to do the same. I’m teaching you every single thing I know with one lesson and one build a day.

Join the AI Masterclass →

© 2026 Mariah Brunner. All rights reserved.