Update to AgentSource

{
  "description": "Build a targeted list of companies or people from a plain-language description of the audience: job titles, seniority, department, industry, company size, location, tech stack, buying-intent topics, or recent company events such as funding or a new office. Use for requests like 'find 50 CISOs in Texas', 'companies using Snowflake in the UK', 'build a target account list', 'companies that opened a new office in California', or 'heads of demand gen at fintechs'. Not for a single named company or person (use enrich-company or enrich-contact), for counting a market without pulling rows (use market-sizing), or for sending outreach.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 325
    }
  ],
  "name": "list-builder",
  "skill_md_contents": "---\nname: list-builder\ndescription: \"Build a targeted list of companies or people from a plain-language description of the audience: job titles, seniority, department, industry, company size, location, tech stack, buying-intent topics, or recent company events such as funding or a new office. Use for requests like 'find 50 CISOs in Texas', 'companies using Snowflake in the UK', 'build a target account list', 'companies that opened a new office in California', or 'heads of demand gen at fintechs'. Not for a single named company or person (use enrich-company or enrich-contact), for counting a market without pulling rows (use market-sizing), or for sending outreach.\"\n---\n\n# List Builder\n\nTurn a plain-language audience description into a list of companies or people. Results come back in full, one page at a time.\n\n## Connector rules\n\nUse only the AgentSource tools in your tool list. Each tool's live description and input schema are authoritative; if this skill disagrees with a tool, follow the tool.\n\n- **`tool_reasoning`** is required on every call: the user's original request in their exact words (up to 2000 characters), reused unchanged across chained calls for the same task. Never replace it with a per-step rationale or add personal data the user did not write.\n- **Sessions:** reuse `session_id` from the previous response while continuing the same request; omit it to start a new request. Never invent one.\n- **Chaining by ID:** pass `business_id` and `prospect_id` values from `match-business`, `match-prospects` or `fetch-entities` results. Do not re-match entities that a fetch already returned.\n- **`autocomplete` first**, one concept per call, for `linkedin_category`, `naics_category`, `company_tech_stack_tech`, `job_title`, `interests`, `skills`, `business_intent_topics`, and US `city_region`. Use the returned values as-is. Use ISO codes directly for countries (`US`) and regions (`US-CA`).\n- **What you see:** every tool returns full results inline. `fetch-entities` returns up to `page_size` rows per call (at most 500) and a `next_cursor` for the next page; `fetch-entities-statistics` returns aggregates over every match.\n- **Credits:** every data call uses credits on the user's AgentSource account. Request only the rows and enrichments the task needs, count with `fetch-entities-statistics` before a large pull, and confirm with the user before fetching more than 100 rows or enriching contact details for more than 50 people.\n- **Limits per call:** `match-business` 50 companies, `match-prospects` 40 people, `enrich-business` and `enrich-prospects` 50 IDs, `fetch-businesses-events` 20 companies. Name several enrichment types in one `enrichments` list rather than one call each.\n- **Presenting:** show returned records in a table with the fields that matter for the task. Never mention session IDs or internal table names.\n- **Event details:** if a fetch used the `events` filter and the user did not already ask for event details, ask before calling `fetch-businesses-events` or `fetch-prospects-events`.\n- **Lists:** work from lists pasted in chat or text from attached files, in batches that respect the limits above.\n\n## Parse the request\n\nPull these out of the user's message:\n\n- **Entity type:** `prospects` if any person attribute is named (title, seniority, department, skills); `businesses` only when the request is about companies with no people.\n- **Roles:** titles, seniority, department.\n- **Company traits:** industry, size, revenue, company age, public or private.\n- **Geography:** country, state or region, US city. Note whether it describes the person or the company.\n- **Signals:** tech stack, buying-intent topics, recent events (funding, new office, hiring, M&A) with a 30-90 day window.\n- **Count:** use the exact number requested; default 30. Set `page_size` to the count, up to 500; for more, page with `next_cursor`. Confirm before pulling more than 100 rows, because each row uses credits.\n- **Extras:** contact details (emails, phones), people per company.\n\nExamples: \"100 VP Engineering at Series B SaaS in the US that use Snowflake\", \"50 CISOs based in TX with 5+ years of experience\", \"500 companies that opened a new office in CA in the last 90 days\", \"50 CFOs at public manufacturers that raised funding in the last 90 days\".\n\n## Workflow\n\n1. **Ask what is missing, once.** Skip any question the user already answered.\n   - *Location (prospects only):* if \"in <place>\" could mean where the person lives or where the company is headquartered, ask which, or both. Clear wording such as \"companies in Germany\" or \"prospects based in New York\" needs no question.\n   - *Contact details (prospects only):* unless the user already said what contact data they want, ask using the options in the live `fetch-entities` description, then set `has_contact_details` to match. It filters availability only; it does not return the values.\n2. **Resolve values.** Run `autocomplete` for every controlled-vocabulary filter you will use. Use ISO codes directly for countries (`US`) and regions (`US-CA`), and the schema enums for company size, revenue, age, job level and job department.\n3. **Build the filters.**\n   - **Roles:** broad seniority or department asks (\"engineering VPs\") use `job_level` plus `job_department` only. A specific title uses `job_title` (from autocomplete); for executive titles add `job_level`. Title filters are loose, so seniority keeps them tight.\n   - **One industry taxonomy:** `linkedin_category` or `naics_category`, never both. Start with LinkedIn. Switch to NAICS only if the best LinkedIn match is a parent industry that would pull in many unrelated companies.\n   - **One location level per side:** `company_country_code` or `company_region_country_code`; `prospect_country_code` or `prospect_region_country_code`.\n   - **Experience:** \"5+ years of experience\" means `total_experience_months` with `gte: 60`; time in the current role uses `current_role_months`.\n   - **Buying intent:** \"who needs\", \"is looking for\", \"interested in\" a product means `business_intent_topics`, with values from autocomplete.\n   - **Events:** `events` works for businesses only, with `values` (for example `new_office` for \"opened a new office\", `new_funding_round`, `new_product`, `merger_and_acquisitions`) and `last_occurrence` of 30-90 days. It selects companies that had the event; it does not add event columns. A completed office-opening event does not establish future office demand. For office-seeking intent, resolve an appropriate intent topic or explain that the requested intent cannot be expressed; do not substitute the event silently.\n   - **Ambiguous words** (\"designers\", \"security\", \"consulting\"): offer specific sub-categories and an \"all relevant\" option, and do not silently pick the broadest.\n4. **Fetch once.** Combine everything into a single `fetch-entities` call. Set `max_per_company` only if the user gave a number. Do not call `match-business` or `match-prospects` afterwards, because the IDs are already in the result.\n5. **Enrich only on request,** passing the returned IDs (up to 50 per call). Contact enrichment (`enrich-prospects` with `contacts`) follows the user's contact answer: set `parameters.contact_types` to match the channel they chose. For company details on prospect results, use `enrich-business` with their `business_id` values.\n6. **Event details:** if the fetch used `events` and the user did not already ask for event details, ask before running `fetch-businesses-events` or `fetch-prospects-events`.\n7. **Present** the rows in the format below.\n\n## Reply\n\n- **Results Found:** `[key qualifier] [entity type]`, with the rows returned and `total_results` if the response gives it.\n- **Results table:** the rows, with the columns that matter for the request.\n- **Criteria applied:** a short bullet list of the filters that landed. Say plainly if a request was approximated or could not be expressed.\n- **Next steps:** if `total_results` exceeds the rows returned, offer the next page and say it uses credits; never page without a yes. Add one or two concrete refinements: tighten or widen a bucket, switch location level, add a recent-event filter, pull the people at these companies, add an enrichment.\n\n## Limitations\n\n- Company size and revenue are buckets, not exact figures, and results cannot be sorted by them.\n- No metro-area filter: use a US `city_region` or a state or country code.\n- No sub-department job-function filter: use the department plus a title.\n- No Inc 5000 or Fortune ranking filter; approximate with size, revenue and the public-company flag.\n- Contact data arrives only through enrichment. `has_contact_details` filters availability.\n- Results cannot be sorted; `fetch-entities` returns matches in its own order.\n- Department is empty for many cross-functional senior roles (Chief X Officer, President, Founder); group them as \"Unattributed\".\n"
}