These are real open-source skills built by named people, laid out like a small sales team so you can see who does what. Each entry tells you plainly what the skill does and when to grab it, credits the maker, and gives you two ways in: install it in one line, or paste the file into a Claude Project. The one thing we wrote ourselves sits on the first-message desk: a brief that keeps your voice and will not invent consent, a metric, or a case study.
How to install any skill on this page
Two routes, so nobody gets stranded in a terminal.
- The one-line install. If you are comfortable in a terminal, the shared command is
npx skills add <repo>, with an optional--skill <name>to pull just one out of a pack. For a skill that sits deeper in a repo, the line uses the full GitHub link to that skill instead. We give the exact line under each skill. - The paste route. If the terminal is not your thing, open the skill's SKILL.md file in its GitHub repo, copy the whole file, and paste it into a Claude Project. Same instructions, no command line. We link every file below.
1. First messages
The desk that writes the note that starts the relationship. Starts with our own brief, then an open-source first-email skill from a GTM pack.
The "sounds like you" first-message brief by AI with Adele
The one thing on this page we built ourselves. It writes a first email or LinkedIn note in your voice: one true reason you are writing, one small ask, no fake proof. Save it as sounds-like-you-first-message.md, paste it into a Claude Project, and it will refuse to invent a metric, a mutual friend, or permission to contact someone. UK PECR is your job to check; the brief will not pretend you already may.
--- name: sounds-like-you-first-message description: Writes a first outreach message that sounds like the sender in their own voice. Asks for voice, offer, and whether you are allowed to contact the person before drafting. Use for cold or warm first emails, LinkedIn notes, or follow-up openers. Never invents a metric, a case study, or consent. UK English. --- # The "sounds like you" first-message brief You are my outreach editor. Your job is one first message that a real person would send: short, specific, and in my voice. What is at stake is trust. A template blast gets deleted. A message that sounds like me, names one true reason I am writing, and asks one small next step might get a reply. You never invent a number, a case study, a mutual friend, or permission to contact someone. FIRST, CHECK. Ask me these and wait. Do not draft until I have answered: - Who is this for (name, role, company if I have them)? - Why them, specifically, in one honest sentence I can stand behind? If I only have a vague "they look like a fit", stop and help me find one real reason or mark it [gap]. - What do I want them to do next (one small ask: a 15-minute call, a yes/no, a link to read)? - How do I usually sound? If I have not given you a voice sample, ask for 3 to 5 sentences I have actually sent, or point me at [make AI write in your voice](https://www.aiwithadele.com/guides/make-ai-write-your-voice). - Am I allowed to contact this person? UK PECR and similar rules apply. If I have not confirmed I may email or message them, write [gap: consent / PECR] and do not produce a send-ready email. You are not my lawyer. You only refuse to pretend permission exists. THE REFRAME, teach me this in plain words before the draft: Most "AI outreach" fails because it writes a brochure. A first message is not a pitch deck. It is a note from one person to another: I noticed X, I do Y for people like you, here is one true proof or none, here is one small ask. If I cannot name X, we do not send. THE METHOD: 1. One reason you exist in their inbox. Specific. Not "I help companies like yours scale". 2. One line of who I am, in my words, no slogan. 3. One proof I actually gave you, or none. If I have not given a result, do not invent 27% or "we 3x'd pipeline". Write [gap] or omit. 4. One ask. Easy to answer. No calendar dump unless I asked for it. 5. Length: about 80 to 120 words for email; 300 characters or fewer for LinkedIn. Cut anything that sounds like a sequence, a PS of five links, or "just circling back" on a first touch. 6. Subject line (email only): 3 options, lowercase-friendly, no fake urgency, no "quick question" unless that is honestly my voice. OUTPUT, in this order: - The one-sentence reason this person is getting a note. - The draft. - Three subject lines (email) or a first-line variant (LinkedIn). - What I must verify before I hit send (facts, consent, names). - One line I should delete if I am even slightly unsure it is true. WORKED EXAMPLE (illustrative, made up, do not copy the facts onto my message): I sell plain-English bookkeeping to two-person design studios. I am writing to Sam at a studio whose site still says "invoices via email". Reason: their site asks clients to email invoices. Draft starts with that, offers a 20-minute "show me your current invoice path" chat, no fake "we saved studios 9 hours a week". RULES: NEVER invent a metric, a client name, a mutual connection, or that I have permission to write. If a claim needs a figure I have not given, write [gap]. UK English, plain words. No em dashes in the draft unless my sample uses them. A skill drafts, I decide. SELF-CHECK: end by naming the sentence most likely to sound like a template, the claim you are least sure is true, and whether any line would need a number I have not supplied.
cold-email by Sid Chaudhary
The SDR first-email skill from Sid's GTM pack: a real trigger signal and a body under 120 words. Grab it when you have a trigger (a post, a hire, a site change) and need the opener. Sid's pack is MIT and free; the line below installs just this cold-email skill.
npx skills add https://github.com/sidchaudhary/gtm-skills/tree/master/skills/sdr/cold-emailOr open skills/sdr/cold-email and paste that SKILL.md into a Claude Project.
2. Follow-ups
The desk that writes the second and third note, and keeps a relationship warm without nagging.
email-sequence by Sid Chaudhary
Builds a multi-touch sequence from scratch, or audits one you already have and rewrites the weak steps. Grab it when the first note is done and you need the rest of the run, or when replies are thin.
npx skills add https://github.com/sidchaudhary/gtm-skills/tree/master/skills/sdr/email-sequenceOr paste skills/sdr/email-sequence into a Claude Project.
cold-email-sequence-generator by OneWave AI
A multi-touch outbound sequence with a method behind the spacing. Grab it when you want the whole run written in one go, then edit every line before anything sends.
npx skills add OneWave-AI/claude-skills --skill cold-email-sequence-generatorOr open its SKILL.md in OneWave-AI/claude-skills/cold-email-sequence-generator, copy it, and paste it into a Claude Project.
3. Call prep
The desk that gets you into a conversation without a 12-page briefing pack.
call-preparation by Sid Chaudhary
Two modes from the GTM AE set: pre-call (agenda, discovery questions, likely objections) and post-call coaching if you paste notes. Grab it when the meeting is on the calendar and you have 20 minutes to prep.
npx skills add https://github.com/sidchaudhary/gtm-skills/tree/master/skills/account-executive/call-preparationOr paste skills/account-executive/call-preparation into a Claude Project.
sales-call-prep-assistant by OneWave AI
A research brief plus discovery questions for the next call. Grab it when you know the company name and almost nothing else, and you need an honest one-pager to walk in with.
npx skills add OneWave-AI/claude-skills --skill sales-call-prep-assistantOr open its SKILL.md in OneWave-AI/claude-skills/sales-call-prep-assistant, copy it, and paste it into a Claude Project.
4. Pipeline notes
The desk that looks at what is stuck, without turning you into a RevOps team of one.
pipeline-review by Sid Chaudhary
Reads a pipeline and flags stuck deals, thin coverage, and a next action per deal. Grab it when your list is a mess and you need an honest weekly pass over it. You still supply the real numbers.
npx skills add https://github.com/sidchaudhary/gtm-skills/tree/master/skills/account-executive/pipeline-reviewOr paste skills/account-executive/pipeline-review into a Claude Project.
lead-list by Sid Chaudhary
Builds a target list before you reach out, scoring each name hot, warm, cold or skip against your ideal-customer definition, with a source and a confidence level per lead. Grab it before you write a sequence, so the list has a reason to exist.
npx skills add https://github.com/sidchaudhary/gtm-skills/tree/master/skills/sdr/lead-listOr paste skills/sdr/lead-list into a Claude Project.
Where the line is
- These are other people's work, credited and open. Every third-party skill here is MIT-licensed and built by the named maker. Study them, install them, credit them. Do not lift their text into your own page and call it yours.
- A skill drafts, you decide. Read every line before it goes out. Never send a first draft unedited.
- Never publish an invented number, and never invent consent. Our first-message brief leaves a [gap] rather than make a statistic or a PECR permission up. If a skill hands you a figure or a "they said yes" you did not give it, check it or cut it.
Pick a desk and install one today
Do not fit out the whole team at once. If the blank page is a first email, start with our brief. If you already have a trigger and want a method, grab Haines or Sid. If the meeting is tomorrow, use call prep. Two of these lean on writing in your own voice. If your drafts still sound like a brand account, fix that first: make AI write in your voice.
Looking for skills for a different job? Head back to the hub: AI skills by role. Marketing is already live: AI marketing skills.
A few quick questions
Are these sales skills free?
Yes. Every third-party skill on this page is open-source, built by a named person and shared under an MIT licence. You install one with a single line in the terminal, or you open its SKILL.md file on GitHub, copy it, and paste it into a Claude Project. Our own first-message brief is free to copy on this page.
Do I need to use the terminal?
No. The one-line install with npx skills add is there for people who are comfortable in a terminal. If you are not, open the skill's SKILL.md on GitHub, copy the whole file, and paste it into a Claude Project.
What is the first-message brief on this page for?
It is our own brief for writing a first outreach note that sounds like you. It asks for your voice, one true reason you are writing, one small ask, and whether you are allowed to contact the person. It will not invent a metric, a case study, or consent.