Skip to content
Back to search

gtm-plugins

MarketplaceWorks with Claude CodeGitHub

Skills for GTM teams

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/manojbajaj95--claude-gtm-plugin/badge.svg)](/listings/manojbajaj95--claude-gtm-plugin)

HTML

<a href="/listings/manojbajaj95--claude-gtm-plugin"><img src="/api/listings/manojbajaj95--claude-gtm-plugin/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Claude Cowork

Install from the plugin marketplace at [claude.com/plugins](https://claude.com/plugins). Search for **GTM Skills**, click install, and the plugin is immediately available in your Cowork sessions.

Claude Code

# Add the marketplace
claude plugin marketplace add manojbajaj95/claude-gtm-plugin

# Install the plugin
claude plugin install gtm-skills@gtm-plugins

Skills CLI

Use [npx skills](https://github.com/vercel-labs/skills) to install skills directly into any project:

# Install all skills
npx skills add manojbajaj95/claude-gtm-plugin

# Install specific skills
npx skills add manojbajaj95/claude-gtm-plugin --skill seo-and-aeo-strategy

# List available skills
npx skills add manojbajaj95/claude-gtm-plugin --list

Clone and Load Locally

git clone https://github.com/manojbajaj95/claude-gtm-plugin.git

Then open Claude Code in the cloned directory — the plugin loads automatically.

Git Submodule

Add as a submodule for easy updates:

git submodule add https://github.com/manojbajaj95/claude-gtm-plugin.git .agents/claude-gtm-plugin

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 17 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "$schema": "https://code.claude.com/schemas/marketplace.json",
  3. "name": "gtm-plugins",
  4. "owner": {
  5. "name": "mbajaj"
  6. },
  7. "metadata": {
  8. "description": "Go-to-Market skills for Claude — SEO, content, sales, growth, and more"
  9. },
  10. "plugins": [
  11. {
  12. "name": "gtm-skills",
  13. "source": "./",
  14. "description": "Go-to-market skills for Claude — 54 skills covering SEO, content, social, outbound, sales, growth, analytics, strategy, ads, and CRM"
  15. }
  16. ]
  17. }
README.md · README · 209 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # GTM Skills
  2. Go-to-market skills that turn Claude into a GTM specialist. 54 skills across SEO & AI search, content, outbound, sales, growth, analytics, strategy, ads, social, and CRM. Built for [Claude Code](https://claude.com/product/claude-code), also compatible with [Claude Cowork](https://claude.com/product/cowork) and any agent that supports the [Agent Skills spec](https://agentskills.io).
  3. ## Why This Plugin
  4. Most AI assistants give generic marketing advice. This plugin gives Claude the frameworks, workflows, and domain knowledge of an experienced GTM team — so it can write copy in your voice, audit your SEO like a consultant, plan launches like a PMM, and build outbound sequences like an SDR.
  5. This repo is designed to become a working **marketing-team workspace**, not just a directory of prompts. The bootstrap skill interviews you once about your brand, audience, voice, channels, operating cadence, and success metrics, then generates a structured project folder that every skill reads before doing anything.
  6. The result: Claude doesn't just know marketing — it knows *your* marketing, keeps context in durable files, routes new learnings to the right place, and helps a team manage strategy, content, campaigns, and assets from one workspace.
  7. ## Installation
  8. ### Claude Cowork
  9. Install from the plugin marketplace at [claude.com/plugins](https://claude.com/plugins). Search for **GTM Skills**, click install, and the plugin is immediately available in your Cowork sessions.
  10. ### Claude Code
  11. ```bash
  12. # Add the marketplace
  13. claude plugin marketplace add manojbajaj95/claude-gtm-plugin
  14. # Install the plugin
  15. claude plugin install gtm-skills@gtm-plugins
  16. ```
  17. ### Skills CLI
  18. Use [npx skills](https://github.com/vercel-labs/skills) to install skills directly into any project:
  19. ```bash
  20. # Install all skills
  21. npx skills add manojbajaj95/claude-gtm-plugin
  22. # Install specific skills
  23. npx skills add manojbajaj95/claude-gtm-plugin --skill seo-and-aeo-strategy
  24. # List available skills
  25. npx skills add manojbajaj95/claude-gtm-plugin --list
  26. ```
  27. ### Clone and Load Locally
  28. ```bash
  29. git clone https://github.com/manojbajaj95/claude-gtm-plugin.git
  30. ```
  31. Then open Claude Code in the cloned directory — the plugin loads automatically.
  32. ### Git Submodule
  33. Add as a submodule for easy updates:
  34. ```bash
  35. git submodule add https://github.com/manojbajaj95/claude-gtm-plugin.git .agents/claude-gtm-plugin
  36. ```
  37. ## Getting Started
  38. ### Bootstrap Your Project
  39. Ask Claude to bootstrap your project. Claude runs an agency-style onboarding interview — asking about your brand, audience, voice, channels, team workflow, tools, and goals — then generates a structured project:
  40. ```
  41. your-project/
  42. ├── CLAUDE.md # AI instructions: repo structure, naming, workflow, routing
  43. ├── PROGRESS.md # Session progress, blockers, next steps, future opportunities
  44. ├── about/
  45. │ └── me.md # Personal voice, writing style, personality, biography
  46. ├── strategy/
  47. │ └── brand.md # Brand positioning, messaging, audience, competitors, voice
  48. ├── content/
  49. │ ├── ideas.md # Content idea backlog
  50. │ ├── calendar.md # Publishing schedule
  51. │ ├── linkedin/
  52. │ │ ├── drafts/ # Work-in-progress posts
  53. │ │ └── published/ # Archive of published posts
  54. │ ├── twitter/
  55. │ │ ├── drafts/
  56. │ │ └── published/
  57. │ ├── reddit/
  58. │ │ ├── drafts/
  59. │ │ └── published/
  60. │ ├── blog/
  61. │ │ ├── drafts/
  62. │ │ └── published/
  63. │ └── email/
  64. │ ├── drafts/
  65. │ └── published/
  66. └── assets/
  67. ├── logos/ # Logo files
  68. └── brand/ # Brand visual references
  69. ```
  70. | Path | What it captures |
  71. |---|---|
  72. | `CLAUDE.md` | AI instructions — repo structure, what to read first, naming conventions, content workflow |
  73. | `PROGRESS.md` | Session progress — completed tasks, blocked tasks, next steps, future opportunities |
  74. | `about/me.md` | Personal voice — your writing style, quirks, references, personality |
  75. | `strategy/brand.md` | Brand identity — positioning, messaging, audience, competitors, voice guidelines |
  76. | `content/` | Working content engine — ideas, calendar, drafts and published content per platform |
  77. | `assets/` | Reusable visual assets — logos, brand files, visual references |
  78. Content files follow the naming convention `YYYY-MM-DD_short-topic-slug.md`. Drafts live in `content/[platform]/drafts/` and move to `published/` once live.
  79. Once bootstrapped, every skill reads the relevant context before doing anything and updates `PROGRESS.md` each session. Claude works in your voice, for your brand, from day one. Ask Claude to bootstrap again to redo onboarding or refresh the workspace when positioning, channels, or team workflows change.
  80. ### Using Skills
  81. Skills activate automatically when Claude detects a matching task. Just describe what you need in natural language:
  82. ```
  83. "Audit the SEO on my landing page"
  84. → Activates seo-and-aeo-strategy
  85. "Write a cold email sequence for enterprise CTOs"
  86. → Activates outbound-email-strategy + lead-generation-and-demand
  87. "Plan a Product Hunt launch for next month"
  88. → Activates product-hunt-launch + go-to-market-strategy
  89. "Create a 5-email onboarding sequence"
  90. → Activates marketing-automation + user-onboarding
  91. "Help me figure out pricing for my SaaS"
  92. → Activates pricing-strategy
  93. "Write a LinkedIn post about our new feature"
  94. → Activates linkedin + copywriting-core
  95. ```
  96. Skills cross-reference each other. Ask Claude to write a cold email and it pulls from your brand positioning (`strategy/brand.md`), your personal voice (`about/me.md`), and your ICP — not from a generic template.
  97. ## How It Works
  98. ```
  99. claude-gtm-plugin/
  100. ├── .claude-plugin/ # Plugin manifest
  101. ├── skills/ # All 54 skills in one flat directory
  102. │ ├── bootstrap/
  103. │ ├── seo-and-aeo-strategy/
  104. │ ├── linkedin/
  105. │ ├── copywriting-core/
  106. │ └── ... (54 total)
  107. └── scripts/ # Build and validation
  108. ```
  109. **Skills** are markdown files with YAML frontmatter that give Claude specialized knowledge for specific tasks. Claude activates them automatically when it detects a matching task — or you can invoke them directly.
  110. Skills reference each other and build on the project structure created by the bootstrap skill. Each skill checks `strategy/brand.md`, `about/me.md`, `content/ideas.md`, and `content/calendar.md` as appropriate before asking questions. Ask Claude to write a cold email and it pulls from your brand positioning, your voice, and your ICP — not from a generic template.
  111. This repo keeps its existing skill names while adapting best-practice task boundaries from [coreyhaines31/marketingskills](https://github.com/coreyhaines31/marketingskills). See [docs/upstream-marketingskills-mapping.md](docs/upstream-marketingskills-mapping.md) for the local mapping and [docs/skill-principles-review.md](docs/skill-principles-review.md) for the one-by-one skill review.
  112. ## Skills
  113. **54 skills** — all in one plugin, no sub-plugins to juggle.
  114. See [ALL_SKILLS.md](ALL_SKILLS.md) for the complete list.
  115. ## Routing Rules
  116. As you work with Claude, it routes new information to the right file automatically:
  117. - Brand info (positioning, messaging, audience insights) → `strategy/brand.md`
  118. - Personal info (writing preferences, quirks, reference examples) → `about/me.md`
  119. - New content ideas → `content/ideas.md`
  120. - Draft content → `content/[platform]/drafts/`
  121. - Published content → `content/[platform]/published/`
  122. ## Validation
  123. Skills follow the [Agent Skills specification](https://agentskills.io/specification). Run the validator to check all skills:
  124. ```bash
  125. ./validate-skills.sh
  126. ```
  127. This checks frontmatter fields, naming conventions, description quality, and file structure against the official spec. See the [official reference validator](https://github.com/agentskills/agentskills/tree/main/skills-ref) for the canonical implementation.
  128. ## Contributing
  129. **We're actively looking for contributors!** Whether you're a marketer, growth hacker, SEO specialist, or just someone who uses Claude for GTM work — your expertise can help make these skills better for everyone.
  130. ### Ways to contribute
  131. - **New skills** — Have a GTM workflow that Claude should know? Write it as a skill.
  132. - **Improve existing skills** — Better frameworks, updated best practices, sharper prompts.
  133. - **Fix incorrect advice** — Found a skill giving bad recommendations? [Open a bug report](https://github.com/manojbajaj95/claude-gtm-plugin/issues/new?template=bug_report.yml).
  134. - **Add references** — Templates, examples, or supporting material for existing skills.
  135. - **Documentation** — Improve READMEs, add examples, clarify instructions.
  136. ### How to contribute
  137. 1. Fork the repo
  138. 2. Create a branch (`git checkout -b my-skill`)
  139. 3. Make your changes — each skill lives in `skills/<skill-name>/SKILL.md`
  140. 4. Ensure valid YAML frontmatter with at least `name` and `description`
  141. 5. Run `./validate-skills.sh` to catch issues
  142. 6. Submit a PR
  143. ### Reporting issues
  144. If a skill gives incorrect advice, fails to activate, or doesn't use your brand context properly — [file an issue](https://github.com/manojbajaj95/claude-gtm-plugin/issues/new?template=bug_report.yml). The more detail you include (skill name, what you asked, what happened vs. what you expected), the faster we can fix it.
  145. ## License
  146. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.