The Ultimate Clade Code Kit for Marketers: 27 Skills, 12 MCPs, 10 CLIs and 10 Slack Commands

I spent months testing what works. Here’s everything I use to run my AI command center.

---

Ok, I’m stoked about this issue, and I’ve put a LOT of work into it to make sure it’s extremely practical and useful for you.

I use Claude Code every day, and 95% of the time, I’m using the CLI, not the app. If you’ve been using the desktop app or claude.ai, that works, but you’re working with a fraction of what’s available to you. The desktop app is a chat window, but the CLI (paired with an IDE) turns Claude into something closer to a command center for all of your AI workflows.

I’ve spent the last several months building my entire marketing workflow on top of Claude Code CLI. This issue walks through the five things you need to understand to get there: your IDE, Skills, Slash Commands, MCPs, and CLIs.

IDE: A Visual Wrapper to See What Claude Is Doing and Work Faster

When you first install Claude Code, it runs in your terminal. It works, but if you’re not used to working in the terminal, it’s not ideal. If you’re not a developer, then you’re going to want an IDE.

An IDE (Integrated Development Environment) wraps everything into one window: a file explorer on the left, your code or documents in the center, and Claude’s terminal at the bottom. You can see what Claude is changing in real time, and you get visuals that show exactly what Claude is changing. You get tabs, extensions, inline editing and more in an IDE. It’s all in one place, which means you don’t have to be context-switching constantly.

I use Visual Studio Code. It has an official Claude Code extension from Anthropic (over 2 million installs), and the integration is great. You can review Claude’s edits before accepting them, @-mention specific files, and open multiple conversations in separate tabs.

But VS Code isn’t your only option. Here are five others worth checking out if you haven’t chosen your IDE yet.

Cursor is an agent-first IDE built on top of VS Code. Where VS Code treats AI as an assistant, Cursor treats it as the driver. You describe what you want, and it executes autonomously. I find it particularly good for large refactors and multi-file operations.

Google Antigravity is Google’s new agentic development platform, announced in late 2025. It’s built on a modified fork of VS Code and supports multiple AI models (including Claude Opus 4.6 and Sonnet 4.6). The standout feature is the Agent Manager, which lets you run multiple AI agents simultaneously across different workspaces. It’s free during the public preview.

JetBrains (IntelliJ, PyCharm, WebStorm) has an official Claude Code plugin on the JetBrains Marketplace. If your team is already in the JetBrains ecosystem, this keeps everything in one place. Good for enterprise environments.

Windsurf is a standalone agentic IDE that’s more budget-friendly and beginner-friendly than most options. It pioneered the “Cascade” multi-file editing feature and offers 40+ IDE plugins.

Warp is an advanced terminal environment with AI-powered capabilities. If you’re someone who lives in the terminal and wants to stay there, Warp pairs well with Claude Code’s CLI-native workflows.

Now, before trying to set up Claude Code in an IDE, first, make sure you have Claude Code CLI (not the desktop app) installed on your computer. If you don’t, run this in your terminal: npm install -g @anthropic-ai/claude-code.

Now, once you have chosen one of the above (pick whichever one fits how you work), find the download for your operating system (Mac, Windows or Linux), then go to plugins/extensions and find Claude Code.

The point is to get out of the raw terminal and into an IDE. The visibility alone is worth it.

Skills: How to Make Claude Do Specific Work in a Specific Way

Skills are all the rage right now, but they’re nothing too fancy. There are ways for you to tell Claude Code to do a specific thing in a specific way.

If you’ve used ChatGPT’s custom GPTs, skills are a similar concept but they live inside your development environment instead of a separate app. Custom GPTs are self-contained chat experiences you build in OpenAI’s interface. Skills are prompts that plug directly into Claude Code and run alongside your files, your tools, and your workflows.

Skills come in two flavors. The first improves a particular feature or function of Claude Code. For example, it could be a front-end design skill that takes your UIs from generic AI output to something that looks like a human designer built it. The second flavor is workflow. A custom YouTube pipeline skill, for example, could execute all seven production steps (and five sub-skills) with a single command.

Claude Code doesn’t load all the skills you make available to it. Instead, it lists all the skills it can use and provides a short description for each. When you say “I want to use the front-end design skill,” it checks the list, finds the match, and pulls in the full prompt. This keeps the context window from bloating.

Here are the top 27 skills I think B2B marketers should know about.

1. Skill Creator: Anthropic’s own skill for building and benchmarking new skills, install via /plugin. You can create any of the ones listed below with just this one here.

2. Nano Banana 2: AI image generation from Google that renders legible text inside images, great for presentations, ads, and infographics.

3. Cold Email: write B2B cold outreach emails and sequences

4. Email Sequence: create automated email flows and drip campaigns

5. Sales Enablement: create sales collateral and pitch materials

6. Content Strategy: plan content strategy and topic selection

7. Copywriting: write marketing copy for pages and campaigns

8. SEO Strategy: plan and execute search optimization

