---
name: moltsets-company-employee-scout
description: Use this skill when the user wants to find people who work at a specific company. Scope the search by company name or exact domain.
---

# Company Employee Scout

Find employees at a target company - scoped by company name or exact domain. Returns ranked contacts with title, seniority, department, and contact data included.

## Triggers

"find people at Stripe", "show me contacts at HubSpot", "show me the team at [Company]", "find contacts at [Company]", "who works at [Company]". Chains company lookup + people search, with optional contact enrichment.

## Chain

```
company name/domain
  to search_companies   (resolve name to domain + firmographics)
  to search_people  (find people, scoped by company_domain or company name)
  to linkedin_to_business_email     (optional - per-URL parallel calls to fill missing business emails)
```

## Set Expectations

Before firing any calls, give the user a brief, dry heads-up. Deadpan over enthusiastic - no filler, no corporate speak.

Facts to work with:
- Search only: 2–3 calls (company lookup + people search), ~10–15 seconds
- With enrichment: search + batch email enrichment for N people, ~20–40 seconds total

## Step 0 - Input Quality Gate

### Company is required - hard stop
If no company name or domain is provided, **stop and ask before running**:

> "Which company do you want to search? I need a company name or domain to scope the results."

Do not attempt a search without a company - results will be meaningless.

For large companies (recognisable enterprises), expect a broad employee mix; paginate with `offset` to pull more pages.

## Step 1 - Resolve company

**Known domain** (e.g. `stripe.com`): skip to Step 2.

**Company name only**: call `MoltSets:search_companies` with `query: "[name]"`. Confirm the correct match with the user before proceeding.

## Step 2 - Search employees

Call `search_people` scoped to the company:
- `company_domain`: the exact company domain (e.g. `"stripe.com"`) - the most precise scope; use this whenever you have it
- `company`: the company name (e.g. `"Stripe"`, `"HubSpot"`) - use when you only have a name
- `limit`: default 10, max 25 per page
- `offset`: 0, 25, 50, … to paginate across a large employee base

You can also narrow within the company using people filters: `seniority` (Intern, Entry, Senior, Manager, Director, VP, Head, C Suite, Owner, Partner), `department` or `functional_area` (Operations, Sales, Information Technology, Education, Engineering, Finance, Medical & Health, Marketing, Human Resources, Design, Consulting, Legal - use one), and `country`. Add these when the user wants a specific slice (e.g. "VPs at Stripe", "sales team at HubSpot"). `query` can also free-text a person's name or role.

## Step 3 - Present results

Each record returns `full_name`, `title`, `seniority`, `country`, `headline`, `linkedin_url`, `business_email`, company data, and `_score`. Present:

| Name | Title | Seniority | LinkedIn | Business email |
|---|---|---|---|---|

Default 10 per page. For large companies, paginate with `offset` to gather more records. Ask if user wants more pages or wants to enrich with contact data.

## Step 4 - Optional enrichment

`business_email` is often already present in the results - call that out. If user wants the gaps filled or phone numbers: collect LinkedIn URLs for the rows that need it and call `linkedin_to_business_email` once per URL (single `linkedin_url` each), fired in parallel. Phone uses `linkedin_to_mobile_phone` with a `linkedin_urls` array.

Always do a credit check first: "Found X people, Y missing a business email. Enriching = Y × [cost] = ~XXX credits. Proceed?"

## Edge cases

- Company name in `company`/`query` is a soft signal - results may include people with that company mentioned in their headline/title, not just employees. Prefer `company_domain` for precision
- Seniority, department, and country are accepted as request filters - use them to narrow to a role slice within the company. Title also returns as a response field for ranking
- For large companies, paginate with `offset` to pull more pages