19 Claude skills for creators.

---
name: creator-analytics-review
description: Analyze content performance from pasted or exported stats and say what to post more of. Use when the user shares Instagram/TikTok insights, a CSV export or screenshots of stats.
---

# Analytics Review

## Steps
1. Take the data (CSV, pasted table or screenshot). List what's there: posts, views, reach, likes, comments, saves, shares, follows.
2. Calculate per post: engagement rate (interactions ÷ views), follows per 1,000 views, saves + shares per 1,000 views.
3. Find patterns: which topics, hooks, lengths and posting times win. Compare top 20% vs bottom 20%.
4. Report:
   - 3 things that work (with the numbers)
   - 3 things to stop
   - 5 next post ideas based on the winners

## Rules
- Show your math. Don't claim a pattern from fewer than 3 posts.
- If a metric is missing, say so instead of estimating.

---
name: creator-app-teardown
description: Break down any app or website into its features, flows and screens, and write a build plan to recreate a simple version with Claude Code. Use when the user wants to clone, rebuild or understand how an app works.
---

# App Teardown

## Steps
1. Ask for the app name or URL and what part the user wants to rebuild.
2. If you can browse, open it and note what you see. Otherwise work from public knowledge and say so.
3. Output:
   - **Core job**: what the app does in one sentence.
   - **Screens**: list each screen with its main elements.
   - **Flows**: the 3 key user journeys, step by step.
   - **Data**: what gets stored (simple tables).
   - **MVP plan**: the smallest version that does the core job, as numbered build steps for Claude Code, with suggested stack.
4. Offer to start step 1.

## Rules
- Rebuild the idea and features, never copy the brand name, logo, text or assets.
- Flag anything that needs paid APIs or logins.

---
name: creator-best-of
description: Solve a task several different ways, critique each, and return the strongest answer. Use when the user isn't happy with an answer, or says 'best of', 'compete', 'arena' or 'give me the best version'.
---

# Best Of

## Steps
1. Restate the task and define 3–4 judging criteria with the user (or pick sensible ones and say so).
2. Produce 5 genuinely different attempts, each from a different angle (e.g. simplest, boldest, most data-driven, most contrarian, most practical). If sub-agents are available, run them in parallel; otherwise write them one by one.
3. Critique every attempt against the criteria, honestly, with a score.
4. Combine the strongest parts into one final answer.
5. Show: the final answer, then a 3-line summary of why it beats the runner-up.

## Rules
- Attempts must actually differ, not be rewordings.
- Keep it focused: use this for important tasks, it costs more usage.

---
name: creator-carousel
description: Turn an idea into a slide-by-slide Instagram or LinkedIn carousel with a cover that earns the swipe. Use when the user wants a carousel, slides or a document post.
---

# Carousel Builder

## Steps
1. Ask for the idea, platform (Instagram or LinkedIn) and audience.
2. Write 8–10 slides:
   - Slide 1 (cover): hook under 8 words + a subline that promises the payoff.
   - Slides 2–8: one idea per slide, max 25 words, a bold first line.
   - Second-last slide: the summary.
   - Last slide: one CTA (save, comment a keyword, follow).
3. For each slide add a one-line visual note (icon, screenshot, chart).
4. If the user has a code or file tool, offer to build the slides as 1080×1350 images or a PDF.

## Rules
- Every slide must earn the next swipe. Cut anything that doesn't.

---
name: creator-comment-replies
description: Draft replies to Instagram/TikTok comments and DMs in the creator's voice, and spot buyers. Use when the user pastes comments or DMs and wants replies.
---

# Comment Replies

## Steps
1. Read the pasted comments or DMs.
2. Sort each into: question · compliment · objection · buying signal · spam.
3. Draft a reply for each (not spam): short, warm, in the creator's voice. Answer questions fully. For buying signals, answer and offer the next step (link, keyword, DM).
4. List buying signals at the top so the creator answers those first.

## Rules
- Never promise results or discounts the creator hasn't given you.
- Max 2 sentences per comment reply. DMs can be longer.
- If you don't know the answer, write [CHECK] instead of guessing.

---
name: creator-content-week
description: Plan a full week of content across Instagram, TikTok and LinkedIn from one niche. Use when the user wants a content calendar, posting plan or ideas for the week.
---

# Content Week

## Steps
1. Ask for niche, audience, platforms and how many posts a day (default: 1 reel a day + 3 LinkedIn posts a week).
2. Build a 7-day table: day · platform · format · hook · one-line angle · comment keyword.
3. Mix formats: tips, myth vs truth, tool demo, story, results, opinion, "how I do X".
4. No two days use the same hook type.
5. Write the full script for day 1 in the 5-part reel structure.

## Output
The table first, then day 1's script, then a one-line batch plan ("record/approve days 1–3 on Monday").

---
name: creator-geo-check
description: Check whether a page is likely to be cited by AI search (ChatGPT, Perplexity, Google AI Overviews) and rewrite it to be quotable. Use when the user asks about GEO, AEO or AI search visibility.
---

