gtm-engineering

Automate GTM engineering workflows for enrichment, pipeline automation, and CRM integration.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GTM teams often waste time on manual, repetitive engineering tasks. This skill provides a structured approach to enrichment, pipeline automation, signal monitoring, and outbound infrastructure so teams can focus on strategic work.

Core Features & Use Cases

  • GTM play design and selection for enrichment, pipeline automation, signal monitoring, and outbound workflows.
  • Waterfall enrichment architecture and CRM integration to power multi-channel campaigns.
  • End-to-end pipeline orchestration across data sources, tools, and delivery channels.

Quick Start

Design a GTM pipeline by selecting a play type, mapping signals, and wiring enrichment sources to your CRM.

Frequently Asked Questions about gtm-engineering

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

FAQPage Schema
How do I automate GTM engineering workflows for pipeline orchestration?▼

You can automate GTM engineering workflows by selecting modular play types for pipeline orchestration, mapping data signals, and wiring enrichment sources directly to your CRM for multi-channel delivery.

What is waterfall enrichment and how does it work with CRM integration?▼

Waterfall enrichment is an architecture that sequentially processes data across multiple sources to maximize completeness. It integrates directly with your CRM to power multi-channel outbound campaigns.

Can I use this for signal monitoring and outbound infrastructure automation?▼

Yes, signal monitoring and outbound infrastructure are core play types supported. The system applies structured guardrails and error handling to automate these workflows across cross-tool integrations.

What is the best way to design a repeatable go-to-market pipeline?▼

The best way to design a repeatable go-to-market pipeline is by selecting a specific play type, mapping your target signals, and configuring end-to-end orchestration across your data sources and delivery channels.

Does this approach support multi-channel orchestration across different tools?▼

Yes, multi-channel orchestration is supported through cross-tool integration. The system manages end-to-end pipeline automation across diverse data sources, tools, and delivery channels with robust error handling.

How do I handle errors and guardrails when automating outbound workflows?▼

Automated outbound workflows include robust error handling and clear guardrails by design. These features ensure your pipeline orchestration and cross-tool integrations execute reliably without manual intervention.