Skills for Claude
Skills for the Claude app and Claude Code. Download one, upload it and run its command. Free, no account.
Every Claude skill in one zip
Verified. Download everything.
How to install on Claude
- Download the zip.
- In Claude: Settings → Capabilities → turn on Skills.
- Then Customize → Skills → Add → Upload skill.
- Type its command in any chat, like
/grill-me.
Using Claude Code? Unzip the folder into ~/.claude/skills/ instead.
- 01
Be A Damn Human
/be-a-damn-humanStop acting like a polite assistant. Gate the work, ask the hard questions, name what is weak or fake, then answer like a person with judgment. Use when the brief is vague, the stakes are real, the draft sounds like a model, the user wants pushback, or they say be human, be honest, don't fluff, grill me, ask first, have a spine, give a damn, or be-a-damn-human. Do not use for simple lookups, formatting, translations, or tasks where the user already gave a tight brief and just wants execution.
- 02
Client Brief
/client-briefBuild a pre-meeting brief on a prospect before a call. Use this skill whenever the user invokes /client-brief, or asks to "prep me for my call with [company/person]", "what do I need to know before this meeting", "build a brief on [prospect]", "research this client before we talk", or anything about getting ready for a sales or pitch conversation. Pull from connected tools (CRM, Notion, email, calendar), web research on the company and person, and anything the user pastes. Always run the anti-AI writing rules on the prose.
- 03
Decide
/decideBreak a stuck decision into options, criteria that reflect the user's actual priorities, and a clear recommendation with reasoning. Use whenever the user types /decide, says they are stuck, torn, going back and forth, can't choose, or "have been putting this off", or lays out two or more options and asks which to pick — career moves, pricing, tools, hires, projects, offers. Also use when a user keeps re-litigating the same choice across a conversation.
- 04
Deck Builder
/deck-builderBuild presentation decks end to end — outline first, then generate in Gamma. FIRES whenever I mention a deck, slides, a presentation, a talk, a workshop, a keynote, a "slide deck", a webinar, or anything slide-related — e.g. "make me a deck", "build slides for", "I'm giving a talk on", "turn this into a presentation", "outline a workshop on", "pitch deck for". Lean toward firing when slides are even implied. DO NOT fire on: [LIST CONTENT TYPES TO EXCLUDE — e.g. LinkedIn posts, newsletters, blog drafts, one-pagers, ad copy].
- 05
Deep Research Synthesizer
/deep-research-synthesizerSynthesizes insights from large datasets and source material, filters irrelevant data, identifies patterns, evaluates source quality, and produces actionable, well-cited summaries. Use when handed raw research, a pile of sources, or search results and asked to make sense of them.
- 06
Devils Advocate
/devils-advocateStress-test a draft, argument, plan, or idea by attacking it with the strongest realistic counterarguments before the real audience does. Use whenever the user types /devils-advocate, asks "what's wrong with this", "poke holes in this", "would this survive criticism", wants pushback on a post, pitch, strategy, or opinion piece, or is about to publish something opinionated and asks for feedback. Also use when the user seems to want validation on a one-sided argument — the skill exists precisely for that moment.
- 07
Fact Checker
/fact-checkerExtract and verify every factual claim in a draft before it gets published, using web search against primary sources, and return a claim-by-claim verdict report plus a corrected version. Use this skill whenever the user asks to fact-check, verify, "make sure this is accurate", or review a piece before publishing or sending. ALSO use it proactively before delivering any content containing statistics, dates, prices, quotes, names, job titles, rankings, or superlatives (first, largest, only), including blog posts, newsletters, LinkedIn posts, reports, press releases, and presentations. Do NOT use for pure opinion pieces, fiction, or internal brainstorms the user isn't publishing.
- 08
Go Deeper
/go-deeperPush past the obvious first answer on any topic, take, or draft by drilling three "why" layers down until a non-obvious insight appears. Use whenever the user types /go-deeper, says a take feels shallow, generic, or "something everyone already says", asks for a more original angle or a contrarian view, or shares an idea/draft and asks "what am I missing" or "make this more interesting". Also use when the user's own analysis stops at the first explanation.
- 09
Grill Me
/grill-meInterview the user with 10-15 targeted questions BEFORE building anything, then confirm a short spec, then build. Use this skill whenever the user asks Claude to build, create, make, code, design, draft, or generate anything non-trivial — an app, website, script, tool, document, presentation, campaign, plan, or system — even if the request looks detailed enough to start immediately. Especially trigger on vague one-line build requests like "make me a dashboard" or "build an app for my gym". Do NOT use for pure questions, explanations, debugging existing code, tiny edits, or reformatting.
- 10
Handoff
/handoffCompress the entire current conversation into a clean, structured handoff document that lets a new chat session, a colleague, or future-you resume the work without losing decisions, constraints, or progress. Use this skill whenever the user says "handoff", asks to summarize the thread to continue elsewhere, mentions hitting context limits or the chat getting too long, wants to brief a teammate on this conversation, or asks to export or save where things stand. ALSO offer it proactively when a long working thread is clearly winding down or the user says they'll "pick this up later". Do NOT use for summarizing external documents or meetings; this skill summarizes the conversation itself.
- 11
How To
/how-toTurn any 'I want to do X with Claude but I don't know how' into a finished result the user built with their own hands. Use this whenever someone names a goal they want to reach with Claude or AI and wants to be walked there until it is actually done. That covers building a Cowork workflow, automating a repetitive task, setting up a content or newsletter system, writing better prompts, connecting a tool, organizing files, or any 'how do I get Claude to' request. Trigger on phrases like 'how do I', 'I want to do this with Claude', 'give me the exact steps', 'walk me through', 'teach me to', 'I don't know how to', 'get me to the result', or the command /how-to. The skill maps the full step list first, then coaches one rookie-level step at a time and will not move on until the current step is finished and understood. Built for non-technical beginners.
- 12
Humanizer
/humanizerRewrite, audit, or draft text so it reads like a human wrote it. Kills em dashes, robotic tone, AI-giveaway words, negative-parallelism reframes, forced analogies, and formulaic structure. Use this skill whenever the user invokes /humanizer or /delete-ai-words, asks to humanize text, "delete the AI words", "de-AI this", "make this sound less like AI", "audit this against the writing rules", "fix the AI writing", removes the "ChatGPT voice", or complains that a draft sounds robotic, stiff, or generated. Also trigger when the user says "audit your text" (target = your own most recent draft), and use it proactively whenever drafting content that will be read as the user's own words: emails, LinkedIn posts, blog articles, essays, bios, cover letters, newsletters, website copy, and social posts. Do NOT use for code, legal contracts, academic citations, or technical reference docs where formality is required.
- 13
I Have Adhd
/i-have-adhdShapes responses for an ADHD reader. Use whenever writing a reply to this person, for any topic. Detects task mode (action requested: fix, build, run, debug, write, set up) vs talk mode (question, venting, thinking out loud) and applies the right structure — leading with the next action, numbered steps, concrete time estimates, visible progress, no filler openers/closers — for task mode, or a plain warm conversational reply for talk mode.
- 14
Infographic Builder
/infographic-builderTurns textual content into a single, polished infographic image (1080×1350 px PNG) suitable for social feeds, reports, and educational sharing. Use whenever the user wants an "infographic," a "visual summary," a "carousel slide," a "poster," or asks to make text "shareable" / "visual" as an image they can post or download. Triggers on phrases like "make this an infographic," "turn this into a graphic," "visualize this for LinkedIn/Instagram," "one-pager I can post." Do NOT use for editable slide decks (use pptx), data dashboards, or inline chat diagrams.
- 15
Linkedin Hook
/linkedin-hookGenerate LinkedIn post hooks — the critical first 2 lines that determine whether anyone reads your post. Use this skill whenever the user wants to write a LinkedIn hook, draft the opening lines of a LinkedIn post, or shares an image/design and asks for a hook or post opening. Also trigger when the user shares a carousel image, newsletter visual, or any LinkedIn content design and mentions 'hook', 'opening', 'first line', or wants help with the start of a post. Even casual requests like 'write me a hook for this' or 'what should the first lines be' should trigger this skill.
- 16
Linkedin Post Report
/linkedin-post-reportTurn an Apify "LinkedIn profile posts" export (CSV or XLSX) into a decision-ready analytics report plus a reusable SOP for the next post. Use this skill whenever someone uploads a LinkedIn posts scrape and wants to know what's actually working — which formats, hooks, angles, and visuals drive engagement — and what to double down on or drop. Trigger on phrases like "analyze my LinkedIn posts", "what's working on my LinkedIn", "I scraped my posts", "Apify export", "LinkedIn content report", or when an XLSX/CSV with columns like engagement/likes, postImages, document/title, or linkedinUrl is attached. Built to handle the quirks of the Apify export format, which has misleading columns. Produces two files: a written report and a step-by-step SOP.
- 17
Negotiation
/negotiationBuild multi-expert negotiation strategy playbooks for [ YOUR DEAL TYPE — e.g. consulting deals, agency contracts, SaaS enterprise sales, freelance projects ]. Use this skill whenever [ YOUR NAME ] mentions negotiation, deal prep, pricing strategy, a specific client or company being pitched, scope discussions, contract terms, or preparing for a sales call. Also trigger on things like "I have a call with [company]", "how should I price this", "they want to negotiate", "prep me for this deal", or anything about closing, anchoring, objections, concessions, or walking away. Even casual mentions like "this [ BUYER ROLE ] wants a discount" or "they're pushing back on price" should trigger this skill.
- 18
Personal Voice
/personal-voiceMake all writing output match the user's own voice, calibrated from 5 real writing samples plus their explicit rules on sentence length, rhythm, forbidden phrases, and tone. Has two modes: a one-time calibration that builds a voice profile from samples, and an application mode where every draft is written and verified against that profile. Use this skill whenever the user asks for writing "in my voice", "like I'd write it", "sound like me", wants to set up or update their voice profile, or whenever drafting anything that will be published or sent under the user's name (emails, posts, articles, bios) once a profile exists. Do NOT use to imitate the voice of any person other than the user, and do not use for content where a house style overrides personal style (legal filings, API docs).
- 19
Prompt Maker
/prompt-makerRestructure messy, rambling, or stream-of-consciousness requests into a clean task spec BEFORE executing them, so nothing buried in the dump gets lost. Use this skill whenever the user's message is a brain dump: long unstructured paragraphs, voice-dictated text, multiple tangled tasks, requests with contradictions, "sorry this is messy but", walls of context with the actual ask buried in the middle, or copy-pasted notes ending in "can you do this". Do NOT use for short clear requests, follow-ups within an ongoing task, or casual conversation; restructuring a clean request is pure friction.
- 20
Red Pen
/red-penNever show the user a first draft. Run every writing task through a self-critique loop — draft, attack the draft as the harshest reviewer in the room, rewrite, and repeat until a full review pass finds zero flags — then return only the final plus a change log. Use for any writing the user actually cares about: emails, LinkedIn posts, newsletters, docs, announcements, client messages. Trigger whenever the user says 'run the loop', 'self-critique this', 'make it bulletproof', 'don't give me a first draft', 'be brutal', or hands over a task where quality matters more than speed. This is a single-agent loop; for the three-agent version use the-team.
- 21
Reddit Researcher
/reddit-researcherDeep research engine covering the last 30 days across 7 sources — Reddit, X/Twitter, YouTube, LinkedIn, Hacker News, Web, TechCrunch. Uses Apify actors. Synthesizes findings into grounded, cited reports with deduplication, relevance scoring, and cross-source signal detection. Use when asked what people are saying about a topic, for current sentiment, or for a sourced scan of recent discussion.
- 22
Skill Audit
/skill-auditReview the user's installed Claude Skills for overlap, dead weight, vague triggers, and gaps, then deliver a keep/merge/fix/delete action plan. Use whenever the user types /skill-audit, says their skills overlap or fire at the wrong times, asks which skills to keep or delete, wants their skill library cleaned up or organized, or asks "which of my skills are actually useful". Also use after a user has installed a batch of new skills and wants to know how they fit together.
- 23
Skill Creator
/skill-creatorTurn a plain-language description of a desired behavior into a properly structured, installable SKILL.md following Anthropic's skill-authoring best practices: trigger-optimized description, explain-the-why instructions, output templates, examples, and anti-trigger calibration. Use this skill whenever the user says "make a skill", "write a skill for", "turn this into a skill", "create a SKILL.md", describes a behavior they want Claude to follow every time, or complains about re-explaining the same instructions across chats (a recurring-behavior request is a skill request in disguise). Do NOT use for one-off task instructions, MCP server development, or general prompt-writing advice.
- 24
Ste 100
/ste-100Write or rewrite text in ASD-STE100 Simplified Technical English. ONLY use this skill when the user explicitly invokes it by name — i.e. they type "/ste-100" or literally write "use the ste skill" / "apply ASD-STE100". Do NOT trigger it on paraphrased intent such as "simplify this", "make it clearer", "write technical documentation", or "shorter sentences please" — the user has deliberately scoped this skill to explicit invocation only. For those requests, respond normally without loading this skill unless they name it.
- 25
Tc Social Carousel
/tc-social-carouselBuild Instagram carousel slides for TC Social using the fixed six-template system (cover/hook, list, quote, chart, photo, CTA) in the TC Social brand — warm neutral backgrounds, single burgundy accent, Bootzy display type, lowercase-first anti-guru voice, 1080x1350 artboards. Use this skill whenever the user asks for a TC Social carousel, Instagram carousel, IG slides, swipe post, carousel template, or any social slide/card design for TC Social — even if they only mention one slide, a hook, or "make this into a carousel." Also use it when adjusting or iterating on previously generated TC Social carousel designs.
- 26
Tighten
/tightenCut bloat from any draft — posts, emails, articles, scripts, landing pages — while keeping 100% of the meaning and the author's voice. Use whenever the user types /tighten, pastes a draft and asks to shorten, trim, condense, or "make it punchier", complains a piece is too long or rambling, or needs to hit a word/character limit (LinkedIn, X, email subject lines). Also use proactively when the user asks for feedback on a draft that is clearly overwritten.
- 27
Viral Recipe
/viral-recipeCapture the "recipe" of a single post that went viral, then reproduce that recipe for any new topic or person. Use this skill when someone has one post that did unusually well (for their standards) and wants to repeat what made it work — "this post went viral, capture why", "recreate this post for a different topic", "what's the recipe here". The skill stores the original viral post for reference, then iterates through questions and answers with the user to generate a new post that follows the same format, hook, caption structure, and tone — about anything, for anyone. Replace the reference post below with the actual viral post you're capturing.
- 28
Writing Clearly And Concisely
/writing-clearly-and-conciselyApply Strunk's timeless writing rules to ANY prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Makes your writing clearer, stronger, and more professional. Use when asked to tighten, edit, or review prose, or before shipping text someone else will read.
- 29
Xlsx
/xlsxUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like \"the xlsx in my downloads\") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
No skills match that search
Try a shorter word, or clear the filter to see every skill.
New skills are on the way
This library is empty for now. Skills appear here the moment we publish them.