39 Claude Skills Examples to Transform How You Work (From 23 Creators)

Everyone's switching ChatGPT for Claude. If you're one of them, start here.

+18

Daria Cupareanu, Kamil Banc, Karo (Product with Attitude), and 19 others

Jan 25, 2026

If you’ve been on any social app lately, you’ve probably seen it: “Goodbye ChatGPT, hello Claude.”

Articles about it, notes about it, tweets about it. It’s everywhere.

And for good reason. Anthropic built for enterprise first. All the capabilities that came from that focus ended up helping everyone who uses AI for work.

At first, I used Claude mainly for writing. But since Skills came out in October 2025, it's progressively spread into everything I do. Content, research, automations, client work, design, proposals, planning, marketing.

It’s been a game changer. Many things now take half the time, the quality of what I produce improved, and it unlocked tasks I wasn't even using AI for before.

Which meant I started using Claude more. A lot more. Enough that my Pro plan limits started bothering me and I upgraded to Max.

To give you ideas and help you figure out where Skills might be useful for your work too, I decided to write about it.
And for this first post, I wanted variety beyond my own use cases.
So I launched an open invitation on Substack for creators to join me and share their skills with you.
22 creators joined. 39 Claude Skills shared.

Since this article went out, I’ve gone much deeper. I built writing skills, a brand skill, and a lead magnet skill, started using Cowork with scheduled tasks and plugins, let Claude use my computer, and built an MCP that puts all my prompts and workflows right inside your Claude. If you want to go further after this article, those are your next reads.

Switching from ChatGPT? Here’s my guide to making the move. Just getting started with Claude? This complete guide will help you make the most of it.

In this post:

Upgrade to Paid

What are Claude Skills?

Let’s say every time you write a newsletter, you paste the same instructions to Claude.

“Here’s how I write. Here’s how I structure articles. Here’s who I write for.” Every. Single. Time.

A skill is that set of instructions, packaged in a file that Claude can access.

You write it once, reuse it across sessions, and update it as you learn what works - but you never re-explain from zero.

Claude loads it automatically every time you write an article, or you can just ask it to.

And it works the same for anything else. Your coding standards. Your client proposal format. Your proofreading checklist. How you want data analyzed. How you structure emails. How you write Monday reports.

In other words, skills help you build systems for repeatable work. And once you have them, they can cut hours from how you’re doing things now.

What this unlocks:

Consistency. Same standards, same quality, every session
Speed. No more re-explaining context
Automation. Repetitive tasks become one command
Reliability. Review processes that don’t depend on you remembering

By the end of this article, I’ll walk you through how to create your own. But first, let’s see what 22 creators built with theirs.

I split the skills by work domain so you can jump to what’s relevant to you.

Some creators generously shared full skill files or detailed breakdowns. Whenever that happened, I added a link at the end so you can deep dive if something catches your attention.

Now let's get into them.

1. Skills for Writers & Content Creators

13 skills for newsletter writing, content repurposing, SEO, quality control, ideation, and video content.

Voice DNA | by Daria Cupareanu

Problem: You tell Claude “write in my voice” and get something that sounds like a polished stranger. Next session, you start over.

The skill: Analyzes your writing samples and extracts everything that makes your voice yours. Sentence rhythm, paragraph structure, what you never do. Produces a reusable Voice DNA profile Claude references every time it writes for you.

Why it works: It specifically looks for absences, not just patterns. Words you avoid, structures you skip, places where AI will try to “correct” your intentional choices. Then builds override rules to prevent that.

Grab the Voice DNA extraction prompt here.

Content Extraction | by Alex McFarland

Problem: You have existing long-form content but stare at a blank page trying to repurpose it.

The skill: Extracts content ideas from long pieces and organizes them into platform-specific tables with titles, hooks, descriptions, and key points.

Why it works: Systematic extraction means no good idea gets left behind.

Get Alex's content extraction skill here.

Newsletter Ideation | by Raghav Mehra

Problem: You know the general topic, but can’t find a fresh angle. You write the obvious take and discover three other newsletters published the same thing that week.

