Gtm Enablement Engine

GTM启用引擎

一个基于克劳德的面向市场团队的复合智能平台。超越静态内容生成，进入一个自我修复的学习系统，在每笔交易、每次通话和每个季度都变得更加智能。

不是模板的集合。赋能 基础设施 这些化合物。

是什么让这与众不同

传统的启用插件生成内容。这一个 从结果中学习 和 自我治愈:

• 内存层： 每一项技能都从一个持久的知识库中读写。竞争情报、交易模式、ICP数据和团队简介会随着时间的推移而复合。
• 自愈内容： 内容新鲜度持续评分。当竞争对手推出新功能时，系统会自动标记需要更新的每张战斗卡、剧本和通话轨迹。
• 个性化： 材料适应每个代表的经验水平、技能差距和学习风格。新员工得到脚手架；老兵会受到有针对性的轻推。
• 交叉GTM： 涵盖销售、营销、CS、合作伙伴关系和RevOps——因为交易并不存在于一个功能中。
• 预定自动化： 每周的竞争扫描、管道摘要和内容审核都是自动运行的。

安装

claude plugins add gtm-enablement-engine

命令

使用斜线命令调用的显式工作流：

所有命令都有效 独立 （描述您的情况、粘贴笔记或上传数据）并获取 增压的 配备MCP连接器。

技能

核心能力（10项技能）

基础——克劳德在相关时自动使用的领域知识：

智能与个性化（2项技能）

学习层——随着时间的推移，使其他一切变得更加智能：

自愈系统（1项技能）

使您的启用内容保持活跃和最新：

跨GTM支持（5项技能）

功能之间的桥梁——因为交易不存在于一个筒仓中：

预定自动化

设置并忘记让您的支持基础架构运行的工作流：

学习循环是如何运作的

┌──────────────────────────────────────────────────────┐
│                    EVERY INTERACTION                      │
│                                                          │
│  1. READ from memory/  → Get context before acting       │
│  2. DO the task         → Battle card, coaching, etc.     │
│  3. WRITE to memory/   → Store what was learned          │
│  4. CHECK content      → Flag stale assets affected       │
│                                                          │
│  The more you use it, the smarter it gets.               │
│  Quarter 1 outputs ≠ Quarter 4 outputs.                  │
└──────────────────────────────────────────────────────┘

内存架构

memory/
├── product.md          # Your product, features, pricing, roadmap
├── competitors.md      # Competitive landscape, intelligence, trends
├── icp.md              # Ideal customer profile, personas, segments
├── deal-patterns.md    # Win/loss patterns, risk signals, benchmarks
├── objections.md       # Objection library with effectiveness scores
├── team.md             # Team roster, roles, territories
├── content-registry.md # All enablement assets with freshness scores
└── changelog.md        # Audit trail of all memory changes

示例工作流

每周销售经理例行

Monday morning:
1. /pipeline-digest          → See pipeline health, risk alerts, coaching priorities
2. /competitive-pulse        → Catch any competitive moves from last week
3. /rep-dashboard Sarah      → Prep for 1:1 with specific coaching topics
4. /deal-review              → Deep dive on the 2-3 deals that need strategy

新活动启动

Marketing launches a campaign:
1. campaign-to-field triggers → Generates talk tracks, email templates, FAQ
2. content-health updates    → Registers new assets, flags old ones
3. battle-cards checks       → Updates competitive position if campaign changes messaging

自我疗愈在行动

Competitor announces a new feature:
1. competitive-pulse detects → Logged to memory/competitors.md
2. content-health triggers   → Flags all assets referencing that competitor
3. battle-cards re-evaluated → Specific sections needing update identified
4. Remediation plan created  → Prioritized tasks with effort estimates

独立+增压

每个命令和技能都可以在没有任何集成的情况下工作：

MCP集成

看 连接器.md 查看完整的连接器详细信息。

设置

在以下位置创建本地设置文件 gtm-enablement/.claude/settings.local.json:

{
  "name": "Your Name",
  "title": "Sales Enablement Manager",
  "company": "Your Company",
  "product": {
    "name": "Your Product",
    "description": "Brief description of what you sell",
    "pricing_model": "Per seat / Usage / Tier",
    "average_deal_size": 50000,
    "average_sales_cycle_days": 60,
    "value_props": [
      "Key value proposition 1",
      "Key value proposition 2",
      "Key value proposition 3"
    ],
    "competitors": [
      "Competitor A",
      "Competitor B",
      "Competitor C"
    ]
  },
  "icp": {
    "company_size": "50-500 employees",
    "industries": ["SaaS", "Technology"],
    "primary_persona": "VP of Engineering",
    "secondary_personas": ["CTO", "Director of Ops"]
  },
  "methodology": "MEDDIC",
  "team": {
    "aes": 10,
    "sdrs": 5,
    "ses": 3,
    "csms": 4,
    "managers": 2
  },
  "automations": {
    "competitive_pulse": "weekly",
    "pipeline_digest": "weekly",
    "content_audit": "monthly",
    "deal_signals": "daily"
  }
}

如果未配置，插件将以交互方式询问您此信息。

建筑

gtm-enablement-engine/
├── README.md                        # This file
├── CONNECTORS.md                    # Tool-agnostic connector reference
├── LICENSE                          # MIT
├── skills/
│   ├── battle-cards/SKILL.md        # Competitive battle cards
│   ├── objection-handling/SKILL.md  # ACES objection framework
│   ├── discovery-guide/SKILL.md     # Discovery call preparation
│   ├── deal-qualification/SKILL.md  # MEDDIC/BANT/SPICED scoring
│   ├── proposal-builder/SKILL.md    # Proposals and business cases
│   ├── roi-calculator/SKILL.md      # ROI and TCO analysis
│   ├── win-loss-analysis/SKILL.md   # Deal outcome analysis
│   ├── sales-coaching/SKILL.md      # Rep coaching and development
│   ├── playbook-builder/SKILL.md    # Sales playbook creation
│   ├── buyer-persona/SKILL.md       # ICPs and persona development
│   ├── gtm-memory/SKILL.md         # Persistent intelligence layer
│   ├── rep-profile/SKILL.md        # Personalization engine
│   ├── content-health/SKILL.md     # Self-healing content system
│   ├── campaign-to-field/SKILL.md  # Marketing → sales bridge
│   ├── handoff-builder/SKILL.md    # Cross-functional handoffs
│   ├── expansion-playbook/SKILL.md # Upsell/cross-sell/renewal
│   ├── pipeline-intelligence/SKILL.md # Smart pipeline analytics
│   └── partner-enablement/SKILL.md # Partner/channel enablement
├── commands/
│   ├── deal-review.md               # /deal-review
│   ├── enablement-dashboard.md      # /enablement-dashboard
│   ├── onboarding-plan.md           # /onboarding-plan
│   ├── competitive-pulse.md         # /competitive-pulse
│   ├── pipeline-digest.md           # /pipeline-digest
│   ├── content-audit.md             # /content-audit
│   └── rep-dashboard.md             # /rep-dashboard
└── shortcuts/
    ├── weekly-competitive-pulse.md  # Monday competitive scan
    ├── weekly-pipeline-digest.md    # Monday pipeline health
    ├── monthly-content-audit.md     # Monthly freshness scoring
    └── daily-deal-signals.md        # Daily signal detection