Skills Ecosystem — Superpowers on Demand
Skills are pre-built, invokable capabilities that extend Claude far beyond file editing. One command and Claude can generate a full PowerPoint deck, a formatted PDF report, an Excel spreadsheet, or a Word document — without you touching those apps at all.
🧩 What Are Skills?
In regular Claude Code sessions you write prompts and Claude edits files. Skills are different — they are specialized expert modules you call by name. Each skill knows how to produce a specific type of output that would normally require a dedicated app.
- Ask Claude to write slides → get raw text
- Open PowerPoint and format manually
- Ask Claude for a report → get markdown
- Open Word, paste, format manually
- 30–60 minutes per document
- One prompt → a real
.pptxfile on your disk - One prompt → a formatted
.pdfready to share - One prompt → an
.xlsxwith formulas and charts - One prompt → a styled
.docxWord document - 2–3 minutes end to end
Skills vs. regular prompts — what's different
- Skills produce binary files — real
.pptx,.pdf,.xlsx,.docxfiles, not text - Skills have built-in domain knowledge — the PPTX skill knows slide layouts; the PDF skill knows document structure
- Skills are invoked by name — you call them explicitly, like switching to a specialist
- Skills can read your existing files — turn a markdown file or data dump into a polished document
⚡ How to Invoke a Skill
Invoking a skill is a one-line instruction. You name the skill and describe what you want. That's it.
Basic invocation pattern
# Pattern: skill name first, then the brief Use the [skill-name] skill to [describe the output]. # Real examples Use the pptx skill to create a 6-slide pitch deck for my SaaS app. Use the pdf skill to generate a one-page project summary from CLAUDE.md. Use the xlsx skill to build a monthly budget tracker with income, expenses, and a summary chart.
Feeding a skill your own content
Skills don't just generate from scratch — they can transform content you already have. Reference existing files the same way you do in regular prompts.
# Turn a text file into a polished document Use the pptx skill. Read @meeting-notes.md and turn the key points into a 5-slide summary deck. Professional style, dark theme. # Turn structured data into a spreadsheet Use the xlsx skill. Read @sales-data.csv and create an Excel report with a pivot-style summary table and a bar chart by month. # Turn a rough draft into a formatted Word doc Use the docx skill. Read @draft-proposal.md and format it as a professional Word document with a cover page and table of contents.
.md (markdown) file first — fast and easy to edit. Then use a skill to transform it into the polished final format. Edit the markdown, regenerate the output. No manual reformatting ever.
📦 Skills Catalog — The Core Set
These are the skills you'll reach for most often. Each one covers an entire category of output that would otherwise require a dedicated application.
Creates fully formatted PowerPoint files (.pptx) — slides, layouts, themes, bullet points, speaker notes. No PowerPoint needed.
Generates and reads PDF files. Create reports, proposals, and handouts — or extract text and data from existing PDFs.
Creates and edits Microsoft Word documents (.docx) — headings, tables, formatting, cover pages. Readable in Word, Google Docs, or Pages.
Creates Excel-compatible spreadsheets (.xlsx) with formulas, charts, multiple sheets, and data formatting. Opens in Excel, Numbers, or Google Sheets.
Builds and debugs apps using the Anthropic SDK — handles caching, tool use, streaming, and model selection. Preview of Module 07.
Creates new custom skills from scratch, or improves existing ones. Build your own specialized capabilities. Covered in Module 08.
🎯 Real Outputs — What Each Skill Actually Produces
Here are worked examples of prompts and the files they produce. These are real outputs you can use immediately.
PPTX — Slide deck from a brief
Use the pptx skill to create a 7-slide product pitch deck.
Slide structure:
1. Title slide — product name "FlowDesk", tagline "Stop switching apps"
2. Problem — 3 bullet points about context switching killing productivity
3. Solution — how FlowDesk solves it, one clear visual metaphor
4. How it works — 3-step process (Connect, Focus, Ship)
5. Traction — placeholder metrics (MAU, revenue, growth)
6. Team — 3 team member placeholders with role titles
7. Ask — funding round details, contact info
Style: dark background, use accent color #7c6af7 for highlights.
Professional but not corporate. Save as pitch-deck.pptx.
PDF — Report from existing content
Use the pdf skill. Read @project-notes.md and generate a formatted
PDF report called project-summary.pdf.
Include: executive summary (3 sentences), key findings as a numbered
list, next steps section, and a footer with today's date.
Clean professional layout. No images needed.
XLSX — Spreadsheet from data
Use the xlsx skill to create a project tracker spreadsheet.
Sheet 1 — Task List: columns for Task, Owner, Status (dropdown:
Todo/In Progress/Done), Due Date, Priority (High/Med/Low).
Pre-fill 5 sample rows.
Sheet 2 — Summary: formulas that count tasks by status, show
% complete, and highlight overdue items in red.
Save as project-tracker.xlsx.
🔗 Chaining Skills — One Input, Multiple Outputs
The real power comes when you chain skills together. One source document becomes a deck, a PDF summary, and a spreadsheet — all in the same session, all consistent with each other.
Example chain: project kickoff package
Write a project brief in plain text
Create brief.md — project name, goals, timeline, team, budget. Plain text, no formatting needed.
Turn the brief into a kickoff deck
"Use the pptx skill. Read @brief.md and create a 6-slide project kickoff deck for stakeholders."
Create a one-page PDF summary
"Use the pdf skill. Read @brief.md and create a one-page executive summary PDF to email before the meeting."
Build a task tracker from the timeline
"Use the xlsx skill. Read @brief.md and extract the timeline into a task tracker spreadsheet with owners and due dates."
Chaining with iteration
Skills don't have to be final — you can iterate just like regular prompts:
# First pass Use the pptx skill to create a 5-slide overview deck from @brief.md. # Review it, then refine The deck looks good but slide 3 is too text-heavy. Rebuild it with 3 bullet points max and add a simple diagram description. # Final export Regenerate the full deck with that change and save it as final-deck.pptx.
💡 Power Tips for Skills
Tip 1 — Be specific about style
Skills accept style instructions just like design prompts. The more specific you are, the less you'll need to edit afterward.
# For PPTX "Dark background (#0a0a0f), purple accent (#7c6af7), sans-serif font, minimal text per slide, lots of white space" # For PDF "Clean professional layout, section headers in dark color, body text in gray, generous margins, no decorative elements" # For XLSX "Header row dark background with white text, alternating row colors, freeze the top row, auto-filter on all columns"
Tip 2 — Tell the skill who the audience is
Audience context changes tone, density, and structure automatically.
"...for a non-technical executive audience — avoid jargon" "...for engineers — include technical specs and architecture details" "...for a VC pitch — lead with traction, market size, and the ask"
Tip 3 — Use the markdown-first workflow
- Write content in
.md— fast, easy to edit, version-controllable with git - Use a skill to render it — one prompt turns it into the polished format
- Update the
.md, regenerate — no manual reformatting - One source, multiple outputs — same
.mdcan produce a deck, a PDF, and a doc
Tip 4 — Combine skills with web pages
Skills aren't just for documents. Combine a skill output with a landing page for a complete deliverable package:
I need a complete client proposal package. From @proposal-notes.md:
1. Use the pdf skill to create proposal.pdf — the formal document
2. Use the pptx skill to create proposal-slides.pptx — the walkthrough deck
3. Create a proposal.html landing page that links to both files
Make all three consistent in style and messaging.
🎯 Challenge — Three Skills, One Session
Open your terminal. Create a plain text file and use three different skills to produce three different outputs from it.
- 1 Create a notes file. Ask Claude: "Create a file called notes.md with a brief outline for a 3-month content marketing plan. Include goals, channels, and monthly themes."
- 2 Use the pptx skill. "Use the pptx skill. Read @notes.md and create a 5-slide strategy presentation." Open the file in PowerPoint, Keynote, or Google Slides and verify it looks correct.
- 3 Use the pdf skill. "Use the pdf skill. Read @notes.md and create a one-page executive summary PDF." Open the PDF and check the formatting.
- 4 Run /compact, then use the xlsx skill. After compressing, run: "Use the xlsx skill. Read @notes.md and build a content calendar spreadsheet with columns for Month, Theme, Channel, and Status."
🏗 Mini Project — Build a Complete Deliverable Package
You're going to build a real deliverable set: a project brief in markdown, a slide deck, and a PDF summary — all consistent, all from one source file. Pick your OS and follow each step.
Open Terminal and run these one line at a time:
cd ~/my-deliverables
claude
When you see the ❯ prompt, Claude is running inside your new folder. Everything it creates will land here.
At the ❯ prompt, paste this and press Enter. It creates a realistic project brief — feel free to change the project name and details to something real:
Project name: LaunchPad — an AI-powered onboarding tool
Goal: Help SaaS companies reduce time-to-value for new users
Problem: 60% of users churn in the first 2 weeks due to poor onboarding
Solution: Personalized AI walkthroughs that adapt to each user's role
Timeline: 3-month MVP, launch in Q3
Team: 2 engineers, 1 designer, 1 PM
Budget: $120,000 seed funding
Ask: $500K pre-seed round to scale sales and marketing
Claude writes brief.md to disk. This is your source file — all three skill outputs will be generated from it. If you update this file later, you can regenerate everything in minutes.
This prompt tells Claude to use the pptx skill and read your brief as the source. The @brief.md means Claude reads the actual file before generating:
investor pitch deck called pitch-deck.pptx.
Slides: Title, Problem, Solution, How It Works,
Traction & Team, The Ask.
Style: dark background, purple accent color, minimal text
per slide, professional layout.
Claude will generate pitch-deck.pptx in your my-deliverables folder. The file is a real .pptx — open it in PowerPoint, Keynote, or Google Slides.
open ~/my-deliverables/pitch-deck.pptx — it opens in Keynote or PowerPoint if installed. Or find it in Finder under your home folder.Back at the ❯ prompt, use the pdf skill on the same brief:
executive summary called project-summary.pdf.
Include: a 2-sentence overview, the problem and solution
as short paragraphs, key numbers (timeline, team, budget, ask),
and contact information placeholder at the bottom.
Clean professional layout, footer with today's date.
Claude generates project-summary.pdf in the same folder. This is the document you'd email to someone before a meeting — they get context without having to sit through a deck.
brief.md became both a 6-slide deck and a formatted PDF. This is the markdown-first workflow in practice — one source, multiple outputs, zero manual formatting.Skill outputs can use a lot of context. Check where you are and compress:
If context is above 30–40%, run compact before the next skill call:
Claude confirms the compression. Your files (brief.md, pitch-deck.pptx, project-summary.pdf) are safely on disk — compressing the session history doesn't touch them.
Ask Claude to show you what's in the folder:
You should see: brief.md, pitch-deck.pptx, project-summary.pdf. Then open them all:
open ~/my-deliverables/project-summary.pdf
open ~/my-deliverables/brief.md