The skill: Generates 5-7 unique angles for any general topic using frameworks like SCAMPER, Jobs-to-be-Done, and a Contrarian Angle Generator. Each angle comes with a headline, target audience, and value proposition.

Why it works: The Contrarian Angle Generator systematically challenges consensus views and finds hidden assumptions worth questioning.

Read more about it here.

Substack Notes | by Alex McFarland

Problem: Short-form social content needs different patterns than long-form writing. What works in an article doesn’t work in a Note.

The skill: Generates high-performing Substack notes using proven structural patterns while maintaining your voice.

Why it works: Platform-specific patterns plus voice consistency. The skill knows what works for Notes specifically.

Get Alex's substack-notes skill here.

Substack TOC Generator | Kamil Banc

Problem: Creating a table of contents with working jump links on Substack is tedious and easy to mess up.

The skill: Creates numbered tables of contents with working internal anchor links. Just give it your POST_ID from the published URL.

Why it works: Handles Substack’s specific /i/POST_ID/section-slug format automatically. No more trial and error.

Get Kamil’s substack-toc skill here.

SEO Optimizer | by Wyndo

Problem: You don’t have time to learn SEO or manually optimize every post. Your traffic suffers.

The skill: Fetches your newsletter URL, searches Google for relevant keywords, creates a full SEO report (keyword density, heading structure, meta descriptions), then generates an optimized version without losing your voice.

Why it works: Paste your URL, run the skill, walk away. Wyndo’s Google traffic grew to 3.5k clicks in 28 days.

Read more about it here.

Creative QA Check | by Mariam Vossough

Problem: By the time you think you’re ready to publish, you’ve been staring at the same draft for hours. You’re blind to weak openings, voice drift, and structural gaps.

The skill: Audits your drafts for voice authenticity, structure, scanability, SEO elements, and accessibility. Returns prioritized recommendations: Critical → Important → Nice to have.

Why it works: Ego-free feedback. “This opening won’t hook anyone” - not diplomatic encouragement. It searches your project knowledge for brand positioning, then audits against it.

Get Mariam's full breakdown of her QA skill here.

Publication Proofreader | by Mariam Vossough

Problem: The technical cleanup that takes 45 minutes of second-guessing when you’re tired. Curly quotes, bullet styles, broken links, missing alt text.

The skill: Final technical polish after strategic issues are fixed. Checks language, formatting consistency, mobile optimization, visual elements, links, and generates 3-5 headline alternatives.

Why it works: Fix strategy first (Creative QA), then polish execution (Proofreader). Running them sequentially prevents fixing typos before structural problems.

Read more about it here.

LinkedIn Teaser Generator | by Joel Salinas

Problem: Writing LinkedIn posts to promote your newsletter is a separate task that requires context switching. You already wrote the article - now you have to sell it too.

The skill: Detects when you ask for LinkedIn teasers of Substack posts. Has best practices and brand voice loaded. Submit a Substack URL + “linkedin” and it generates the teaser.

Why it works: Simple trigger - URL + keyword. Brand voice is already baked in, so output is ready to post.

Voice Skills | by Rhonda Britten

Problem: Getting AI output to match your voice requires detailed documentation. And even then, Claude kept mixing up audiences no matter how much reminding happened in conversation.

The skills: Three separate skills instead of one: an overall voice skill (word choice, sentence structure, what sounds like her), a public audience skill (for general readers), and a coaches audience skill (for industry peers). Each handles its own context.

Why it works: The more you chunk things out, the better Claude does. One giant voice skill trying to handle everything produces generic output. Separate skills for separate purposes means Claude never confuses who you’re writing for.

Hero Image Prompt Generator | by Dheeraj Sharma

Problem: Maintaining consistent branded hero images across all articles without manual design work. Every article needs a visual, and they should all feel like they belong together.

The skill: Generates brand-consistent hero image prompts for articles featuring “The AI Monk” character. Automatically selects visual themes (like ‘Learning Moment’ with teaching pose for tutorials) and brand backgrounds.

