gtm-pipeline:demo

Generates a demo lead list of enriched contacts with personalized outreach messages and an HTML card deck.

69|8|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/keinsaasforever/gtm-pipeline-skills --skill gtm-pipeline-demo-keinsaasforever
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gtm-pipeline:demo
Source: https://github.com/keinsaasforever/gtm-pipeline-skills/tree/main/skills/gtm-demo
Command: npx skills add https://github.com/keinsaasforever/gtm-pipeline-skills --skill gtm-pipeline-demo-keinsaasforever

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? Producing a convincing demo of an AI-driven lead generation pipeline normally requires manually finding contacts, enriching them, and writing sample outreach. This Skill automates that entire demo workflow from a free-text ICP prompt, delivering roughly 10 enriched contacts with ready-to-send message drafts. ## Core Features & Use Cases - End-to-end demo pipeline: Chains people-search, contact-filter, and people-enrichment (email only) to build a ~10-contact lead list from a webhook or user prompt describing a target audience. - Optional buying-signal pass: A --with-signals flag runs signal-search over the unique companies and merges scored intent signals back into contacts for sharper message hooks. - Message generation with quality gates: Produces 2-4 sample messages following a hook-bridge-offer-CTA structure (320-450 characters), with a client-specific system prompt and review checklist. - White-label HTML card deck: Fills a parameterized deck_template.html with one collapsible card per contact, signal source links, deliverability badges, an embedded CSV download, and a booking CTA, followed by programmatic self-QA. - Use Case: A prospect submits a website demo form describing their ideal customer; the skill runs headless via claude -p, infers the ICP, enriches ~10 contacts, and outputs a sanitized CSV, branded deck, and result.json without blocking on questions. ## Quick Start Run the demo skill with a prompt describing your target audience, for example: "/gtm-pipeline:demo create a demo for a SaaS company selling to German logistics firms with 50-200 employees".

Frequently Asked Questions about gtm-pipeline:demo

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

FAQPage Schema
How do I generate a demo lead list from an ICP description?

Invoke the demo skill with a free-text prompt describing the offering and target audience. It parses the ICP, runs people-search for 10-15 contacts, filters and enriches them with verified emails, then generates 2-4 sample outreach messages and an HTML card deck.

How do I run the demo skill headless from a webhook?

Trigger it via the Claude Code CLI with claude -p and the demo command, using acceptEdits permission mode. In headless mode it never asks questions, records inferred assumptions in context/icp.md, runs end-to-end, and writes a result.json summary.

Can the demo include buying intent signals for contacts?

Yes, pass the --with-signals flag or request signal-anchored messages. The skill runs signal-search over the unique companies, merges scored signals back into the contacts CSV, and uses the highest-scored signal as the message hook. It adds under $0.50 for a 10-contact demo.

What are the limitations of demo mode?

Demo mode restricts output to roughly 10 contacts, enriches email only with no phone numbers, and keeps signal search off by default. It is designed to prove outreach quality, not to deliver a full production lead list, which requires the paid pipeline skill.

Why does the demo deck reject third-party provider names?

The rendered deck is white-label and client-facing, so no enrichment vendor, search, or scrape provider may appear in the copy. Signal source links must cite the original publication such as a press release or careers page, and programmatic QA greps the output to enforce this.