# GEO Check

## Steps
1. Ask for the URL and the questions people would ask an AI that this page should answer. Fetch the page if you can; otherwise ask for its text.
2. Check: does it answer each question directly in the first 2 sentences of a section? Clear headings phrased as questions? Specific facts and numbers with sources? Author and date? Structured data (FAQ, HowTo)? A short summary at the top?
3. Report a score per item and the top 5 fixes.
4. Rewrite the intro and one key section so they're easy for an AI to quote.

## Rules
- Be clear you can't see real AI-search rankings; this is a best-practice check.

---
name: creator-hook-lab
description: Generate and rank scroll-stopping hooks for a topic. Use when the user wants hooks, openers, titles or first lines for a reel or post.
---

# Hook Lab

## Steps
1. Ask for the topic and niche if not given.
2. Write 15 hooks across 5 angles (3 each): bold claim · "this just changed" · a number · a mistake people make · "nobody talks about this".
3. Max 8 words each. Name something the audience already knows (an app, a brand, their job).
4. Score each 1–10 on: curiosity, clarity, specificity. Show the top 5 with total score and one line on why.

## Rules
- No clickbait the video can't pay off.
- No question hooks unless the answer is surprising.

---
name: creator-humanizer
description: Rewrite AI-sounding text so it reads like a real person wrote it. Use when the user asks to humanize, de-AI, or make a draft sound natural before posting.
---

# Humanizer

## Steps
1. Read the draft. List the AI tells you find: em dashes, "delve", "unlock", "in today's fast-paced world", "it's not X, it's Y" patterns, triple adjectives, every line the same length, generic openings and closings.
2. Rewrite in the author's voice. If they shared past posts, match their words and sentence length.
3. Keep every fact, number and the CTA exactly.
4. Show the rewrite, then a short list of what you changed.

## Rules
- Vary sentence length. Use contractions. Prefer concrete words.
- No em dashes. No buzzwords. Don't add claims the author didn't make.
- This makes writing sound natural; it doesn't hide authorship. If a platform requires AI disclosure, keep it.

---
name: creator-ig-profile
description: Audit and rewrite an Instagram profile so visitors follow and click the link. Use when the user wants a bio, profile, highlights or link-in-bio review.
---

# Instagram Profile Audit

