From gtm-skills
Builds targeted company lists for outbound campaigns using Extruct via decision tree: lookalikes from seeds, semantic/deep searches matching ICPs.
npx claudepluginhub extruct-ai/gtm-skills --plugin gtm-skillsThis skill uses the workspace's default tool permissions.
Build company lists using Extruct, guided by a decision tree. Reads from the company context file for ICP and seed companies.
Builds targeted company and contact lists using Common Room Prospector for net-new prospects or existing accounts with signals. Clarifies object types and refines iteratively.
Finds, enriches, and qualifies companies and people matching ICP criteria from playbooks, segments, and personas. Outputs prospect lists with fit reasoning and sales approaches.
Generates ranked tables of enriched decision-maker leads (emails/phones) from ICP descriptions using Apollo company/people searches and bulk enrichment.
Share bugs, ideas, or general feedback.
Build company lists using Extruct, guided by a decision tree. Reads from the company context file for ICP and seed companies.
This skill delegates all Extruct API calls to the extruct-api skill.
For all Extruct API operations, read and follow the instructions in skills/extruct-api/SKILL.md.
All company search, lookalike search, deep search, table creation, row uploads, and enrichment runs are handled by the extruct-api skill. This skill focuses on what to search for and why — the extruct-api skill handles the how.
Before running any queries, determine the right approach:
Have a seed company from win cases or context file?
YES → Lookalike Search (pass seed domain)
NO ↓
New vertical, need broad exploration?
YES → Semantic Search (3-5 queries from different angles)
NO ↓
Need qualification against specific criteria?
YES → Deep Search (criteria-scored async research)
NO ↓
Need maximum coverage?
YES → Combine Search + Deep Search (~15% overlap expected)
Read the company context file if it exists:
claude-code-gtm/context/{company}_context.md
Extract:
Also check for a hypothesis set at claude-code-gtm/context/{vertical-slug}/hypothesis_set.md. If it exists, use the Search angle field from each hypothesis to design search queries — these are pre-defined query suggestions tailored to each pain point.
Use when you have a seed company (from win cases, existing customers, or user input). Delegate to the extruct-api skill to run a lookalike search with the seed domain.
When to use:
Tips:
Delegate to the extruct-api skill to run semantic company search queries.
Query strategy:
Delegate to the extruct-api skill to create and run deep search tasks.
Query strategy:
After collecting results, delegate to the extruct-api skill to create a company table and upload domains. Extruct auto-enriches each domain with a Company Profile.
After the list-enrichment skill adds data points to this list, consider re-running list building using enrichment insights as Deep Search criteria. For example:
| Campaign stage | Target list size | Method |
|---|---|---|
| Exploration | 50-100 | Search (2-3 queries) |
| First campaign | 200-500 | Search (5 queries) + Deep Search |
| Scaling | 500-2000 | Deep Search (high result count) + multiple Search |