9. Keyword Research: identify target keywords and search opportunities

10. Analytics Tracking: set up and audit GA4 events, conversion tracking, UTM parameters, and attribution models

11. LinkedIn Posts: create LinkedIn-specific social content

12. Paid Ads: manage Google, Meta, and LinkedIn campaigns

13. Ad Creative: generate and scale ad creative for campaigns

14. Landing Page Generator: build landing pages from templates

15. Pricing Strategy: develop pricing and monetization models

16. GTM Strategy: plan go-to-market motions

17. Product Marketing Context: create foundational PMC documentation

18. Launch Strategy: plan product launches and announcements

19. Lead Magnets: create lead magnets for email capture

20. Form CRO: optimize lead capture and contact forms

21. Page CRO: improve conversion rates on marketing pages

22. A/B Test Setup: plan, design, and implement A/B tests

23. Customer Research: conduct and analyze customer research

24. RevOps: manage revenue operations and lead lifecycle

25. Marketing Psychology: apply behavioral science to marketing

26. Competitive Intelligence: build competitive analysis, battle cards, and positioning intel

27. ICP Builder: build research-backed ICP and buyer persona documents

I created a GitHub repo that has all of these skills in one library here (for free): https://github.com/guerrilla2799/marketing-skills

Just run this command in Claude Code:

/install-skill https://github.com/guerrilla2799/marketing-skills

If that doesn’t work as a one-liner, the manual approach is:

git clone https://github.com/guerrilla2799/marketing-skills.git /tmp/marketing-skills && cp -r /tmp/marketing-skills/skills/* ~/.claude/claudecodeskills/

A word of caution: There are GitHub repositories with hundreds of skills. Download the individual skills you’ve read and understand. Don’t bulk-install entire repositories. More skills mean more noise in the context window, and Claude has to sort through a longer list every time you make a request. Also, with big libraries of 100+ skills, they’re not always vetted and you’re more likely to expose yourself to malicious actors. A bad skill can read files on your machine, run shell commands, and send data to an external server without you knowing. Treat every skill you install like software you’re giving access to your system, because that’s what it is.

---

---

Slash Commands: Shortcuts That Give You More Speed and Control

Slash commands are typed shortcuts inside Claude Code that execute predefined tasks. You type a forward slash, pick a command, and it runs. Some ship with Claude Code out of the box. Others you can create yourself (custom commands live in your .claude/commands/ folder).

Here are 10 that I use regularly.

1. /insights: Surface patterns and analysis from your current project. Good for getting a quick read on what Claude sees across your files.

2. /yolo: Skip permission prompts so Claude can execute without asking you to approve every step. Use this when you trust the task and want speed. (The official flag is --dangerously-skip-permissions, but /yolo is the shorthand.)

3. /model: Switch between Claude models mid-session. If you’re doing heavy reasoning, switch to Opus. If you want speed for a simpler task, drop to Sonnet or Haiku.

4. /context: Show you how much of the context window you’re using. This matters more than you’d think, because once you hit the limit, Claude starts losing track of earlier instructions.

5. /clear: Reset the conversation. I use this constantly. Every time I shift to a new task, I clear the context so Claude starts fresh.

6. /compact: Compress the conversation to save context space while preserving key information. Good when you’re deep into a session and don’t want to start over.

7. /plan: Tell Claude to plan a complex task before executing it. Instead of charging ahead, it lays out the steps and waits for your approval. I use this for anything with more than two or three moving parts.

8. /rewind: Show a list of your previous messages and roll back to any point. Also supports “rewind code only,” which reverts file changes while keeping the conversation history.

9. /export: Save the conversation to a file or clipboard. Useful for documenting workflows, sharing processes with your team, or keeping a record of how you built something.

10. /hooks: Configure automation triggers on specific tool events. You can set actions to fire before file edits, after bash commands, or when a session starts. This is where Claude Code starts feeling like a programmable marketing platform.

There’s no need to install anything to use these. All of them are ready to go. In fact, the one I would start with is /Insights. The first time I used this, a few weeks into my Claude Code journey, it was the best thing to level up my game.

MCPs: Connect Claude to the Tools You Already Use

MCP stands for Model Context Protocol. Think of it as the standard that lets Claude Code talk to external tools and services. An MCP connects Claude to a live system (your CRM, your Google Drive, your meeting notes) so it can read data, take actions, and stay in sync without you copying and pasting between tabs.

Here are 12 MCPs that I think are worth setting up if you’re a B2B marketer.

1. Google Drive MCP: This connects Claude to your Google Workspace. You can search across Drive, edit Google Docs, manage Sheets, and schedule Calendar events without leaving Claude Code.

2. Granola MCP: This connects to Granola.ai for meeting intelligence. Search through transcripts, extract action items, and synthesize across multiple meetings. Available on all plans.

3. Notion MCP: This lets you read and write Notion pages, query databases in natural language, and manage content calendars. If your marketing ops live in Notion, this is essential.

