I needed to make a pitch deck for Freebo. I did not want to open PowerPoint. I did not want to drag boxes around in Google Slides. I wanted to type what the deck should say and have it come out looking right.
So I built a Claude Code skill that does exactly that.
What it actually does
The skill is called freebo-slides. It lives in ~/.claude/skills/ like any other Claude Code skill. When I type /freebo-slides make me a presentation about X, Claude reads the skill prompt, follows a locked-in design system, and writes a single self-contained HTML file with every slide.
No templates to pick. No theme marketplace. The brand, colors, typography, and layout rules are baked into the skill itself. Every deck comes out looking the same way: Swiss Modern with Freebo’s red and navy, Archivo headings, Nunito body text, a red accent bar on every slide, grid pattern overlay, consistent header and footer. Done.
The output is one HTML file. You open it in a browser. Arrow keys navigate. It works on a phone. It works on a TV. There is a built-in edit mode if you want to tweak copy live.
How fast is fast
This morning a client needed a deck for a new revenue strategy. I typed one sentence into the terminal describing what the presentation should cover. Eight slides came back. Title, problem, solution, business model, projections, implementation steps, closing slide. Full brand styling, animations, nav dots, progress bar. About 60 seconds from prompt to opening in my browser.
I did not write a single line of HTML. I did not choose a font. I did not align anything.
Why a skill instead of a template
Templates are starting points. You still have to do the work. A skill is a set of instructions that Claude follows every time. The difference matters.
My skill prompt includes:
- A complete design system with CSS variables, component classes, and typography scales
- Content density limits per slide type (a stat slide gets one hero number and three bullets, max)
- A phased workflow: gather content first, write a presentation-copy.md file, confirm the outline, then generate HTML
- Edit rules so I can say “change slide 4” and Claude makes a surgical string replacement instead of rewriting the whole file
The skill knows that title slides get a geometric accent in the bottom right. It knows that two-column slides should split evenly. It knows the footer says “Freebo — Confidential” and the slide counter format is “01 / 08”. I taught it these things once and now every deck is consistent without me thinking about it.
The broader point
Claude Code skills are just markdown files with instructions. There is nothing fancy about them. But the compounding effect is real. Every skill you write is a workflow you never have to think about again.
I have skills for blog posts, SEO audits, meme generation, SVG icons, and now presentations. Each one started because I got tired of doing the same thing manually. Each one took maybe 30 minutes to write. And each one saves me that time back on every single use.
If you are using Claude Code and you keep doing the same multi-step task, write a skill for it. Put the instructions in a markdown file. Be specific about what you want. Let the model do the boring parts.
You will not go back to dragging boxes around.