## Steps
1. Ask for: handle or a screenshot of the profile, niche, who it's for, and the one action they want visitors to take.
2. Score 1–10 with one line each: name field (searchable keyword?), bio (who it's for + what they get + proof), link, highlights, top 3 pinned posts, profile photo.
3. Rewrite:
   - 3 bio options, max 150 characters, each with a clear next step.
   - Name field with a search keyword.
   - Highlight names and covers (max 5).
   - Which 3 posts to pin and why.

## Rules
- Plain words, no emoji walls. Max 2 emojis in a bio.
- Never invent proof. If there's no number to show, leave [PROOF].

---
name: creator-lead-finder
description: Find companies that likely need the user's service and draft a personal opener for each. Use when the user wants leads, prospects or clients.
---

# Lead Finder

## Steps
1. Ask for: what the user sells, ideal client (industry, size, region) and a buying signal (e.g. hiring for a role the service replaces, a new launch, bad reviews).
2. Using web search, browsing or connected data tools, find 15 companies with that signal. If you have no web access, explain how the user can export a list and paste it.
3. For each: company, link to the signal, why they fit, the likely decision-maker's role, and a one-line personal opener.
4. Rank by fit.

## Rules
- Every company needs a source link you actually found. No invented companies, people or emails.
- Respect privacy and anti-spam rules; don't collect personal contact details that aren't publicly listed for business use.

---
name: creator-linkedin-post
description: Turn an idea, reel script or article into a LinkedIn post that reads like a person, not a brand. Use when the user wants a LinkedIn post or to repurpose content for LinkedIn.
---

# LinkedIn Post

## Steps
1. Take the source (idea, script, link text). Find the one insight worth a post.
2. Write it:
   - Line 1: a hook under 12 words.
   - Line 2: blank.
   - 6–10 short lines, one idea per line, with one concrete example or number.
   - A takeaway line.
   - A question that invites comments.
3. Give 3 alternative first lines.

## Rules
- First person, plain words. No "I'm thrilled to announce", no hashtag walls (max 3), no emojis as bullets.
- Under 1,300 characters.

---
name: creator-prompt-sharpener
description: Turn a rough one-line request into a precise prompt so Claude gets it right the first time. Use when the user types /sharpen, asks to improve a prompt, or wants to save usage.
---

# Prompt Sharpener

## Steps
1. Read the rough request.
2. Ask at most 3 short questions only if something essential is missing (goal, audience, format).
3. Return a sharpened prompt with:
   - **Goal**: what done looks like
   - **Context**: who it's for, what exists already
   - **Scope**: what Claude may and may not change
   - **Output**: format and length
   - **Check-in**: when to stop and ask
4. Then list the 3 biggest things the rough version was missing.

## Rules
- Keep the sharpened prompt under 150 words.
- Don't do the task itself unless the user says go.

---
name: creator-reel-script
description: Write a 30–45 second Instagram reel script in the 5-part viral structure (hook, clarify, proof, twist, comment CTA). Use when the user asks for a reel, short, TikTok or video script.
---

# Reel Script

You write short-form video scripts that sound spoken, not written.

## Inputs
Ask once for anything missing: topic, niche, audience, comment keyword and what they get for commenting.

## Structure (always)
1. **Hook**: a bold claim about something the audience already knows. Max 8 words.
2. **Clarify**: one plain sentence explaining the claim.
3. **Proof**: 2–3 specific details with real numbers.
4. **Twist**: an "even crazier" moment that keeps people to the end.
5. **CTA**: "Comment [KEYWORD] and I'll send you [thing]."

## Rules
- 30–45 seconds read aloud (about 90–120 words).
- Short sentences. No jargon, no emojis, no hashtags.
- Never invent numbers. If you don't have a real figure, ask or leave [NUMBER].

## Output
1. Five hook options, best first.
2. The full script using hook #1, one line per sentence.
3. A 20% shorter version.

---
name: creator-review-miner
description: Read user reviews of an app or product and find the features people want and the problems they hate. Use when the user wants product ideas, to improve on a competitor, or to find gaps in a market.
---

# Review Miner

## Steps
1. Ask for the product and where its reviews are (App Store, Play Store, G2, Trustpilot, Reddit). Browse them if you can; otherwise ask the user to paste 30–100 reviews.
2. Tag each review: praise, bug, missing feature, pricing, support, UX.
3. Report:
   - Top 5 complaints with how often they appear and one real quote each
   - Top 5 requested features
   - What people love (keep this in any rebuild)
4. Turn the top 3 problems into features for a better version, with a one-line build note each.

## Rules
- Quote reviews exactly; never invent one.
- Show counts so the user can see what's a pattern and what's one person.

---
name: creator-seo-check
description: Run a quick SEO check on a web page using Claude's web tools instead of paid SEO software. Use when the user asks for an SEO audit, keyword ideas or why a page doesn't rank.
---

# SEO Check

## Steps
1. Ask for the page URL and the main keyword it should rank for.
2. Fetch the page (web fetch / browser tool if available). If you can't fetch it, ask the user to paste the page text.
3. Check and report:
   - Title tag and meta description (length, keyword, click appeal)
   - H1 and heading structure
   - Does the content answer the search intent for the keyword?
   - Missing subtopics competitors would cover (search the keyword if web search is available)
   - Internal links, image alt text, page speed red flags you can see
4. Give a prioritized fix list: top 5 changes, each with the exact new text where possible.
5. Suggest 10 related keywords grouped by intent.

## Rules
- Say clearly which checks you could run and which you couldn't (no live ranking or traffic data).
- Never invent search volumes.

---
name: creator-virality-scan
description: Break down why top videos in a niche worked and turn the patterns into original ideas. Use when the user asks what's going viral, wants to study competitors, or needs proven content ideas.
---

# Virality Scan

## Steps
1. Ask for the niche and platform. If web search or browsing is available, find 10 top-performing recent videos; otherwise ask the user to paste titles, hooks or links with view counts.
2. For each: hook, format, length, topic, why it worked (one line).
3. Group into 3–5 winning patterns.
4. Turn the top 3 patterns into original ideas for the user's audience, with hook and outline.

## Rules
- Learn the pattern, never copy the script, footage or wording.
- Say clearly which numbers came from real data and which you couldn't check.

---
name: creator-yt-package
description: Create YouTube title and thumbnail ideas and pick the strongest before recording. Use when the user wants titles, thumbnails or packaging for a video.
---

# YouTube Packaging

## Steps
1. Ask for the video topic, audience and 2–3 competing videos if they have them.
2. Write 10 titles (max 60 characters) across angles: result, mistake, curiosity, comparison, timeframe.
3. Pair the best 5 with a thumbnail concept: main visual, max 4 words of text, emotion, colour contrast.
4. Score each pair 1–10 on curiosity, clarity and "would I click this on my phone". Recommend one.
5. Write the first 15 seconds of the video so it pays off the title immediately.

## Rules
- The title and thumbnail must make one promise together, not repeat each other.
- No clickbait the video doesn't deliver.

---
name: creator-yt-script
description: Write a YouTube video script with a strong opening, clear sections and retention hooks. Use when the user wants a long-form YouTube script or outline.
---

# YouTube Script

## Steps
1. Ask for topic, target length, audience and the title they'll use.
2. Outline: hook (0:00–0:30), promise, 3–6 sections, payoff, CTA.
3. Write the script:
   - Open by restating the title's promise in the first sentence.
   - End every section with a reason to keep watching ("but the third one is where it gets interesting").
   - Mark B-roll and on-screen text in [brackets].
4. Add chapter timestamps and a 2-line description.

## Rules
- Spoken language. Read-aloud pace about 150 words a minute.
- Never invent stats; use [NUMBER] where you need one.