4. HubSpot MCP: This lets you access CRM records, deals, engagement history, and lead scoring data directly from Claude Code. You can log activities and pull pipeline data without exporting CSVs.

5. Obsidian MCP: If you use Obsidian for knowledge management or competitive intelligence, this connects your vault directly to Claude Code for AI-powered analysis.

6. Slack MCP: This lets you search messages, retrieve conversations, and pull context from team discussions. This is useful when you need Claude to reference a decision or campaign debate that happened in Slack.

7. Google Analytics and Search Console MCP: This gives you real-time access to GA4 traffic data and GSC search performance. You can ask questions like “which pages rank 1 through 5 but have a bounce rate over 60%?” without touching a dashboard.

8. Clay MCP: This connects Claude to your Clay workspace for contact search, interaction history, and profile data. If you’re running outbound, this gives Claude direct access to your enriched contact database.

9. SEMRush MCP: This connects Claude to your Semrush account for live SEO and advertising data. You can pull keyword research (search volume, difficulty, broad match keywords), run backlink audits and competitor domain comparisons, and retrieve Google Ads copies for any domain.

10. LinkedIn Ads MCP: This lets you analyze LinkedIn campaign performance and get optimization recommendations. You can search by job function, seniority, company size, and industry.

11. Perplexity MCP: This gives Claude access to Perplexity’s AI-powered web search. You can conduct real-time market research, competitor monitoring, and fact verification without leaving your workflow.

12. Apify MCP: This enables web scraping and data extraction at scale. You can run pre-built automation bots (“Actors”) to scrape competitor websites, build lead lists, gather pricing intelligence, or monitor content changes automatically.

CLIs: Single-Purpose Tools That Handle the Jobs MCPs Don’t

CLI stands for Command Line Interface. These are standalone tools you run in your terminal that do a specific job and return a result. Where MCPs stay connected to a live service and let Claude interact with it continuously, CLIs are more like single-purpose power tools. You invoke them (still right in Claude Code), they do their thing, and they hand you back the output.

So, you’re probably wondering, “When would you use a CLI over an MCP?” There are a few instances: When the tool doesn’t need a persistent connection. When you want to run a one-off task (scrape a site, process a CSV, push code to GitHub). When the tool exists as a CLI but not yet as an MCP.

Here are 10 CLIs worth knowing, testing out and using.

1. OpenCLI: This turns any website, app, or local binary into a standardized CLI tool. If there’s a marketing platform you use that doesn’t have an MCP or API, OpenCLI can bridge that gap. This is similar to the skill creator skill – here you’re using a CLI to create other CLIs.

2. NotebookLM CLI: This gives you programmatic access to Google NotebookLM. You can upload sources, generate content in multiple formats, and export insights, all from the terminal. If you read one of my previous newsletters on NotebookLM, you know how I feel about this tool.

3. Claude Agent SDK: This lets you build custom agentic workflows in Python or TypeScript. This is how you go from “Claude does what I ask” to “Claude runs my entire content pipeline autonomously.”

4. Anthropic CLI: This lets you interact directly with the Anthropic API from your terminal. It’s good for testing prompts, running batch jobs, and integrating Claude into scripts.

5. Firecrawl CLI: This is for intelligent web scraping with automatic strategy selection and Playwright browser automation. I use this for competitive intelligence and pulling content from competitor sites.

6. DuckDB CLI: This lets you run SQL queries directly on CSV files with zero setup. Export your campaign data from HubSpot, GA4, or LinkedIn Ads, point DuckDB at the file, and get aggregations, filters, and cross-tabulations without spinning up a database.

7. Postiz Agent CLI: You can schedule and publish posts across 28+ social platforms (LinkedIn, X, Instagram, TikTok, YouTube, Reddit, and more) directly from the terminal. Outputs structured JSON for automation workflows.

8. SEO Bhishma CLI: This is a full SEO toolkit with backlink checking, sitemap analysis, bulk indexing verification, Google Search Console data extraction, and redirect mapping. Exports to CSV for reporting.

9. GitHub CLI: This is GitHub’s official command-line tool. Create pull requests, manage issues, and automate repository operations. If your team uses GitHub for documentation, website code, or campaign asset management, this keeps you in the flow.

10. Canva CLI: This is Canva’s official CLI tool for creating and managing Canva apps. You can build custom templates, data connectors, and content publishers directly in Claude Code.

What Comes Next

I think the gap between marketers who use AI as a chatbot and those who build workflows on top of it is going to get wider, fast. The tools covered in this issue (Skills, MCPs, CLIs, Slash Commands) are the building blocks. None of them existed in this form 18 months ago, but I think all of them will be table stakes 18 months from now.

If you’re new to Claude Code CLI, start with an IDE and one or two skills. Then add an MCP for the tool you use most (HubSpot, Notion, Google Drive). And then build from there.

Sure, there’s a learning curve, but it’s shorter than you think. And if you ever get stuck, remember you can always go back to Claude App or even ChatGPT, take a screenshot, and ask for help.

---