agentleFS
vivekkhimanivivekkhimani/gtm-tools-template/.agents/skills/gtm-demo/SKILL.md

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

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
  1. Distinctive:

    Do NOT proceed to search until ICP is clear enough to build a meaningful filter.

    line 44
  2. Very specific:

    Create the {client-slug}-gtm/ directory structure as defined in conventions.md.

    line 52
  3. Distinctive:

    Use the people-search skill to find ~10–15 contacts.

    line 58
  4. Distinctive:

    Prefer BetterContact Lead Finder or FullEnrich Finder — both return LinkedIn URLs directly, needed for email enrichment

    line 61
  5. Distinctive:

    If no company list (persona-based prompt), use Parallel FindAll or BC Search

    line 62
  6. Distinctive:

    Follow the people-search execution protocol: sandbox → test → review → run.

    line 71
  7. Distinctive:

    Run contact-filter on the 10–15 contacts found.

    line 77
  8. Distinctive:

    Run people-enrichment on the filtered contacts.

    line 90
  9. Distinctive:

    Every message must follow: Hook → Bridge → Offer → Soft CTA

    line 114
  10. Distinctive:

    Total: 320–450 characters: No blank line after greeting.

    line 123
  11. Very specific:

    Write a client-specific system prompt (save to prompts/message_prompt.md)

    line 141
  12. Distinctive:

    If issues found, refine the system prompt and regenerate

    line 144
  13. Very specific:

    Stripe payment (full list): After successful payment, run the full pipeline via the pipeline skill.

    line 196

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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, location

Follow 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:

  1. FullEnrich v2 (email) — all contacts
  2. 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

PartPurposeLength
HookReference something specific to this person (post, career move, company signal)1 sentence
BridgeConnect their situation to your offer1 sentence
OfferWhat you provide, clearly stated1 sentence
CTASoft 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

  1. Write a client-specific system prompt (save to prompts/message_prompt.md)
  2. Generate 2–4 samples — include contacts with and without LinkedIn posts
  3. Review against quality checklist above
  4. If issues found, refine the system prompt and regenerate
  5. 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–450

Step 7 — Output

Deliver:

  1. CSV at csv/output/contacts_enriched.csv: lead data + generated messages
  2. 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_posts

Messages 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.