gtm-pipeline:company-enrichment
Skill1 starsChanged 5 months agoMITView on GitHub
Enrich a company list with structured data and score against ICP. Phase 1: data enrichment (PhantomBuster SN, Parallel Task Group, SimilarWeb, Firecrawl, SerpAPI). Phase 2: ICP scoring via LLM (icp_score 0-100, optional gate ≥70). Use after company-search and before signal-search. Also triggers on "enrich companies", "ICP scoring", "score companies".
- Reads credentials
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★ 7583% 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-searchSkill
- gtm-pipeline:contact-filterSkill
- gtm-pipeline:demoSkill
- 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
14 rules. About 0 are common, 6 are distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
After company-search — raw list needs domains, revenue, headcount, etc.
- Very specific: line 17
Before signal-search — ICP scoring determines which companies to invest signal credits on
- Very specific: line 18
Before people-search — enriched domains required for most people search providers
- Distinctive: line 33
Add structured company data.
- Distinctive: line 44
Ask the user which provider to use: Default: PB SN Scraper if SN URLs available, otherwise Parallel Task Group.
- Very specific: line 58
Read _shared/phantombuster.md for the full API pattern.
- Very specific: line 86
Always include company_website and linkedin_company_url in the schema.
- Very specific: line 88
Check latest docs via context7 (libraryName: parallel-web).
- Very specific: line 100
Write to csv/intermediate/companies_enriched.csv.
- Distinctive: line 108
Read company rows (status=new, or all unscored)
- Distinctive: line 111
Write score back to CSV
- Distinctive: line 114
LLM: Ask the user which model to use (any LLM with structured output / JSON mode works).
- Very specific: line 151
Write to csv/intermediate/companies_scored.csv with added columns:
- Distinctive: line 156
All original + enrichment columns preserved.
≈ “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
Company Enrichment
Enrich a company list with structured data and score against ICP. Returns enriched CSV + ICP scores.
Read .agents/skills/_shared/conventions.md before executing.
When to Use
- After
company-search— raw list needs domains, revenue, headcount, etc. - Before
signal-search— ICP scoring determines which companies to invest signal credits on - Before
people-search— enriched domains required for most people search providers
Inputs
| Input | Required | Source |
| Company CSV | Yes | Company Search output or user-provided |
| ICP definition | Yes | context/icp.md or user prompt |
Two Phases
Phase 1: Data Enrichment
Add structured company data. Choose provider based on what's available:
| Provider | Data Points | Input needed | Cost | Notes |
| PB SN Scraper | Full SN profile: headcount by dept, growth metrics, revenue range, industry, location | SN company URL | Free (SN account) | Most comprehensive |
| Parallel Task Group | Custom fields via web research | Company name + domain | ~$0.025–0.05/row | Flexible output schema. Ask which processor |
| SimilarWeb via Apify | Monthly traffic, traffic sources | Domain | Apify credits | Actor: curious_coder/similarweb-scraper |
| Firecrawl | Website content, tech stack signals | Domain | Firecrawl credits | Scrape + extract |
| SerpAPI | Domain from company name | Company name | SerpAPI credits | Google search → extract domain |
| Pipe0 company data | TBD — not yet tested | Domain | TBD | Check pipe0 catalog |
Ask the user which provider to use. Default: PB SN Scraper if SN URLs available, otherwise Parallel Task Group.
Phase 2: ICP Scoring
Score enriched companies against client ICP definition.
Phase 1 Execution
PhantomBuster SN Account Scraper
Agent: Sales Navigator Account Scraper (config key: PB_AGENT_SN_ACCOUNT in _shared/local.md, or look up via PhantomBuster MCP)
Read _shared/phantombuster.md for the full API pattern. Use the /phantombuster skill to generate the script:
/phantombuster "Sales Navigator Account Scraper" -- scrape SN company data from <csv_file>, column <sn_url_column>Input: SN company URLs (one per row in CSV) Output per company: name, industry, headcount by dept, location, LinkedIn URL, SN URL, revenue range, growth metrics (6m / 1y / 2y), median tenure
Parallel Task Group (Custom Enrichment)
Endpoint: POST https://api.parallel.ai/v1/tasks
Auth: x-api-key: $PARALLEL_API_KEY
Always ask which processor to use: core, core2x, pro, ultra
Design an output schema matching the data points needed for ICP scoring. Example:
{
"company_website": {"type": "string"},
"linkedin_company_url": {"type": "string"},
"estimated_revenue": {"type": "string"},
"employee_count": {"type": "integer"},
"industry": {"type": "string"},
"founded_year": {"type": "integer"},
"tech_stack_indicators": {"type": "array", "items": {"type": "string"}}
}Always include company_website and linkedin_company_url in the schema.
Check latest docs via context7 (libraryName: parallel-web).
SimilarWeb via Apify
Actor: curious_coder/similarweb-scraper
Env var: APIFY_API_KEY
Input: list of domains Output: monthly visits, traffic sources, bounce rate, pages per visit
Output
Write to csv/intermediate/companies_enriched.csv. Preserve all original columns, add enrichment columns.
Phase 2: ICP Scoring
How It Works
- Read company rows (status=new, or all unscored)
- Load ICP definition from
context/icp.md - LLM scores each company →
icp_score(0–100) +icp_rationale - Write score back to CSV
- Process in batches (~10–20 companies per loop)
LLM: Ask the user which model to use (any LLM with structured output / JSON mode works).
Input Fields Used for Scoring
From the enriched company data:
- name, industry, description, employee count, location, website, LinkedIn URL
- Revenue (min/max), department headcounts (engineering, sales, ops, IT, BD, marketing)
- Growth metrics (6m, 1y, 2y), median tenure, year founded
ICP Scoring Prompt
The LLM receives each company row + the ICP definition and returns a structured score.
Output schema per company:
{
"icp_score": 85,
"icp_rationale": "DACH-based B2B SaaS company in target revenue range. Experiencing rapid growth with lean tech team, indicating clear need for external automation support rather than in-house development."
}Per-Client Customization
- ICP doc: Maintain
context/icp.mdwith the client's ICP definition — industry, size, location, revenue, tech profile, exclusions - Score threshold: Adjust the gate based on selectivity (default: ≥70). The gate is optional — useful for credit savings on downstream steps, not a hard requirement.
Optional Gate for Next Step (Signal Search)
To save credits on downstream signal-search, gate by:
icp_score >= 70websitenot emptytypein [Startup, Scaleup] (if type field available)
Skip the gate if you want to score signals on the full enriched set.
Output
Write to csv/intermediate/companies_scored.csv with added columns:
icp_score, icp_rationale, scoring_statusAll original + enrichment columns preserved.
Full Output
Updated CSV with all columns:
company_name, company_domain, company_linkedin_url,
company_industry, company_hq_location, company_hq_country,
company_employee_count, company_employee_range,
revenue_range, growth_6m, growth_1y, growth_2y,
headcount_engineering, headcount_sales, headcount_operations, headcount_IT,
icp_score, icp_rationale, enrichment_sourceWhat's Missing (To Document)
- Pipe0 company data pipe: test and document endpoint
- Parallel Task Group for company enrichment: test with specific output schema
- SimilarWeb via Apify: document the full actor setup and output field mapping
- LLM API integration patterns for standalone ICP scoring (outside orchestration platforms)
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.

