AI marketing skills, organised like a team

A curated set of real, free marketing skills you can install in one line or paste in, sorted by the job, plus our own GEO/AEO brief. Think of it as an org chart: pick the department you need, grab the best skill in it, and put it to work today.

Claude Open-source

These are real open-source skills built by named people, laid out like a marketing 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 in the SEO department: our GEO/AEO brief for getting a page cited by AI answers.

Run the whole team on one question

marketing-council by Corey Haines

Runs your whole team at once: a simulated board of famous marketers argues one question, so you hear several angles before you decide. It is a persona simulation, and the value is the range of takes it forces onto one call. Grab it when you are stuck on a decision.

npx skills add coreyhaines31/marketingskills --skill marketing-council

Or open the skill's SKILL.md in coreyhaines31/marketingskills, copy it, and paste it into a Claude Project.

1. Content and copy

The department that turns a blank page into a draft: writing, editing, and getting one piece of work to stretch further.

Curated picks

copywriting by Corey Haines

Writes the first draft of a piece of copy from a brief, holding a real method rather than guessing. Grab it when you have the point but not the words yet.

npx skills add coreyhaines31/marketingskills --skill copywriting

Or open its SKILL.md in coreyhaines31/marketingskills, copy it, and paste it into a Claude Project.

copy-editing by Corey Haines

Takes a draft you already have and tightens it: cuts the padding, fixes the flat lines, keeps your meaning. Grab it when the words exist but the copy is not landing.

npx skills add coreyhaines31/marketingskills --skill copy-editing

Or open its SKILL.md in coreyhaines31/marketingskills, copy it, and paste it into a Claude Project.

content-strategy by Corey Haines

Steps back from a single post and helps you decide what to make and why, so the calendar has a spine. Grab it when you are posting without a plan and it shows.

npx skills add coreyhaines31/marketingskills --skill content-strategy

Or open its SKILL.md in coreyhaines31/marketingskills, copy it, and paste it into a Claude Project.

content-repurposer by OneWave

Takes one finished piece and reshapes it for other formats so a single idea earns its keep. Grab it when you have written something good once and want more from it.

npx skills add OneWave-AI/claude-skills --skill content-repurposer

Or open its SKILL.md in OneWave-AI/claude-skills, copy it, and paste it into a Claude Project.

2. Social

The department that gets the work out onto feeds, and one heavier tool for people who want a proper drafting agent.

Flagship pick

social-media-agent by LangChain

Give it a URL and it drafts a Twitter and a LinkedIn post from what it finds, with a human-in-the-loop step where you approve or edit before anything is scheduled. Be honest with yourself here: this is a developer-grade agent you clone and run (Node and LangGraph), not a one-line skill. It is heavier setup, and it is worth it if you are comfortable with that. It does not install with npx skills add.

It is a developer project, so there is no paste route. Clone and run it from the repo: langchain-ai/social-media-agent.

Curated picks

social by Corey Haines

Drafts social posts from your idea with a lighter touch than the LangChain agent, no setup beyond installing it. Grab it when you just want a post written and out.

npx skills add coreyhaines31/marketingskills --skill social

Or open its SKILL.md in coreyhaines31/marketingskills, copy it, and paste it into a Claude Project.

social-repurposer by OneWave

Takes one social post and recuts it for other platforms so it reads native everywhere rather than pasted. Grab it when you have one caption you like and four places it needs to fit.

npx skills add OneWave-AI/claude-skills --skill social-repurposer

Or open its SKILL.md in OneWave-AI/claude-skills, copy it, and paste it into a Claude Project.

3. SEO and GEO/AEO

The hero department. It starts with the brief we wrote ourselves, for getting a page cited by AI answers, then the full open-source engine for people who want the lot.

Our own flagship brief

The GEO/AEO brief by AI with Adele

The one thing on this page we built ourselves. It gets a page ready to be cited by AI answers, ChatGPT, Claude, Perplexity and Google AI Overviews, by making the answer easy to lift. Save it as geo-aeo-brief.md, paste it into a Claude Project or above a page you are working on, and it walks you through the reframe and the method. It never puts an unverified number on your page, and it teaches the mechanism instead.

SkillThe GEO/AEO brief (geo-aeo-brief.md)
---
name: geo-aeo-brief
description: Gets a web page ready to be cited by AI answers such as ChatGPT, Claude, Perplexity and Google AI Overviews. Reads a page or a topic, works out whether it is quotable, and rewrites it so an AI assistant can lift a clean answer straight from it. Use whenever the user wants to show up in AI answers, be cited by an AI assistant, do GEO or AEO, or make a page answer-ready. Teaches the mechanism and never invents a statistic.
---

# The GEO/AEO brief

You are my answer-engine editor. Your job is to get one of my pages cited by the AI assistants people now ask instead of searching: ChatGPT, Claude, Perplexity, Google AI Overviews. What is at stake is real: those tools quote a handful of sources and skip the rest, so a page that is not easy to lift gets no mention at all, however good it is. You make my page the one that is easy to quote, and you never put a number on it that I cannot stand behind.

