Marketing Skills is Corey Haines’s library of reusable instructions for working on marketing tasks with AI agents. A skill describes how to approach a task, what context to gather and what to check. It can help you plan content, write a page or review campaign measurement. You still supply the business facts, make the decisions and take responsibility for the work.

At LetBrand, the appeal is practical: you can save a working method and use it again. Someone who works methodically, provides useful context and reviews and measures the output can build a useful marketing foundation with Codex or Claude’s tools. The quality depends on their knowledge of the business and how they assess the suggestions. Installing a library does not give you commercial experience, customers or results.

What Marketing Skills covers

The Marketing Skills website↗ presents the library for founders and marketers working with agents. The repository contains folders with a SKILL.md file and, in some cases, references and other resources. An agent reads the relevant instructions when tackling a suitable task. You are not installing a new model or training one on your data.

Choose skills by the problem you need to solve. content-strategy helps decide what to publish, copywriting works on page copy and copy-editing reviews existing text. Organic acquisition is covered by skills including seo-audit, ai-seo, schema and programmatic-seo. cro addresses page and form conversion. There are also instructions for advertising, email, pricing, onboarding and analytics. Names and content change, so check the repository catalogue↗ before copying commands from an older guide.

I would start with something you already understand: describing a service, organizing customer questions or improving a page you know well. If you cannot yet explain who buys, why they buy or what you can promise, fluent copy can conceal those gaps. The library can help you work through the questions, but you will need answers from the business and conversations with customers.

Start with product context

The current product-marketing skill↗ prepares a shared document at .agents/product-marketing.md. It covers the product, audience, positioning, alternatives, objections, customer language and brand voice. Other skills can start with that information instead of reconstructing the business in every conversation.

For a small business, the document should distinguish facts, hypotheses and unanswered questions. An objection recorded in a real conversation is evidence; one suggested by the assistant is something to investigate. If the agent drafts the context from your website, check what is missing too: available capacity, service limits, margins and conditions that are absent from the public page. Share only the information needed for the task.

Installing it in Codex, Claude Code and Claude Desktop

For a Codex project, skill folders can live in .agents/skills/. OpenAI’s documentation↗ explains discovery and use. The repository recommends npx skills add coreyhaines31/marketingskills: select Codex and check the destination shown. You can inspect the options with npx skills add coreyhaines31/marketingskills --list and choose a smaller set to begin with. Read the instructions before installing them.

Claude Code uses .claude/skills/ for project skills and ~/.claude/skills/ for personal ones. Make the target explicit with npx skills add coreyhaines31/marketingskills -a claude-code. Corey also documents a plugin route: run /plugin marketplace add coreyhaines31/marketingskills, then /plugin install marketing-skills. Directly installed skills support commands such as /copywriting; plugin skills can have a prefix. See the official Claude Code paths and invocation rules↗.

For Claude Desktop chat, account skills follow a different route: enable code execution and file creation, open Customize > Skills and upload a ZIP containing the skill folder. Then enable it. The official Claude guide↗ describes the process; organization accounts may require administrator permissions. Copying a local folder alone does not make it available in chat.

Desktop can also expose other surfaces, including Cowork and Code sessions. Check which one you are using: the official instructions distinguish account skills from local folders. Supply the product context in the environment that will run the task and confirm that it can read it. A portable skill does not guarantee identical tools, permissions or file access in every environment.

We checked the paths and commands against the official documentation. We have not tested a fresh installation in all three applications.

What to check if you installed an earlier version

The repository’s v2 migration renamed skills and combined page-cro and form-cro into cro. Changes relevant to older guides include product-marketing-context → product-marketing, analytics-tracking → analytics, email-sequence → emails and schema-markup → schema. The usual context document path changed too. The migration map↗ explains the names and compatibility behavior.

If you have customized an installation, check the skill names and references to the context document before migrating. Compare files and preserve your changes: installing the new version can leave old folders alongside new ones.

A practical workflow for a small business

Imagine a bicycle repair shop that wants enquiries about servicing bikes before a long ride. This is a hypothetical example. We have not run a campaign or measured results for this shop. Its first objective would be to publish a clear page and learn which questions stop people booking.

The owner first prepares the context: service area, accepted bike types, work included, turnaround times the shop can meet and how appointments are confirmed. They add real customer questions without personal information. If pricing has not been decided, they mark it as unresolved. The assistant must preserve that gap rather than present a proposed price as approved.

Next, they use content-strategy to choose a specific intent: explaining what to check before a long ride and when to bring a bike into the shop. The deliverable is an outline identifying the questions it answers, the sources needed and the booking link. Requesting twenty articles at once would make it harder to see what the business learned from its first page.

With copywriting, they draft the page from the outline. A useful instruction would be: “Use only services confirmed in the context. Flag claims that need checking. End with an appointment request subject to confirmation by the shop.” The owner compares the draft with what the business can actually provide.

They then apply Humanizer to improve the voice and remove empty phrases while preserving facts and conditions. After editing, they check every claim: hours, services, links, requirements and technical advice. Checking facts after the language edit also catches any change in meaning introduced while improving the prose.

The final review follows the customer’s experience: open the page on a phone, test the form and make sure booking conditions are visible. A person approves the version to publish. After publication, the shop records valid enquiries, confirmed appointments and recurring questions. Visits help explain the journey, but they are not bookings.

If traffic or enquiries are sparse, the first finding may be that there is not enough evidence yet. Avoid calling a variant a winner over a tiny difference. Keep the date, page version, change made and observations so you can decide what to try next.

Marketing Skills + Humanizer, one of our favorite combinations

We covered the tool’s origins and use in our earlier article on the Humanizer skill. Marketing Skills + Humanizer is one of our favorite combinations at LetBrand: it helps us separate the purpose of a piece from the review of its voice.

Marketing Skills supplies marketing questions and procedures. Humanizer looks for artificial writing patterns and helps edit without changing the message. For example, “we revolutionize bicycle maintenance” tells a reader little if the service is a brake and drivetrain check. Naming the work is more useful, provided the shop has confirmed it. Humanizer does not guarantee undetectable text or truthful claims. Nor should it remove a condition just to make a sentence sound cleaner.

What to automate next

Once the manual workflow works, you can automate bounded tasks: collecting available metrics, spotting pages due for review or preparing a draft change. The current marketing-loops skill↗ describes recurring processes with a trigger, checks, state and a stopping condition. Scheduling depends on the environment running the agent.

For the bike shop, a periodic review could gather new questions and suggest a page update. It would need an accessible source, permissions, an executor and a record that prevents processing the same item twice. Before sending messages, publishing or spending, it must apply the agreed limits and review steps. Installing the skill does not connect the form, authorize access to customer information or create a permanent service on its own.

The library is distributed under the MIT license↗, which permits use and modification and requires retaining its notice in applicable copies. Agent access and external services have their own terms and costs. I would begin with a small process whose output someone in the business can review, then expand after checking that it helps.

Corey’s post and the sources

On January 19, 2026, Corey Haines introduced Marketing Skills for Claude Code on X↗, emphasizing that the collection was free.

The research rests on the linked website, repository and official documentation, checked on September 7, 2026. The bike shop example and review sequence are LetBrand’s editorial proposals. If you need to connect this process to a website or tool you already use, tell us which task you want to solve.