gtm-pipeline:demo
Skill1 starsChanged 5 months agoMITView on GitHub
Generate a demo lead list of ~10 enriched contacts with personalized message examples. Use when a demo is requested, a webhook prompt describes a target audience, or someone asks to "create a demo for [client]". Enforces demo mode restrictions (email only, no phone, ~10 contacts). Chains people-search → people-enrichment → message generation.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- keinsaasforever/gtm-pipeline-skillsedited, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- keinsaasforever/gtm-pipeline-skills★ 7522% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- article-writingSkill
- brand-voiceSkill
- deep-researchSkill
- email-personalizationSkill
- exa-searchSkill
- gtm-pipeline:company-enrichmentSkill
- gtm-pipeline:company-searchSkill
- gtm-pipeline:contact-filterSkill
- gtm-pipeline:outreachSkill
- gtm-pipeline:people-enrichmentSkill
- gtm-pipeline:people-searchSkill
- gtm-pipeline:pipelineSkill
- gtm-pipeline:setupSkill
- gtm-pipeline:signal-searchSkill
- investor-materialsSkill
- investor-outreachSkill
- lead-intelligenceSkill
- marketing-campaignSkill
- market-researchSkill
- research-opsSkill
- social-graph-rankerSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 10 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 44
Do NOT proceed to search until ICP is clear enough to build a meaningful filter.
- Very specific: line 52
Create the {client-slug}-gtm/ directory structure as defined in conventions.md.
- Distinctive: line 58
Use the people-search skill to find ~10–15 contacts.
- Distinctive: line 61
Prefer BetterContact Lead Finder or FullEnrich Finder — both return LinkedIn URLs directly, needed for email enrichment
- Distinctive: line 62
If no company list (persona-based prompt), use Parallel FindAll or BC Search
- Distinctive: line 71
Follow the people-search execution protocol: sandbox → test → review → run.
- Distinctive: line 77
Run contact-filter on the 10–15 contacts found.
- Distinctive: line 90
Run people-enrichment on the filtered contacts.
- Distinctive: line 114
Every message must follow: Hook → Bridge → Offer → Soft CTA
- Distinctive: line 123
Total: 320–450 characters: No blank line after greeting.
- Very specific: line 141
Write a client-specific system prompt (save to prompts/message_prompt.md)
- Distinctive: line 144
If issues found, refine the system prompt and regenerate
- Very specific: line 196
Stripe payment (full list): After successful payment, run the full pipeline via the pipeline skill.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Demo
Generate a demo lead list of ~10 enriched contacts with personalized message examples, triggered by a webhook prompt.
Read .agents/skills/_shared/conventions.md before executing.
When to Use
- Webhook trigger: user submits a free demo form describing their target audience
- Goal: prove the AI agent writes authentic, non-generic outreach using real leads
- Scope: ~10 contacts, enriched with LinkedIn + email, 2–4 message examples
Demo Restrictions
- No phone enrichment — email only
- ~10 contacts (request 10–15, expect enrichment drop-off)
- Message generation is optional but recommended
Step 1 — Parse the Prompt & Ask Discovery Questions
The webhook prompt describes the user's target audience. Before running anything, extract or ask for:
Must have:
- What do you sell / offer?
- Who is your ideal customer? (industry, role, company size, location)
- What's your value proposition?
- What tone? (formal vs. casual, examples if possible)
- Is this for recruiting OR selling to customers?
If not in the prompt, infer or ask:
- Target job titles
- Target location
- Target company size or type
Do NOT proceed to search until ICP is clear enough to build a meaningful filter.
Save ICP to: {client-slug}-gtm/context/icp.md
Step 2 — Create Working Directory
Create the {client-slug}-gtm/ directory structure as defined in conventions.md. Write the ICP definition to context/icp.md.
Step 3 — People Search (10 contacts)
Use the people-search skill to find ~10–15 contacts.
Provider selection for demo:
- Prefer BetterContact Lead Finder or FullEnrich Finder — both return LinkedIn URLs directly, needed for email enrichment
- If no company list (persona-based prompt), use Parallel FindAll or BC Search
Key fields to collect:
full_name, first_name, last_name,
job_title, company_name, company_domain,
linkedin_profile_url, locationFollow the people-search execution protocol: sandbox → test → review → run.
Step 4 — Contact Filter (ICP Ranking)
Run contact-filter on the 10–15 contacts found. Even small batches benefit from ICP ranking — it ensures the enrichment step focuses on the best-fit contacts.
- Applies job tier, industry tier, location tier, and company size classification
- Rejects hard non-ICP contacts
- Ranks passed contacts by priority
- Output:
csv/intermediate/contacts_filtered.csv
For demos: use a relaxed hard-reject threshold (allow tiers 1–5 to pass), prioritize ranking over filtering.
Step 5 — People Enrichment (Email Only)
Run people-enrichment on the filtered contacts. Demo mode: email only, no phone.
Recommended flow:
- FullEnrich v2 (email) — all contacts
- Pipe0 waterfall — for FE misses only
Additional enrichment for message personalization (if available):
- LinkedIn headline and summary (from LinkedIn scrape via PhantomBuster)
- Recent LinkedIn posts (2–3 per contact) — significantly improves message quality
Minimum viable fields for message generation:
name, job_title, company_name, linkedin_profile_url,
headline (optional), summary (optional), recent_posts (optional)Step 6 — Generate Message Examples
Generate 2–4 sample messages before committing to the full batch.
Message Structure
Every message must follow: Hook → Bridge → Offer → Soft CTA
| Part | Purpose | Length |
| Hook | Reference something specific to this person (post, career move, company signal) | 1 sentence |
| Bridge | Connect their situation to your offer | 1 sentence |
| Offer | What you provide, clearly stated | 1 sentence |
| CTA | Soft ask — not "let's schedule a call" | 1 sentence |
Total: 320–450 characters. No blank line after greeting. Paragraphs separated by single line break.
Quality Rules
Must have:
- Specific hook (post reference OR career insight — not generic)
- Clear value proposition
- Natural, conversational tone
- Soft CTA
Must avoid:
- Repeating profile info they already know ("You work as X at Y")
- Generic observations ("impressive background", "I noticed you're in [industry]")
- Corporate jargon or buzzwords
- Pushy CTAs ("Let's schedule a call this week")
Generation Process
- Write a client-specific system prompt (save to
prompts/message_prompt.md) - Generate 2–4 samples — include contacts with and without LinkedIn posts
- Review against quality checklist above
- If issues found, refine the system prompt and regenerate
- Only batch generate once quality is approved
System Prompt Template (key sections)
- Client context: what they sell, who they target, their value prop, tone
- Forbidden rules: no profile repetition, no generic flattery
- Message structure: hook → bridge → offer → CTA
- Hook examples: with posts / without posts
- Character limit: 320–450Step 7 — Output
Deliver:
- CSV at
csv/output/contacts_enriched.csv: lead data + generated messages - Google Sheet (optional): formatted for easy review
Output CSV Columns
name, first_name, last_name, location, headline, summary,
linkedin_url, email, email_status,
company_name, job_title,
post_1_content, post_1_date,
post_2_content, post_2_date,
generated_message, char_count, has_postsMessages saved separately to csv/output/messages.csv.
Quality Checklist (Before Delivering)
- Messages feel personal, not templated
- No profile info repetition
- Clear value proposition in every message
- Proper formatting (line breaks, character count 320–450)
- Hook differs between contacts (no copy-paste structure)
- All data fields populated correctly
- Client-specific context incorporated
Trigger Context
Webhook (demo form): Free demo trigger — user describes their ICP in a text prompt. Run this skill with ~10 contacts and 2–4 message samples.
Stripe payment (full list): After successful payment, run the full pipeline via the pipeline skill. See pipeline skill for orchestration.
What's Missing (To Document)
- LinkedIn post scraping via PhantomBuster API (launch, poll, download)
- Automated webhook integration (currently manual trigger)
- Stripe payment trigger integration
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