Why it works: Central place for brand guidelines. Tweaks and improvements stay consistent. Article theme automatically flavors the visual output.

The Self-Interview | by Nick Quick

Problem: The bottleneck isn’t “I need AI to write something”. It’s “I need to figure out what I actually think about this.” Circling the same thoughts for days, needing someone to ask the question you haven’t thought to ask yourself.

The skill: Flips the typical AI interaction. Instead of you prompting and AI producing, the skill asks you progressively deeper questions about your project, decision, or half-formed idea. AI plays journalist, therapist, or strategist.

Why it works: When you’re prompting, you stay in your existing frame. When you’re being prompted, you get pushed outside it.

YouTube Toolkit | by Jean-Paul Paoli

Problem: Downloading and transcribing YouTube content means juggling multiple tools and writing custom scripts.

The skill: Downloads YouTube videos, audio, and transcripts with one request. Handles quality selection, format conversion, subtitle extraction. Prefers manual subtitles over auto-generated, falls back to transcription if needed.

Why it works: Discuss what you want to do with the video in Claude Code. The skill handles finding best quality, sanitizing filenames, extracting subtitles.

2. Skills for Marketers & Business Owners

9 skills for lead magnets, email funnels, social promotion, positioning, and analytics.

Brand Design System | by Daria Cupareanu

Problem: You either design documents manually in tools like Canva or PowerPoint, or you keep fixing formatting every time Claude generates a new PDF or presentation.

The skill: Turns your visual brand into a reusable skill that Claude uses whenever it generates a Word document, PDF, or presentation, automatically applying your logo, colors, fonts, spacing, and layout rules.

Why it works: Your brand rules live in one place and get reused automatically instead of being reapplied manually.

Grab my prompt to build your own custom Brand Skill.

Slides Presentation Builder | by Kamil Banc

Problem: You know the content, but turning it into clean, professional slides takes too long and pulls you into design work.

The skill: Generates a complete, animated HTML presentation from a simple prompt. No PowerPoint. No templates to tweak.

Why it works: Design rules are built in. You focus on the message, and the output is ready to present.

Get Kamil’s presentation builder skill here.

Pre-Sale Article/Lead Magnet | by Rhonda Britten

Problem: Generic lead magnets don’t connect to specific offerings. You’re using the same PDF for every class.

The skill: Creates unique lead magnets for each class - PDFs or articles designed to drive pre-sale interest for that specific offering.

Why it works: Each class gets a tailored asset rather than one-size-fits-all content. The lead magnet actually relates to what you’re selling.

Post Live Class Email | by Rhonda Britten

Problem: Post-class follow-up is a specific conversion moment with its own psychology - urgency, social proof from the live session, addressing objections that came up. Generic email templates miss all of that.

The skill: Focuses on conversion emails sent after teaching a live class. Built for that specific moment when people are still warm.

Why it works: Timing and context are built into the skill. It knows what just happened and how to convert that energy.

Email Conversion Tester | by Rhonda Britten

Problem: Emails go out with weak CTAs or unclear value propositions because you’re too close to see them.

The skill: Tests emails for conversion optimization before sending - the final quality gate in the email workflow.

Why it works: External review catches what familiarity blinds you to. It’s the fresh eyes you need before hitting send.

Social Media Amplification | by Rhonda Britten

Problem: Social only works after your sales page and emails are tightened. Doing it first wastes effort - you’re amplifying something that doesn’t convert yet.

The skill: Creates social content to promote classes and content. Positioned as the last step in the workflow, not the first.

Why it works: Rhonda realized social amplification comes after other assets are tested. This skill is built for that sequence.

Business Profile | by Daria Cupareanu

Problem: Every time you write a CTA, about page, sales copy, or consulting proposal, you’re re-explaining what your business does, who it serves, and what makes it different.

The skill: A central reference for your business positioning. Claude pulls from it when creating CTAs, about pages, sales copy, positioning statements, consulting proposals, or bios.

Why it works: Write it once, and every piece of content accurately represents your business without you having to re-explain the basics.

