Systems Lab

Agent skill

list-builder-router

activeSelf-containedInstructions only258 words

Filed under Prospecting and list building.

From timyakubson/cold-outbound-grokbot-repo · 27 skill entries · 3 · pushed 2026-10-04

What it does when it runs

Automated analysis of the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.

Keys and connectors you must supply
None found.
Hosts it reaches
No third-party host appears in the skill or its bundled files.
Tool permissions it declares
No allowed-tools in the frontmatter. It only issues instructions, so there is nothing to bound.
Actions present in the files
None. Instructions only.

Ask about list-builder-router

Opens your assistant with this page's verified links already in the prompt.

Is this safe to install?ClaudeChatGPT
Adapt it to my stackClaudeChatGPT
What else do I need for it to workClaudeChatGPT
Rather ask a human? Talk to Cheetah

Install it

View source on GitHub ↗
git clone --depth 1 --filter=blob:none --sparse https://github.com/timyakubson/cold-outbound-grokbot-repo.git /tmp/cold-outbound-grokbot-repo
git -C /tmp/cold-outbound-grokbot-repo sparse-checkout set "stage-4-company-tam/list-builder-router"
mkdir -p ~/.claude/skills/list-builder-router
cp -R "/tmp/cold-outbound-grokbot-repo/stage-4-company-tam/list-builder-router/." ~/.claude/skills/list-builder-router/

Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗

The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.

The skill

Source on GitHub ↗

Reproduced in full from timyakubson/cold-outbound-grokbot-repo/blob/26fedfe6f14f477887097004f6a41371e1860562/stage-4-company-tam/list-builder-router/SKILL.md, which is licensed MIT (repository). 258 words, 4 headings.

list-builder-router

Segment-aware router for Step 3 (Company TAM) and Step 4 (People TAM). Reads the segment type off client-profile.yaml (produced by icp-onboarding) and picks the right data source instead of running one fixed provider for every ICP.

Routing table

Segment / needProviderWhy
Company-level lookalikes, LinkedIn data, firmographic depthCompanyEnrichSimilar Companies API for TAM expansion; wins on coverage and field depth in independent benchmarks
Person-level database, quick lookalike expansion during outreachLemlistBuilt-in 600M+ B2B database + AI Lookalike Finder (LinkedIn URL in, similar profiles out), used inline while sending, not as the primary list-build step
E-commerce companiesStoreLeadsPurpose-built for identifying and enriching e-commerce storefronts
Local / brick-and-mortar business leadsOutscraperGoogle Maps / local business data at volume
Everything else / no clean provider matchExa.aiGeneral-purpose web search and retrieval, catch-all fallback

Behavior

  1. Read segment_type from client-profile.yaml.
  2. Match against the table above.
  3. If no confident match, fall back to Exa.ai and flag the record for manual review.
  4. Hand the resulting company/people list to list-builder / list-expander / disco-like for enrichment and lookalike expansion as normal.

Status

Net-new skill, not present in the upstream repo this was forked from. Built for the Grok Bot GTM course; CompanyEnrich and Lemlist integrations are sponsor placements, both chosen because they do real, distinct work in the pipeline (see routing table above), not interchangeable mentions.

Other skills for the same job

Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.

Need help setting it up?

This page tells you what list-builder-router does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.

Book a call →

The directory stays free. There is nothing gated behind this.