What problem does it solve? Writing valid Clay advanced search queries requires knowing the query grammar, field names, enum values, and operator semantics. This Skill translates plain-language audience descriptions, job postings, briefs, and ICP notes into correct Clay search queries without manual syntax lookup. ## Core Features & Use Cases - Natural-language to query conversion: Turn descriptions of leads, companies, candidates, or job postings into valid select from Clay search queries. - Entity and filter reasoning: Automatically choose the right result entity (people, companies, jobs) and express cross-entity filters like experiences.any(...), people.exists(...), and jobs.exists(...). - Guardrails and transparency: Apply defaults for tenure, job status, and low-coverage fields, and clearly report any criteria the dataset cannot capture. - Use Case: A sales rep pastes an ICP note like "VP Sales leaders at B2B SaaS companies in Germany with 50-500 employees" and receives a ready-to-paste Clay search query for https://clay.com. ## Quick Start Ask the assistant to write a Clay search query for the audience or job postings you want to find, describing your filters in plain language.