Read more about it here.

Ideal Customer Profiles | by Daria Cupareanu

Problem: Marketing content falls flat because it’s written for a vague “target audience” instead of real people with specific problems, triggers, and language patterns.

The skill: Deep customer persona profiles with their problems, triggers, language patterns, decision journey questions, and information needs. Claude uses them when writing marketing content, sales copy, landing pages, email sequences, or offers.

Why it works: Content resonates when it speaks to specific people. The skill holds four detailed personas so Claude never writes generic copy again.

Read more about it here.

Analytics Tracking | by Daria Cupareanu

Problem: Setting up tracking properly takes time - GA4, conversion tracking, event tracking, UTM parameters, tag manager. Easy to miss something or set it up wrong.

The skill: Helps set up, improve, or audit analytics tracking and measurement. Covers GA4, conversion tracking, event tracking, UTM parameters, and tag manager implementation.

Why it works: A checklist and guide for getting tracking right the first time, so you’re not fixing gaps months later.

3. Skills for Developers & Technical Teams

6 skills for code quality, testing, debugging, and engineering standards.

Frontend Design | by Jeff Morhous

Problem: AI-generated frontends look the same - purple gradients on white, Inter font, cookie-cutter layouts. Generic “AI slop” aesthetics.

The skill: Creates distinctive, production-grade frontend interfaces. Commits to bold aesthetic directions - brutally minimal, maximalist, retro-futuristic. Focuses on typography (distinctive fonts, not Arial/Inter), color, motion, and spatial composition.

Why it works: Forces a conceptual direction before coding. “What makes this UNFORGETTABLE?” Match complexity to vision.

Get Jeff’s raw skill file here or read his writeup on installing and using it.

Automated UI Test | by Jenny Ouyang

Problem: Testing web apps meant opening browsers, copying credentials from password managers, clicking the same flows repeatedly. Every code change cost 15-20 minutes of manual testing.

The skill: Uses Playwright MCP to run end-to-end browser tests. Reads test credentials from .env, navigates the app, clicks through flows, reports pass/fail with screenshots on errors.

Why it works: Skills live in the repo (.claude/skills/), committed with code. New environments get them on clone. Type /automated-ui-test and it works.

MCP Execution Debugger | by Jenny Ouyang

Problem: Reading hundreds of lines of MCP tool logs when something broke. 20-minute debugging sessions guessing which business rule misguided a query.

The skill: When running a query through a custom MCP server, executes the request normally then generates a structured report showing every tool call in the chain, where it failed, and what to fix on the backend.

Why it works: Turned debugging into 2-minute reads. One skill, one job - it surfaces problems clearly but doesn’t try to fix them.

Verify-Work | by Ilia Karelin

Problem: The “wrap up and ship” moment is when you’re most likely to miss things - unused imports, console.logs, edge cases not handled. Because you’re mentally done.

The skill: Runs an end-of-session review that checks coding practices, security, and feature completeness. Flags incomplete work, broken tests, and bugs before you close the session.

Why it works: It’s a pre-flight checklist that triggers automatically when you say something like “now that we’re done, verify the work we did.”

Engineering Standards | by Jinx

Problem: Without centralized standards, generated code doesn’t match your team’s style. Known LLM weaknesses in engineering keep appearing.

The skill: Team-wide engineering standards converted into a skill - coding style, security considerations, scalability patterns, and debugging approaches (full code path trace instead of symptom fixing).

Why it works: Applied to all Claude Code projects automatically. Include broad triggers so it activates on all common contexts.

Project-Specific Context | by Jinx

Problem: Rebuilding context through handoff files or repeated explanations is exhausting. If you’re rebuilding the same context frequently, it belongs in a skill.

The skill: Contains architecture details, module information, goals, and repo link for a specific project. Claude can answer detailed questions and check current commits for potential conflicts.

Why it works: Decide if context should be global (applies everywhere) or project-based (specific codebase only). Either way, the re-explaining stops.

4. Skills for Business Operations

