Skip to content
AI stack, guide

How to install and vet marketing skills

Last verified

Find skills with npx skills find and install them with npx skills add owner/repo. Before you use one on client data, read its LICENSE file, open the SKILL.md, list any bundled scripts without running them, check what it can write or send out, and pin the commit you reviewed.

Find skills with npx skills find

The skills CLI is the tool behind skills.sh, a directory and installer for agent skills. Run npx skills find to search it from the terminal. The directory ranks skills by installs, and an install count says how often something was copied. It does not say whether the skill is safe, licensed for your use, or any good.

Agent Skills is an open format for portable instruction folders that agents load on demand, such as an ad audit or a creative testing playbook. Because a skill is a folder and not a product, you can read all of it before you use it.

Install with npx skills add

Install a whole repository with npx skills add owner/repo. Install one skill from a repository by adding the skill name. The README of the skills CLI documents these forms, and this guide states no other flags because none were verified.

  1. 1.Install a full pack

    Use this when you want every skill in a repository. The marketingskills repository holds 53 skills for CRO, copywriting, paid ads, tracking, SEO and growth.

    npx skills add coreyhaines31/marketingskills
  2. 2.Install a pack of a few skills

    The user-acquisition-skills repository holds 15 skills for paid acquisition in app and subscription businesses. The author of this site publishes it, so treat it like any other repo and vet it the same way.

    npx skills add ua5er/user-acquisition-skills
  3. 3.Install a single skill

    Add --skill and the skill name when you need one playbook and not the whole set.

    npx skills add ua5er/user-acquisition-skills --skill meta-ads-launch-planner

A larger pack is not a better pack. Packs of several hundred skills often cover near-duplicate topics, while depth tends to show up in packs of 6 to 50 skills. Start with one or two skills that match a job you do every week.

Vet a skill before you use it on client data

Vetting a skill means reading what it will tell the agent to do and what it can reach. The skills CLI itself runs git and fetches skill repositories, and skills can bundle scripts, so read first and run nothing until you have. The skills.sh site names no licence and has a security audit section whose scope is not described, so do not treat it as a clearance.

Vetting checklist for one skill
CheckWhat to doStop if
LicenceOpen the LICENSE file in the repository and in the skill folder.There is no file. No licence means all rights reserved, so link to it and do not copy or host it.
SKILL.mdRead the whole file, including when it says not to use the skill.It is a persona prompt with no procedure, thresholds or inputs.
ScriptsList the bundled files and open each script. Do not run any.A script fetches code, calls unknown hosts or edits files outside its job.
WritesFind what it can change: files, ad accounts, email, a CRM.It writes to an ad account without a preview or a read-before-write step.
Data outNote which tools or APIs receive your data when you wire them in.You cannot say where client data goes.
PinRecord the commit you reviewed and install from that state.The repository changes and you have not reread the diff.

Licences are read per repository, and a single skill can carry another one. A repository can have no repo-level file and one LICENSE.txt per skill, and some of those are source-available and not open source. MIT and Apache-2.0 still require you to keep the copyright notice if you copy anything.

Good skills tend to share a few traits. They state when not to use them, cap their claims by the inputs they receive, separate observation from recommendation, and read before they write on an ad account. If MCP servers are part of the setup, remember that they run with your permissions, so review each server and its scopes too.

One context file for all packs

Many SKILL.md files lean on a project context file that holds your product, audience, offer and constraints. The marketingskills pack shares one product marketing context file across its 53 skills. Keep one neutral file of your own and point every pack at it, so you answer those questions once and not once per skill.

  • Product and offer in two or three sentences.
  • Audience and the markets you buy in.
  • Conversion events and the metric you optimise for.
  • Brand and legal limits on claims.
  • Rules the agent must follow, for example read-only access to ad accounts.

Where skills live per client

Claude Code, Codex and Cursor each load skills from their own locations, and those locations are defined in each client's documentation. No folder path was verified for this guide, so none is given here. Check the docs of your client, and confirm after an install that the agent lists the skill before you rely on it.

Claude Code needs a paid Claude plan or API billing, because the Free plan has no Claude Code. Codex is included in several ChatGPT plans, and API-key use bills at API rates.

Questions

How do you install Claude skills?
Run npx skills find to search, then npx skills add owner/repo to install a repository. To install one skill, add --skill and its name. Before using it on client data, read the licence, the SKILL.md and any scripts, and pin the commit you reviewed.
Are Claude skills safe?
Not automatically. A skill is a folder of instructions that can bundle scripts, and an agent follows it with your permissions. Read the SKILL.md, list the scripts without running them, check what it can write or send out, and treat directory audits as a first filter only.
What skills should you give Claude Code?
Start with one or two skills tied to a weekly job, such as an ad audit, a creative test plan or tracking setup. Skills that state when not to use them and work from defined inputs tend to be more useful than broad persona prompts.
Is there a marketing skill for Claude?
Yes. Third-party repositories publish marketing skills, for example a 53-skill library for CRO, copy, paid ads, tracking and SEO, and a 15-skill pack for paid user acquisition. Vet each one for licence, scripts and write access before you use it.

Sources

Each source shows the date it was last checked.

  1. Agent Skills agentskills.io/home
  2. Anthropic claude.com/pricing
  3. Anthropic code.claude.com/docs/en/overview
  4. Cursor cursor.com/pricing
  5. learn.chatgpt.com learn.chatgpt.com/docs/pricing
  6. GitHub coreyhaines31/marketingskills: LICENSE
  7. GitHub ua5er/user-acquisition-skills: LICENSE
  8. GitHub coreyhaines31/marketingskills
  9. GitHub ua5er/user-acquisition-skills
  10. Vercel skills.sh

Want your own AI and acquisition setup checked for gaps and risks? Start with a growth audit.

See the growth audit