gtm-infra

Design and configure GTM infrastructure stacks with data flows and runbooks.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jforksy/claude-skills --skill gtm-infra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gtm-infra
Source: https://github.com/jforksy/claude-skills/tree/main/gtm-infra
Command: npx skills add https://github.com/jforksy/claude-skills --skill gtm-infra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to designing and configuring a GTM tech stack, including tool selection, integrations, data flows, and governance. It helps startups avoid tool sprawl and data silos by defining minimal viable stacks and repeatable runbooks.

Core Features & Use Cases

  • Minimum viable GTM stack design: identify core tools and integrations to support prospecting, outbound, content, and analytics.
  • Runbooks and configuration management: documented setup and hand-off for faster onboarding.
  • Data flow architecture: maps data between tools (CRM, enrichment, sequencing, analytics) with run-ready workflows.
  • Use Case: early-stage startup implementing GTM Infra for a handful of deals, with HubSpot, Clay, Instantly, Calendly, GA4.

Quick Start

Follow these steps to begin: establish the core stack (HubSpot + Clay), wire essential integrations (Instantly, Calendly), and create the initial stack configuration and runbooks in data/gtm/infra.

Frequently Asked Questions about gtm-infra

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a GTM tech stack for an early-stage startup?

Designing a GTM tech stack involves selecting core tools like HubSpot and Clay to support prospecting and outbound, then wiring integrations to establish clear data flows and documented configuration runbooks for minimal viable infrastructure.

What is a minimum viable stack for go-to-market infrastructure?

A minimum viable GTM stack combines a core CRM like HubSpot with enrichment tools like Clay, plus sequencers such as Instantly and scheduling tools like Calendly, ensuring tracked data flows across prospecting, content, and analytics.

How do I map data flows between HubSpot, Clay, and Instantly?

Mapping data flows between HubSpot, Clay, and Instantly requires defining integration patterns that sync CRM records with outbound sequencing platforms, documented within configuration runbooks to ensure reproducible data architecture.

Can I use GA4 and Fathom for GTM analytics integration?

Yes, GA4 and Fathom can be integrated into GTM infrastructure to capture content and web analytics, mapping that data back to the core stack to provide a complete view of prospecting and outbound performance.

What's the best way to document GTM configuration and credential handling?

The best way to document GTM configuration is by creating structured runbooks within your data directories, capturing tool selection, integration patterns, and credential handling to enable reproducible deployment and faster onboarding.

Why do I need runbooks for my GTM infrastructure?

Runbooks are needed for GTM infrastructure to prevent tool sprawl and data silos, providing documented setup steps and hand-off procedures that ensure your tech stack configuration remains reproducible and governable.