8 skills for inventory, presentations, business cases, document formatting, systems, knowledge capture, and meeting analysis.

Business Case Builder | by Zain Haseeb

Problem: Business cases get rejected because they’re not rigorous enough. Or they never get written because people don’t know where to start.

The skill: 6-step workflow to build investment cases. Frame the decision, quantify costs/benefits, compare alternatives, calculate metrics (ROI, payback, NPV), assess risks, build recommendation. Outputs executive-ready templates: quick (1-page), standard (2-3 page), comprehensive (5+ page).

Why it works: Forces you to quantify with ranges (conservative/expected/optimistic), which is more credible. Always includes “do nothing” option and explains why alternatives were rejected. That’s what skeptical finance teams look for.

Get Zain's business case builder skill here.

Presentation Builder | by Raghav Mehra

Problem: First hour spent staring at blank slides, unsure how to structure content. Then overloading slides with 8 bullets and burying key messages.

The skill: Transforms ideas, outlines, or documents into structured slide content. Adapts to presentation type - pitch decks, business reviews, technical workshops each get different templates. Generates titles (5-10 words stating the takeaway), 3-5 bullets per slide, visual placeholders.

Why it works: Structure templates are the unlock. Say “pitch deck” and it knows: Problem → Solution → Market → Traction → Team → Ask. Explicit rule: “if you have 8 bullets, you have 2 slides.”

Read more about it here.

Inventory Analyst | by Alex Willen

Problem: Managing inventory across 9 e-commerce brands. Deterministic projection rules fell apart at edge cases. Back to spreadsheets.

The skill: When typing /inventory (optionally with brand name), checks inventory and sales data (pulls from Amazon if >5 days old), reads brand-specific context, uses historical trends and velocity to project monthly sales for 12 months, determines stock-out dates, and recommends when to place next order - factoring in manufacturing time, shipping, and buffers like Chinese New Year.

Why it works: Claude as inventory analyst holds context in non-structured ways that rigid apps couldn’t. Key: be very granular in instructions. Tell it to write out month-by-month sales, or it’ll just project from last 30 days (which breaks for seasonal brands).

Word Document Styling | by Ed Rodgers

Problem: Every exported document needed manual font and style updates before sharing.

The skill: Adjusts all .docx output to follow a custom Word normal.dotm template - specific fonts, colors, heading styles (H1, H2, H3).

Why it works: Post-editing is now just proofreading. Formatting is automatic and uniform.

Live Class System | by Rhonda Britten

Problem: Forgetting elements of class setup when you’re juggling multiple classes per month. Did you send the reminder? Set up the room? Prep the materials?

The skill: A checklist and system for class preparation - helps remember everything needed for each class.

Why it works: Operational memory. The skill doesn’t forget what you might.

Brand/Contractor Onboarding | by Patrick Schaber

Problem: When you change contractors, you start from ground zero on brand onboarding every time. Explaining your voice, tone, visual guidelines - again and again.

The skill: Packages brand language, tone, and visual guidelines into a skill that can be shared with subcontractors or partners working on your website or content.

Why it works: Anything you want to be consistent could have a skill. Share it with new partners and they’re immediately aligned.

Blue Fish | by mark

Problem: Learning moments happen constantly when working with AI, but they get lost across tools, conversations, and time.

The skill: Automatically extracts learning moments from conversations and organizes them into a Notion database. Captures eureka moments, decisions, breakthroughs, and frameworks with a shortened title, 3 bullets, and context.

Why it works: Three skill components work together: a scan that reads conversation history, a capture sub-skill (what qualifies as significant), and a category sub-skill (how to classify). Say “PIN” to mark something, “APPROVE” or “SKIP” when reviewing.

Meeting Analyzer | by Daria Cupareanu

Problem: You sit through meetings but walk away without clear action points - and no idea what you missed.

The skill: Analyzes meeting transcripts to extract action items, decisions made, and moments where you missed opportunities to listen or respond.

Why it works: Turns every meeting into a clear list of what to do next - and what to do better next time.

5. Skills for Career & Personal Development

