build-list
Build a list of contacts or companies matching specific criteria. Describe what you're looking for in natural language and get a structured, tabular list you can export. Supports filtering by title, seniority, department, industry, company size, location, tech stack, growth rate, and more. Outputs a clean table artifact.
What this skill does
# Build List Build a targeted list of contacts or companies from ZoomInfo and output as a structured table. ## Input The user will describe what they want via `$ARGUMENTS`. Examples: - "CTOs at Series B+ startups in SF with 50-200 employees" - "VP of Sales at healthcare companies using Salesforce with 500+ employees" - "All SaaS companies in EMEA with $10M-$50M revenue" - "Directors of Engineering at companies similar to Datadog" - "Marketing leaders at Fortune 500 companies in financial services" The user may also specify: - How many results they want (default: 25) - Whether they want contacts, companies, or both - Specific fields to include in the output ## Workflow 1. **Determine list type**: Is the user asking for contacts, companies, or both? Default to contacts if they mention titles/roles, companies if they mention firmographics only. 2. **Parse criteria** from natural language into structured filters: - Job titles, management levels, departments, job functions → contact filters - Industry, employee count, revenue, geography, tech stack, company type → company filters - Growth rate, funding, rankings → company filters 3. **Resolve all filter values** using `lookup` before searching. This is critical — do NOT guess values. For every filter you plan to use, call `lookup` with the corresponding field name to get the valid values and use the returned `id` values in your search parameters. 4. **Execute the search**: - For **contacts**: Use `search_contacts` with all resolved filters. Sort by `-contactAccuracyScore`. Request up to 100 results. - For **companies**: Use `search_companies` with all resolved filters. Sort by `-employeeCount` or `-revenue`. Request up to 100 results. - For **both**: Search companies first, then search contacts at the top results. 5. **Enrich top results** if the search returns limited detail: - Use `enrich_contacts` (batch of 10) or `enrich_companies` (batch of 10) on the top results to fill in emails, phones, and other details. 6. **Output as a clean table artifact.** Create a markdown or CSV artifact the user can copy or export. ## Output Format ### Search Criteria Applied Show the user exactly what filters were used so they can verify: | Filter | Value | |--------|-------| | Management Level | Vice President | | Industry | Computer Software | | Employee Count | 51-100, 101-250 | | Metro Region | San Francisco-Oakland-Hayward, CA | | ... | ... | ### Contact List (if contact search) | # | Name | Title | Company | Email | Direct Phone | Accuracy | Location | |---|------|-------|---------|-------|-------------|----------|----------| | 1 | | | | | | | | | 2 | | | | | | | | ### Company List (if company search) | # | Company | Industry | Employees | Revenue | HQ Location | Website | ZoomInfo ID | |---|---------|----------|-----------|---------|-------------|---------|-------------| | 1 | | | | | | | | | 2 | | | | | | | | ### List Summary - **Total results found**: X (showing top Y) - **Filters applied**: [summary] - **Average accuracy score**: X (contacts only) - **Data quality**: Flag any concerns (low accuracy, stale records) ### Refinement Options If the list is too broad or too narrow, suggest specific filter adjustments: - "Add `revenue` filter to narrow from 847 to ~200 results" - "Remove metro region filter to expand from 12 to ~150 results" - "Try adjacent industries: Information Technology Services, Internet" If the user wants to iterate, they can re-run with adjusted criteria. Suggest the exact modified command.
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".