Claude Code Hooks for GTM

Claude Code hooks, skills, and subagents for go-to-market teams. Trigger real actions in Slack, Apollo, Lemlist, Notion, Linear, Figma, Google Sheets, and 14+ other tools when Claude finishes work — and use a curated library of GTM skills and outbound agents from inside any session.

---

The three-layer system

┌─────────────────────────────────────────────────────────────┐
│  CLAUDE CODE SESSION                                        │
│                                                             │
│  1. SKILLS  (skills//SKILL.md → ~/.claude/skills/)    │
│     Pre-written instruction modules that tell Claude        │
│     HOW to do GTM work — campaign building, lead            │
│     enrichment, personalization, signal monitoring.         │
│           ↓                                                 │
│  2. AGENTS + COMMANDS (agents/*.md, agents/commands/*.md)   │
│     Subagents (lead-prioritizer, prospect-profiler, etc.)   │
│     and the /outbound-pipeline slash command that chains    │
│     them into a 5-stage outbound workflow.                  │
│           ↓                                                 │
│  3. HOOKS + ORCHESTRATOR (hooks/, orchestrator/)            │
│     settings.json fragments that fire on Claude Code        │
│     lifecycle events (Stop, PostToolUse, SessionStart…)     │
│     and Python handlers that hit real REST APIs.            │
└─────────────────────────────────────────────────────────────┘

Skills = what to do. Agents = who does it. Hooks = when to act. Orchestrator = how to actually send it somewhere.

---

What you get

• 30 hooks across 8 categories (notifications, logging, content, CRM, outbound, design-ops, automation, bootstrap)
• 17 integrations (Slack, Discord, Notion, Apollo, HubSpot, Attio, Airtable, Google Sheets, Lemlist, Instantly, Smartlead, Clay, Typefully, Linear, Figma, Zapier/n8n/Make) — all direct REST, no MCP dependency required for hooks
• 6 GTM skills (campaign-builder, lead-enrichment, personalization-writer, pipeline-reviewer, reply-classifier, signal-monitor)
• 7 subagents + the /outbound-pipeline slash command that orchestrates them
• 17 content prompts for pitch decks, one-pagers, carousels, case studies, ICP cards, proposals
• 5 role-based starter packs (founder, sales, marketing, ops, design) — paste-ready settings files
• One-shot installer, validator, and uninstaller

---

Quickstart

git clone https://github.com/janskuba/go-to-market-orchestrator.git
cd go-to-market-orchestrator
./scripts/install.sh
# Fill in at least SLACK_WEBHOOK_URL in .env
./scripts/validate.sh

Start Claude Code, give it any task, and watch your Slack channel light up when it finishes. Full walkthrough: QUICKSTART.md.

---

How a hook fires

Claude Code event (Stop / PostToolUse / SessionStart / Notification / SessionEnd)
   └──→ ~/.claude/settings.json hook entry
         └──→ bash $CLAUDE_GTM_DIR/orchestrator/run.sh  
               └──→ orchestrator/dispatch.py
                     - reads stdin (Claude's hook payload)
                     - merges  into payload["action"]
                     - exec orchestrator/py/.py
                       └──→ POST to Slack / Apollo / Notion / …

dispatch.py exists so a single contract — payload["action"] — drives every handler. The CLI action overrides any value in stdin; handlers fall back to a sensible default if neither is present.

---

Hook index

Every hook lives in hooks/// with a hook.json snippet and a plain-English README.md.

Team notifications

Reporting and logging

Content production

Prospecting and CRM

Outbound and sequencing

Design ops

Automation bridges

Bootstrap

---

Integration index

Every integration is a Python handler in orchestrator/py/.py. Handlers read JSON from stdin, respect DRY_RUN=1, and call REST APIs directly. No MCP server is required for hooks to work.

---

Skills, agents, and commands

The /outbound-pipeline command chains 5 subagents (signal-scraper → lead-prioritizer → prospect-profiler → hook-writer → sequence-builder) into a single end-to-end workflow with checkpoint files in agents/output/.

To pull the latest skills/agents from upstream repos: ./scripts/sync-skills.sh. The repo ships with vendored copies, so this is optional.

---

Content prompts

The /gtm-content-prompts/ directory contains 17 ready-to-use prompts for pitch decks, one-pagers, LinkedIn carousels, case studies, ICP cards, and proposals. Each prompt suggests a hook to pair it with so the output goes to Notion, Linear, or your tool of choice. See gtm-content-prompts/README.md.

---

Role-based starter packs

Skip assembling hooks one by one. Each file is a complete ~/.claude/settings.json:

Or just run ./scripts/install.sh to install everything.

---

Scripts reference

./scripts/install.sh          # full install (skills + agents + commands + hooks)
./scripts/install.sh --help   # all flags
./scripts/uninstall.sh        # remove everything install.sh added
./scripts/validate.sh         # schema-validate hooks, compile + dry-run handlers, report env state
./scripts/sync-skills.sh      # pull latest skills/agents from upstream repos (optional)
./scripts/install-mcps.sh     # OPTIONAL: register MCP servers for Claude to *use* (not for hooks)

---

Dry-run mode

Set DRY_RUN=1 in .env (or export it) to make every handler print what it would have sent and exit cleanly. Combine with validate.sh for an end-to-end smoke test.

---

FAQ

Do I need to use every tool? No. Each hook is independent. Start with one, add more as needed.

What if I don’t have an API key for X? Use the Zapier/n8n/Make webhook bridges as a fallback. They accept any JSON payload and route it anywhere.

Why no Gmail integration? Gmail OAuth setup is heavier than the other integrations. Use Zapier/Make to bridge to Gmail, or contribute a PR.

How do I verify my setup? ./scripts/validate.sh.

How do I uninstall? ./scripts/uninstall.sh. Backups of your previous settings.json are preserved as settings.json.bak.*.

---

The other two repos

• claude-md-repo — A library of Claude Code skills and templates for GTM workflows.
• outbound-agents — Pre-built Claude Code agents for outbound sales tasks.

./scripts/sync-skills.sh pulls the latest copies into skills/ and agents/. Use --no-upstream if you don’t have access — the repo ships with vendored copies.