2 skills for job search and career transition.

Job Description Analyzer | by Jose Antonio Morales

Problem: Reading lengthy, jargon-filled job descriptions wastes time when applying to multiple positions daily. It’s overwhelming to evaluate fit for each one.

The skill: Reads job descriptions, compares against your resume/skills/preferences, provides a compatibility score and recommendation on whether to apply.

Why it works: Trained on your profile. Provides objective, consistent evaluations so you can focus effort on promising opportunities instead of application fatigue.

Micro-Experiments | by Dee McCrorey

Problem: When you’re between jobs, every small action feels like it should lead somewhere. A coffee chat inflates into “does this mean I should commit to a marketing career?”

The skill: Helps design and debrief small, low-stakes experiments during career transition - without requiring commitment, clarity, or a grand plan. Asks “What are you curious about?” not “What’s your goal?” Validates “I hated it” and “I’m more confused now” as useful outcomes.

Why it works: Catches inflation signals: “This will show me if I should...” → “No, it shows you one data point.” Holds the frame when your anxiety wants certainty. The skill needs to be more restrictive than you think.

The skill that helps you build other skills

The Skill Builder | by Karo (Product with Attitude)

Problem: YAML formatting errors cause skills to fail. You upload something, it doesn’t work, and you have no idea why. Wrong indentation, properties in the wrong place, missing fields.

The skill: A meta-skill that produces properly formatted SKILL.md files with correct YAML frontmatter. You describe what you want your new skill to do, and it generates the file with correct structure. Includes templates, common errors to avoid, and a validation checklist.

Why it works: It catches things like putting author or version outside of metadata (they need to be inside), fields that don’t belong at the top level, indentation issues - the stuff that breaks skills without telling you what went wrong.

Get the Skill Builder skill here.

How to create your own skills in Claude

For this guide, I’ll focus on how you can create skills in the Claude desktop app.

If you've never created skills before, go to Settings → Capabilities first.
Enable the skill-creator skill under Skills, and turn on "Cloud code execution and file creation". Claude needs this to create the skill files for you.

There are three ways to add new skills:

1. Create with Claude

Best for: complex skills that need a lot of context.

How to use: You open a chat conversation and tell Claude you want to create a skill together. I’d recommend sitting long in the conversation to reach a solid final version. That’s how my best skills were built.

For example, my ideal-customer-profiles skill came from a very long conversation where Claude interviewed me. I fed it a lot of information about my ideal customers, even attached feedback and testimonials, reasons why people reached out to me - for it to analyze and identify their core problems, triggers, language patterns, decision journey questions, and information needs.

Once done: You have two options. Either download the markdown file (SKILL.md) and import it manually from Settings → Capabilities → Skills → Add → Upload a skill. Or, if Claude shows you a “Copy to skills” button when it finishes, just click it and the skill gets imported automatically.

2. Write skill instructions

Best for: Simpler skills you can describe in a few sentences.

How to use: Go to Settings → Capabilities → Skills → Add, then select “Write skill instructions”. Fill in three fields: skill name, description, and instructions.

Tip: This is also how you can use skills shared by others - if a creator shared their instructions earlier in this article, you can just copy them here.

3. Upload a skill

Best for: When you already have a skill file ready.

How to use: Go to Settings → Capabilities → Skills → Add → Upload a skill, then drag and drop the file.

Works with: Skill files from other people in the correct format or skills you created in conversation with Claude and downloaded.

Know someone who just switched to Claude? Send them this.

And if you're not sure whether something should be a skill, a project, or a Cowork thing, I wrote a decision framework that helps you pick the right Claude tool for your need.

Now it’s your turn

Whether you’re switching to Claude or just curious about what it can do, Skills is worth exploring.

Just imagine how much less you’ll need to repeat yourself and how fast you’ll be able to work after creating some of these for processes you do every day.

That’s how it went for me and the creators in this post. A complete game changer.

So now it’s your turn.

Go build your own - and if any of these skills inspired you, follow the creators and give them a shoutout in the comments.