40 Marketing Skills Loaded with a Single Slash Command
If your team is re-explaining the same campaign brief to an AI every single time you switch tasks — CRO audit in one tab, email sequence in the next, SEO brief after that — there's a better way. The marketingskills toolkit for Claude Code ships 40 pre-built marketing workflows that share a common context layer, so you stop repeating yourself and start shipping faster.
This post walks through how the skill architecture works, how to wire it up, and what to watch once your team is relying on it daily.
1. Why this matters now
Most AI-assisted marketing workflows have a hidden tax: context setup. Before you can ask Claude to write a CRO recommendation, you need to tell it your product, your audience, your tone, your conversion goals. Before the email sequence, you do it again. Before the ad copy, again. That context cost compounds fast across a team of five people running ten tasks a day.
The pain gets worse when you try to standardize. One person's product brief is another's customer persona doc. There's no shared memory, no shared format, and every output feels slightly off-brand compared to the last one.
What the marketingskills toolkit solves is exactly that: a single shared foundation (product-marketing) that every other skill reads before it does anything. You define your context once. The other 39 skills inherit it automatically.
This matters right now because Claude Code's slash-command system makes this pattern genuinely usable at team scale — not just a neat solo trick.
2. The core idea
Every marketing skill in the toolkit is a slash command — /cro, /emails, /seo, /copy, and so on. But before any of them runs, they pull in product-marketing first.
Think of it like a base class in object-oriented programming. The product-marketing skill holds your shared context: what the product does, who the customer is, what tone you use, what your conversion goals are. Every other skill extends that base without re-declaring it.
| Skill | What it does | Inherits from |
|---|---|---|
product-marketing |
Defines product context, ICP, tone | — (the base) |
/cro |
Conversion rate optimization audit | product-marketing |
/emails |
Email sequence generation | product-marketing |
/seo |
On-page SEO recommendations | product-marketing |
/copy |
Ad and landing page copy | product-marketing |
| … 36 more | Various marketing workflows | product-marketing |
The result: you define your product context once, and every downstream skill already knows who it's talking to and what it's selling.
3. How to implement it
Here's how to get the marketingskills toolkit running in your Claude Code setup.
Step 1 — Install the skills
# Clone the marketingskills repo into your Claude skills directory
git clone https://github.com/your-source/marketingskills ~/.claude/skills/marketingskills
# Verify the skill files are present
ls ~/.claude/skills/marketingskills/
# product-marketing.md cro.md emails.md seo.md copy.md ...
Step 2 — Configure your shared product context
Open product-marketing.md and fill in your actual product details. This is the file every other skill reads first.
# Product Marketing Context
## Product
Name: Acme Analytics
Description: Real-time event tracking for SaaS products. No-code setup, Postgres-native.
## Ideal Customer Profile
- Role: Head of Product or Growth Engineer
- Company size: 10–200 employees
- Pain: Drowning in raw event logs, no time to build dashboards
## Tone
Direct, technical, no fluff. We talk to builders, not executives.
## Conversion goals
- Primary: free trial signup
- Secondary: docs engagement, demo booking
Step 3 — Run a skill
Once the base context is set, invoke any of the 40 skills directly from Claude Code:
/cro https://acme.io/pricing
Expected output: Claude reads product-marketing first, then runs the CRO audit with your product's conversion goals already loaded. No re-briefing needed.
Step 4 — Verify context inheritance
You can confirm the base skill is loading by asking Claude to summarize what it knows before it runs the task:
/emails --debug-context
# Context loaded from product-marketing:
Product: Acme Analytics
ICP: Head of Product / Growth Engineer
Tone: Direct, technical
Goal: Free trial signup
# Running: email sequence skill
If the debug output shows your product details, the inheritance chain is working correctly.
4. What to watch in production
Context drift over time. The product-marketing base file is only useful if it stays current. If your ICP shifts or you launch a new product line, every downstream skill will silently use the stale version. Put a recurring task on your team calendar to review product-marketing.md quarterly — or whenever you do a major positioning update.
Skill conflicts on shared concepts. If your /copy skill and /emails skill have different assumptions about tone baked into their individual files, those local overrides will clash with the base context. Audit each skill file for inline tone or audience definitions and remove anything that duplicates what's in product-marketing.md. One source of truth, not two.
Team access and file location. If multiple people are using these skills, they each need the skill files in their local ~/.claude/skills/ directory. There's no automatic sync. The cleanest solution is to keep the marketingskills folder in a shared repo and have everyone pull updates from it:
# Pull latest skill updates from team repo
cd ~/.claude/skills/marketingskills && git pull origin main
Environment differences. On macOS, the ~/.claude/skills/ path resolves without issues. On Linux servers or Docker-based Claude Code setups, confirm the skills directory path matches your Claude Code config before assuming inheritance works. Check your claude_config.json for the skills_dir key if something isn't loading.
Skill depth vs. specificity tradeoff. Forty skills sounds comprehensive, but generic skills can produce generic output. Once you've confirmed the base inheritance is working, consider extending the most-used skills with project-specific addons — a product-marketing-q3-launch.md variant, for example — without touching the base file.
Closing
Define your product context once in product-marketing, and the other 39 skills stop asking you to repeat yourself. That's the whole leverage.
Next step: audit which of the 40 skills your team uses most in the first two weeks, then invest in making those individual skill files more specific to your actual use cases. The shared base gives you breadth; per-skill tuning gives you depth.
🐦 Faster updates on X: @baegseungh7061
📚 More in this series: All posts
💌 Subscribe: Follow on X or grab the RSS
댓글
댓글 쓰기