FIRST, CHECK. Before you touch anything, ask me these and wait for the answers, because they change what you do:
- Do I currently show up in ChatGPT, Perplexity or Google AI Overviews when someone asks about my topic? Have I checked, and what did I see?
- Which exact page are we working on, and what is the one claim I want it to be cited for?
- Who am I competing with for that answer, the sites that get quoted today?
If I have not given you the page or the claim, stop and ask. Do not guess my topic, and do not rewrite a page you have not been shown.

THE REFRAME, teach me this in plain words before the method:
Traditional SEO gets a page RANKED: it earns a spot on the results list and waits for a click. Answer-engine work gets a page CITED: an AI assistant reads it, lifts a sentence, and names me as the source inside its answer. These are different goals. A page can be cited even when it sits on page two of normal search, because the assistant is choosing the clearest answer to quote, not the highest rank. So the target is simple: be the easiest correct answer to lift, whatever your normal search rank.

THE METHOD. Make the answer easy to lift. Go through the page and do these:
1. ONE CLEAR CLAIM PER SECTION. Under each header, put a single, self-contained sentence that answers the question directly, early, in plain words, so it makes sense pulled out on its own with no surrounding context. This is the sentence an assistant can quote.
2. HEADERS THAT MATCH REAL QUESTIONS. Rewrite headers into the plain wording a person actually asks, so the page maps onto the question an assistant is answering. No cute headings.
3. A SHORT FAQ. Add three to five real follow-up questions with short, honest, self-contained answers. This is some of the most liftable text on a page, so make each answer stand alone.
4. STRUCTURED DATA. Recommend the schema.org types that fit the page (for example FAQPage for the FAQ, Article for the body) and say plainly that the visible words and the structured data must match word for word.
5. AN llms.txt POINTER. Suggest a plain llms.txt file at the site root that points AI crawlers at the pages worth reading, and say what to list in it for this page.
6. EARN THIRD-PARTY MENTIONS. Explain that assistants often cite sources other than my own site, so name two or three realistic places a mention could come from for my topic (a directory, a round-up, a community answer, a partner's page) and the honest way to earn each. Never fabricate a mention.

OUTPUT, in this order:
- The one claim this page should be cited for, in a single sentence.
- The rewritten headers, question-shaped.
- The lift-ready sentence to sit under each header.
- The FAQ, three to five question-and-answer pairs.
- The schema types to add, with a note that visible text and markup must match.
- The llms.txt lines for this page.
- Two or three third-party mention targets with how to earn each.

WORKED EXAMPLE (illustrative, made up):
Page: a small studio's guide to repointing brickwork. Claim to be cited for: "Repointing lime mortar is best done in spring or autumn, not summer."
- Header rewritten from "Timing considerations" to "When should you repoint brickwork?"
- Lift-ready sentence under it: "Repoint lime mortar in spring or autumn, when it is mild and damp, because summer heat dries the mortar too fast and it cracks."
- FAQ pair: "Can you repoint in winter? No, lime mortar can freeze before it sets, so wait for a mild spell."
- Schema: FAQPage on the FAQ, Article on the body, wording identical to the page.
- Third-party target: a local heritage-trades directory that lists specialists, earned by a genuine listing, not a planted review.

RULES: NEVER invent a statistic, a competitor claim, a ranking or a number to make a point land. If a claim needs a figure I have not given you, write it as [gap] and ask me for the real one. Do not tell me GEO gets a set percentage of traffic or a set lift; you do not have that data and neither of us should publish it. Work from the mechanism, not made-up proof. UK English, plain words.

SELF-CHECK: end by naming the one section least likely to be lifted cleanly as it stands, the claim on the page you are least sure is true (so I can verify it before publishing), and whether any sentence you wrote would need a real number I have not supplied.
Curated picks

ai-seo by Corey Haines

The full pro-grade GEO engine for people who want the whole thing, not just a brief. Where ours is a focused starting point, this is the built-out install. Grab it when GEO is a serious, ongoing part of your work.

npx skills add coreyhaines31/marketingskills --skill ai-seo

Or open its SKILL.md in coreyhaines31/marketingskills, copy it, and paste it into a Claude Project.

seo-audit by Corey Haines

Reads a page and reports where it is weak for search, sorted so you know what to fix first. Grab it when a page should be getting found and is not.

npx skills add coreyhaines31/marketingskills --skill seo-audit

Or open its SKILL.md in coreyhaines31/marketingskills, copy it, and paste it into a Claude Project.

schema by Corey Haines

Generates the structured data that helps both search and AI answers read your page correctly. Grab it when you want your FAQ or article marked up properly. It pairs naturally with the GEO/AEO brief above.

npx skills add coreyhaines31/marketingskills --skill schema

Or open its SKILL.md in coreyhaines31/marketingskills, copy it, and paste it into a Claude Project.

4. Ads and paid

The department for what you put money behind: the creative, and the checks that stop you burning budget.

Curated picks

ads by Corey Haines

Drafts paid ad copy with a method behind it rather than a lucky line. Grab it when you have an offer and need the ad written.

npx skills add coreyhaines31/marketingskills --skill ads

Or open its SKILL.md in coreyhaines31/marketingskills, copy it, and paste it into a Claude Project.

ad-creative by Corey Haines

Works on the creative side of an ad, the concept and the visual angle, not just the words. Grab it when the copy is fine but the idea is flat.

npx skills add coreyhaines31/marketingskills --skill ad-creative

Or open its SKILL.md in coreyhaines31/marketingskills, copy it, and paste it into a Claude Project.

google-ads-audit by Swan (swan-gtm)

Reviews a Google Ads setup and flags what is leaking money or badly built. Grab it before you scale spend on an account you are not sure is sound.

npx skills add swan-gtm/gtm-skills --skill google-ads-audit

Or open its SKILL.md in swan-gtm/gtm-skills, copy it, and paste it into a Claude Project.

the paid-ads set by Sid Chaudhary (Intempt)

The performance-marketer role from Sid Chaudhary's GTM skills, built around running and improving paid campaigns. Grab it when paid is a standing part of your job, not a one-off.

npx skills add sidchaudhary/gtm-skills

Or open the SKILL.md files in sidchaudhary/gtm-skills, copy the one you want, and paste it into a Claude Project.

5. Email and lifecycle

The department that keeps the relationship going: the emails, the outreach, the newsletter, and the small tweaks that lift open rates.

Curated picks

emails by Corey Haines

Drafts marketing emails with a real structure, problem to offer to one ask. Grab it when you have something to send and a blank compose window.

npx skills add coreyhaines31/marketingskills --skill emails

Or open its SKILL.md in coreyhaines31/marketingskills, copy it, and paste it into a Claude Project.

cold-email by Corey Haines

Writes outreach that reads like a person rather than a template blast. Grab it when you are reaching people who do not know you yet.

npx skills add coreyhaines31/marketingskills --skill cold-email

Or open its SKILL.md in coreyhaines31/marketingskills, copy it, and paste it into a Claude Project.

newsletter-management by Manoj Bajaj

Helps run a newsletter as an ongoing thing rather than a scramble each week. Grab it when the newsletter is a habit you want to keep steady.

npx skills add manojbajaj95/claude-gtm-plugin --skill newsletter-management

Or open its SKILL.md in manojbajaj95/claude-gtm-plugin, copy it, and paste it into a Claude Project.

email-subject-line-optimizer by OneWave

Works only on the subject line, the one bit that decides whether the rest gets read. Grab it when the email is written and the open rate needs a lift.

npx skills add OneWave-AI/claude-skills --skill email-subject-line-optimizer

Or open its SKILL.md in OneWave-AI/claude-skills, copy it, and paste it into a Claude Project.

How to install any skill on this page

Two routes, so nobody gets stranded in a terminal.

  1. 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. We give the exact line under each skill. Corey Haines' pack also installs as a Claude Code plugin: run /plugin marketplace add coreyhaines31/marketingskills, then /plugin install marketing-skills.
  2. 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 repo below.

Where the line is

  • These are other people's work, credited and open. Every skill here is MIT-licensed and built by the named maker. We point you to the best per job and tell you when to grab it. Study them, install them, credit them. Do not lift their text into your own page and call it yours.
  • A skill drafts, you decide. Install one and you still read every line before it goes out. The install is the easy part; the judgement about what is true and what fits your brand is still yours.
  • Never publish an invented number. Our GEO/AEO brief is built to leave a [gap] rather than make a statistic up, and it will not tell you GEO gets a set percentage of anything. If a skill hands you a figure you did not give it, check it or cut it.

Pick a department and install one today

Do not try to fit out the whole team at once. Find the job on your plate right now, the post that needs writing, the page that should be getting cited, the ad account you are unsure about, and grab the one skill for it. Install it in a line or paste the file into a Project, and you are working with a real method inside a minute.

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. And if you want a worked walkthrough of stretching one idea across a week of posts, we have a full guide for that: turn one idea into a week of content.

Looking for skills for a different job? Head back to the hub: AI skills by role.

A few quick questions

Are these marketing skills free?

Yes. Every 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. Either way it costs nothing.

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. That gets you the same instructions without touching a command line.

What is the GEO/AEO brief on this page for?

It is our own brief for getting a page cited by AI answers such as ChatGPT, Claude, Perplexity and Google AI Overviews. Traditional SEO gets you ranked; this teaches the moves that get you quoted as the answer, like one clear claim per section, plain question-shaped headers, a short FAQ and structured data. It teaches the method, and it never puts an unverified statistic on the page.