· 1 observation
Technical updates · 1
Package or technical metadata updated
View technical comparison →Explorium.ai v8.1.2
Find leads & B2B contact data
From the developer
This plugin does not sell products or process payments. Vibe Prospecting is a B2B data service used through the user's existing account.
Find 30 VPs of Engineering based in Texas at SaaS companies.
Developer declarations; not independently tested. Listing last checked Nov 19, 2026. Package observed Nov 19, 2026.
From the marketplace listing
Vibe Prospecting brings live B2B data into ChatGPT for prospecting, lead research, and data enrichment. It draws on a database of 150M+ companies and 800M+ professional contacts aggregated from 50+ sources, so you can build lead lists, research accounts, and fill in missing contact data without leaving the conversation. Search for companies. Describe your ideal customer profile in plain language and filter by industry (including LinkedIn industry, NAICS, and SIC classifications), employee count, revenue range, location, funding stage, and the technologies a company uses. Results come back as structured lists you can refine, rank, and export. Find the right people. Search professional contacts by job title, seniority, department, location, skills, and work history. Look up a specific person by name and company, or map the decision-makers across a target account, including org structure and reporting lines, to plan multi-threaded outreach. Get contact details. Retrieve business emails and phone numbers for the contacts you find, with verification status included, so outreach lists are ready to use. Fill gaps in partial records, for example a name and company with no email. Verify email addresses you already have before a send, and flag records that need replacing. Track buying signals. See which companies raised funding, announced news, grew headcount, opened relevant job listings, or had key people change roles. Use these events to time outreach, score leads, and prioritize accounts. Enrich your existing records. Paste or upload a list of companies or contacts and append firmographics, technographics, contact details, and recent signals. The app matches records to the right company or person, flags duplicates, and returns a clean table you can export to CSV for your CRM, ATS, or outreach tools. Who it's for. Sales teams and SDRs building qualified pipeline. Recruiters sourcing candidates by role, skills, and location. RevOps and marketing teams segmenting accounts, sizing markets, and improving CRM data quality. It also supports market sizing and TAM analysis, lead scoring, territory planning, and account-based marketing list building. Try prompts like: "Find US SaaS companies with 100 to 1,000 employees that use HubSpot." "Identify VP-level decision-makers at these accounts and get verified work emails." "Enrich this list with industry, employee count, revenue, and tech stack." "Which of these companies raised funding or grew headcount in the last 6 months?" "Find backend engineers in Austin with fintech experience and get their profiles." "Build a target account list for my ICP and rank it by fit." "Map the sales leadership org chart at this company." "Verify the emails in this list and flag the risky ones." "Estimate how many US companies match this ICP." "Write a personalized cold email opener for each contact based on their company's recent news." Vibe Prospecting is built on Explorium's B2B data platform. Data is retrieved live at query time, not from a static export, so results reflect current company and contact information.
Language: English · Automatically detected from descriptions.
· 1 observation
Package or technical metadata updated
View technical comparison →· 3 observations
Is template instance added: “false”. Full description changed from “Vibe Prospecting brings live B2B data into ChatGPT for prospecting, lead research, and data enrichment. It draws on a database of 150M+ companies and 800M+...” to “Vibe Prospecting: Find leads & B2B contact data.”. Capabilities updated; open the...
View comparison →Is template instance added: “false”. Full description changed from “Vibe Prospecting brings live B2B data into ChatGPT for prospecting, lead research, and data enrichment. It draws on a database of 150M+ companies and 800M+...” to “Vibe Prospecting: Find leads & B2B contact data.”. Capabilities updated; open the...
View comparison →Package or technical metadata updated
View technical comparison →· 3 observations
Plugin name changed from “AI Vibe Prospecting” to “Vibe Prospecting”. App-6947c583d8308191844af6213ceabe16 updated; open the comparison for details. Vibeprospecting updated; open the comparison for details. Publisher keywords: 33 added. 3 more changes in the comparison.
View comparison →Plugin name changed from “AI Vibe Prospecting” to “Vibe Prospecting”. App-6947c583d8308191844af6213ceabe16 updated; open the comparison for details. Vibeprospecting updated; open the comparison for details. Publisher keywords: 33 added. 2 more changes in the comparison.
View comparison →Package or technical metadata updated
View technical comparison →Finding similar plugins… Results will appear here automatically.
Browse plugins →---
name: account-contacts
description: "Find and rank the right people at one target company: a contact shortlist for outbound, or a buying-committee map showing economic buyers, technical evaluators, influencers and coverage gaps. Use for 'get the HR leadership at miro.com', 'who are the decision-makers at Acme', 'map the buying committee at Globex', 'contacts at Stripe for a security pitch', 'who owns this at the account'. Not for finding people across many companies (use list-builder) or for looking up a named person (use enrich-contact)."
---
# Account Contacts
Pull the right people at one company, check how reachable they are, and say who to engage first.
## Connector rules
Use only the Vibe Prospecting 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.
- **`tool_reasoning`** is required on every call: one short sentence (≤200 characters) that paraphrases what the user wants. No earlier conversation, contact details, or other personal data.
- **Chaining:** copy `session_id` and `table_name` from the previous tool response; never invent either. After an enrich or events step, use the new `table_name`.
- **`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.
- **What you can see:** `match-business` and `match-prospects` return complete results; fetch, enrich, and events tools return only a masked preview, so never quote values from it; `fetch-entities-statistics` returns aggregates; `show-sample` reveals up to 5 full rows.
- **Finish with `show-sample`**, once per final `table_name`, then reply. Match-only and statistics-only work does not need it. The widget displays the sample rows, so do not repeat them as a table; use them for your analysis. If `display_status` is `masked`, say the full rows could not be revealed.
- **Export** only after the user explicitly confirms, because it consumes credits. Show the returned download `url`. Never mention table names or session IDs to the user.
- **Uploads:** you cannot upload files to Vibe Prospecting. Pasted lists and text from attached files are fine to use. If the user asks how to upload a list, point them to the Vibe Prospecting Hub: https://app.vibeprospecting.ai/lists
## Input
- **Company** (required): a domain (preferred) or a name.
- **Use case:** prospecting (default), deal acceleration, or renewal and expansion. For a buying-committee request, add the purpose: deal stage, who is already engaged, who is missing, and any hypothesis ("find the economic buyer").
- **Focus (optional):** a function (HR, security, finance, RevOps) or seniority (C-level, VP and above, Director and above), and how many people (default 25, up to 100).
If only a bare company is given, ask once what the contacts are for; if the user declines, build a general prospecting shortlist and say so.
## Workflow
1. **Match the company** with `match-business`. A big brand that resolves to 1-50 employees under "Corporate Managing Offices" probably hit a shell entity, so retry with the other domain. If several companies match, show the top 2-3 (industry, size, HQ) and ask.
2. **Turn the use case into a persona blueprint** before fetching:
- *Prospecting:* broad coverage of the functions that would buy, weighted to Director, VP and C-level.
- *Deal acceleration:* the economic buyer, a technical evaluator, procurement, and one Director-level champion candidate.
- *Renewal or expansion:* current product-owner functions plus an executive sponsor, including Manager and Director levels.
Apply any function or seniority the user named, and say which roles that dropped.
3. **Contact preference.** If the user did not say what contact data they want, ask using the options in the live `fetch-entities` description and set `has_contact_dPreview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
--- name: account-research description: "Build a purpose-driven intelligence brief on one target company: firmographics, funding, hiring and workforce trends, tech stack, recent business events, and peers. Use for pre-call research, renewal or QBR prep, competitive evaluation, and outbound targeting, for example 'research stripe.com for outbound to finance leaders', 'account brief on Snowflake', 'profile this company before my call'. Not for a quick lookup of one data point (use enrich-company), a comparison of several rivals (use competitor-research), or a meeting agenda with attendee profiles (use meeting-prep)." --- # Account Research A brief on one company, framed around why the user needs it. ## Connector rules Use only the Vibe Prospecting 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. - **`tool_reasoning`** is required on every call: one short sentence (≤200 characters) that paraphrases what the user wants. No earlier conversation, contact details, or other personal data. - **Chaining:** copy `session_id` and `table_name` from the previous tool response; never invent either. After an enrich or events step, use the new `table_name`. - **`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. - **What you can see:** `match-business` and `match-prospects` return complete results; fetch, enrich, and events tools return only a masked preview, so never quote values from it; `fetch-entities-statistics` returns aggregates; `show-sample` reveals up to 5 full rows. - **Finish with `show-sample`**, once per final `table_name`, then reply. Match-only and statistics-only work does not need it. The widget displays the sample rows, so do not repeat them as a table; use them for your analysis. If `display_status` is `masked`, say the full rows could not be revealed. - **Export** only after the user explicitly confirms, because it consumes credits. Show the returned download `url`. Never mention table names or session IDs to the user. - **Uploads:** you cannot upload files to Vibe Prospecting. Pasted lists and text from attached files are fine to use. If the user asks how to upload a list, point them to the Vibe Prospecting Hub: https://app.vibeprospecting.ai/lists ## Input - **Company** (required): a name or domain. - **Purpose** (strongly recommended): one sentence on why the brief is needed and what decision it supports (renewal risk, competitive evaluation against Acme, outbound to finance leaders). If it is missing, ask once; if the user declines, produce general account intelligence and say so. ## Workflow 1. **Anchor on purpose.** Restate it in one sentence and pick 2-4 themes (for renewal risk: workforce changes, executive moves, competing vendors, expansion signals). Themes decide which enrichments to add and how to filter peers. 2. **Match the company** with `match-business` using name and domain. A major brand that resolves to 1-50 employees in "Corporate Managing Offices" is likely a shell entity; retry with the other domain or the plain name. If there is no confident match, ask the user. 3. **Enrich in tiers**, at most 3 types per `enrich-business` call, each on the latest `table_name`: - *Always:* `enrich-business-firmographics`, `enrich-business-company-hierarchies`, `enrich-business-funding-and-acquisitions`, `enrich-business-workforce-trends`, `enrich-business-linkedin-posts`. - *By purpose:* competitive evaluation adds technographics, webstack and competitive-landscape; renewal or QBR adds company-ratings, challenges and strategic-insights; outbound adds website-changes and website-keywords (keywords tied to the user's offering); investor or M&A adds financial-metrics (needs a `date`). - *Skip* the rest unless the purpose calls for th
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
---
name: clean-data
description: "Tidy a pasted list of companies or contacts before matching or enrichment: normalize company names, domains, countries and emails, flag invalid rows with a reason, match each row to Vibe Prospecting records, and remove duplicates that resolve to the same company or person. Use for 'clean this list', 'match these companies to domains', 'dedupe these contacts', 'which of these emails are valid', 'prep this list for enrichment'. Works on lists pasted in chat, up to roughly 100 rows. Not for building a new list (use list-builder)."
---
# Clean Data
Standardize and check a pasted list, then match it so duplicates collapse onto real company or person records. Nothing is deleted: every row stays, with a status and reason.
## Connector rules
Use only the Vibe Prospecting 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.
- **`tool_reasoning`** is required on every call: one short sentence (≤200 characters) that paraphrases what the user wants. No earlier conversation, contact details, or other personal data.
- **Chaining:** copy `session_id` and `table_name` from the previous tool response; never invent either. After an enrich or events step, use the new `table_name`.
- **`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.
- **What you can see:** `match-business` and `match-prospects` return complete results; fetch, enrich, and events tools return only a masked preview, so never quote values from it; `fetch-entities-statistics` returns aggregates; `show-sample` reveals up to 5 full rows.
- **Finish with `show-sample`**, once per final `table_name`, then reply. Match-only and statistics-only work does not need it. The widget displays the sample rows, so do not repeat them as a table; use them for your analysis. If `display_status` is `masked`, say the full rows could not be revealed.
- **Export** only after the user explicitly confirms, because it consumes credits. Show the returned download `url`. Never mention table names or session IDs to the user.
- **Uploads:** you cannot upload files to Vibe Prospecting. Pasted lists and text from attached files are fine to use. If the user asks how to upload a list, point them to the Vibe Prospecting Hub: https://app.vibeprospecting.ai/lists
## Input
A list of companies or contacts pasted in chat, or the text of an attached file. Roughly 100 rows is the practical limit in one conversation; for more, work in batches. Note which column is the company name, domain, email, LinkedIn URL, phone or country; ask only if it is unclear. For a very large file, suggest the user clean it in a spreadsheet first.
## Workflow
1. **Profile the input.** Report row count, fill rate for each field, and obvious problems: placeholder text ("N/A", "none", "-"), pasted addresses in the name field, many spellings of one country, free-email providers, and role addresses.
2. **Standardize,** keeping the raw value beside the normalized one:
- *Company name:* trim, collapse spaces, remove stray punctuation, and drop a trailing legal suffix (Inc, LLC, Ltd, GmbH, S.A.) for matching only.
- *Domain:* strip the protocol and `www`, keep the registrable domain, lowercase. Flag free-email domains separately.
- *Country:* convert to ISO two-letter codes (`United States` → `US`, `UK` → `GB`, `Deutschland` → `DE`).
- *Email:* trim and lowercase.
- *LinkedIn:* keep the full profile URL.
3. **Validate** each field and tag the row; never delete one:
- *Email:* syntax, role addresses (`info@`, `sales@`, `noreply@`, `support@`), well-known free or disposable providers. You cannot check deliverability or mail servers, so say that valid means well-formed.
- *Domain:* looks like a real domain, no IP address or Preview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
--- name: competitor-research description: "Compare two to four rival companies side by side: size, funding, hiring trends, tech stack, recent strategic moves, and overlap with the user's target customers, with a short battlecard per competitor. Use for 'compare Gong and Chorus', 'size up our competitors', 'competitive landscape for X', 'battlecard for renewal'. Not for a deep brief on one company (use account-research) or for finding lookalike companies (use lookalike-accounts)." --- # Competitor Research A dated, fact-led comparison of a few named rivals. ## Connector rules Use only the Vibe Prospecting 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. - **`tool_reasoning`** is required on every call: one short sentence (≤200 characters) that paraphrases what the user wants. No earlier conversation, contact details, or other personal data. - **Chaining:** copy `session_id` and `table_name` from the previous tool response; never invent either. After an enrich or events step, use the new `table_name`. - **`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. - **What you can see:** `match-business` and `match-prospects` return complete results; fetch, enrich, and events tools return only a masked preview, so never quote values from it; `fetch-entities-statistics` returns aggregates; `show-sample` reveals up to 5 full rows. - **Finish with `show-sample`**, once per final `table_name`, then reply. Match-only and statistics-only work does not need it. The widget displays the sample rows, so do not repeat them as a table; use them for your analysis. If `display_status` is `masked`, say the full rows could not be revealed. - **Export** only after the user explicitly confirms, because it consumes credits. Show the returned download `url`. Never mention table names or session IDs to the user. - **Uploads:** you cannot upload files to Vibe Prospecting. Pasted lists and text from attached files are fine to use. If the user asks how to upload a list, point them to the Vibe Prospecting Hub: https://app.vibeprospecting.ai/lists ## Input - **Competitors** (required): 2-4 names or domains. Four is the practical limit, because `show-sample` reveals 5 rows. - **Purpose** (ask once if missing): battlecard, board update, win-loss prep, renewal. - Optional: priority angles (pricing pressure, AI roadmap, a region), the user's target customers (to judge overlap), and hypotheses to confirm or contradict. ## Workflow 1. **Anchor.** Restate the purpose, angles and hypotheses in 1-2 sentences. 2. **Match all competitors** in one `match-business` call, with name and domain where available. Check each for the shell-entity pattern (a big brand showing 1-50 employees under "Corporate Managing Offices") and retry with the alternate domain. Drop and flag any that do not resolve confidently; do not proceed with the wrong company. 3. **Enrich** the matched table, at most 3 types per call, each on the latest `table_name`: firmographics, funding-and-acquisitions, workforce-trends, technographics, competitive-landscape, strategic-insights, challenges, company-ratings, linkedin-posts. Prioritize by the user's angles, and say which were skipped. 4. **Fetch events** with `fetch-businesses-events` for the last 90 days. Keep launches (`new_product`), funding (`new_funding_round`), `merger_and_acquisitions`, `new_office` and `closing_office`, `cost_cutting`, partnerships, and notable department hiring or cuts. Before using an event, check that it names the competitor. 5. **Show** with `show-sample` on the enriched table and on the events table. 6. **Judge overlap** per competitor (High, Partial, None) against the user's stated target customers, using firmographics. If none were given, write "N
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
--- name: enrich-company description: "Look up one company, or a pasted list of up to 50 names or domains, and add firmographics, tech stack, funding and acquisitions, workforce and hiring trends, ratings, company hierarchy, website changes, or LinkedIn posts. Use for 'enrich this company', 'what does acme.com use', 'how big is Stripe', 'funding history for Asana', 'add industry and headcount to this list of domains'. Not for finding new companies (use list-builder) or a full multi-section brief (use account-research)." --- # Enrich Company Resolve named companies to Vibe Prospecting records, then add the data the user asked for. ## Connector rules Use only the Vibe Prospecting 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. - **`tool_reasoning`** is required on every call: one short sentence (≤200 characters) that paraphrases what the user wants. No earlier conversation, contact details, or other personal data. - **Chaining:** copy `session_id` and `table_name` from the previous tool response; never invent either. After an enrich or events step, use the new `table_name`. - **`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. - **What you can see:** `match-business` and `match-prospects` return complete results; fetch, enrich, and events tools return only a masked preview, so never quote values from it; `fetch-entities-statistics` returns aggregates; `show-sample` reveals up to 5 full rows. - **Finish with `show-sample`**, once per final `table_name`, then reply. Match-only and statistics-only work does not need it. The widget displays the sample rows, so do not repeat them as a table; use them for your analysis. If `display_status` is `masked`, say the full rows could not be revealed. - **Export** only after the user explicitly confirms, because it consumes credits. Show the returned download `url`. Never mention table names or session IDs to the user. - **Uploads:** you cannot upload files to Vibe Prospecting. Pasted lists and text from attached files are fine to use. If the user asks how to upload a list, point them to the Vibe Prospecting Hub: https://app.vibeprospecting.ai/lists ## Input One or more company names or domains, typed or pasted (up to 50 per match call). A name plus a domain matches best. Optional: which kinds of data the user wants. ## Workflow 1. **Match.** Call `match-business` with each company's `name` and/or `domain`. The result is complete, so read it directly. 2. **Check the match.** A well-known brand that resolves to 1-50 employees in a "Corporate Managing Offices" category probably landed on a registered-agent shell. Retry with the alternate domain or the plain company name. The match has no confidence score, so when the candidates look ambiguous, ask the user instead of guessing. Report unmatched rows and do not substitute other companies. 3. **Choose enrichments** from what the user asked for. With no preference, use firmographics plus technographics. | Need | Enrichment | |---|---| | Name, description, size, revenue, location, industry | `enrich-business-firmographics` | | Tech stack | `enrich-business-technographics` | | Web infrastructure | `enrich-business-webstack` | | Rounds, investors, IPO, acquisitions | `enrich-business-funding-and-acquisitions` | | Headcount and department trends | `enrich-business-workforce-trends` | | Employee-satisfaction ratings | `enrich-business-company-ratings` | | Parent, subsidiaries, org tree | `enrich-business-company-hierarchies` | | Public-company financials | `enrich-business-financial-metrics` (needs `parameters.date`) | | Keywords on their website | `enrich-business-website-keywords` (needs `parameters.keywords`) | | Site content changes
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
---
name: enrich-contact
description: "Look up one person or a small pasted list of people and return their professional profile and contact details: work email, phone, LinkedIn, title, seniority, department, work history, and recent job changes. Identify people by email, LinkedIn URL, phone number, or full name plus company. Use for 'find the email for Jane Smith at Acme', 'enrich this contact', 'who is this person', 'background on these attendees'. Not for finding new people by role (use list-builder or account-contacts) or for drafting outreach."
---
# Enrich Contact
Resolve people to Vibe Prospecting records, then add the profile and contact data the user asked for.
## Connector rules
Use only the Vibe Prospecting 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.
- **`tool_reasoning`** is required on every call: one short sentence (≤200 characters) that paraphrases what the user wants. No earlier conversation, contact details, or other personal data.
- **Chaining:** copy `session_id` and `table_name` from the previous tool response; never invent either. After an enrich or events step, use the new `table_name`.
- **`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.
- **What you can see:** `match-business` and `match-prospects` return complete results; fetch, enrich, and events tools return only a masked preview, so never quote values from it; `fetch-entities-statistics` returns aggregates; `show-sample` reveals up to 5 full rows.
- **Finish with `show-sample`**, once per final `table_name`, then reply. Match-only and statistics-only work does not need it. The widget displays the sample rows, so do not repeat them as a table; use them for your analysis. If `display_status` is `masked`, say the full rows could not be revealed.
- **Export** only after the user explicitly confirms, because it consumes credits. Show the returned download `url`. Never mention table names or session IDs to the user.
- **Uploads:** you cannot upload files to Vibe Prospecting. Pasted lists and text from attached files are fine to use. If the user asks how to upload a list, point them to the Vibe Prospecting Hub: https://app.vibeprospecting.ai/lists
## Input
For each person, one of: an email, a LinkedIn URL, a phone number, or a full name with a company name or domain. A name without a company cannot be matched. Up to 40 people per `match-prospects` call. Optional: whether the user wants contact details, a profile, or career changes.
## Workflow
1. **Pick the strongest identifier** for each person: email, then LinkedIn URL, then phone, then name plus company. Do not fan out several strategies for one person. If the user gave a role instead of a name ("the CFO at Asana"), do not match on the title; use `match-business` to get the company, then `fetch-entities` for prospects filtered by title and seniority, and let the user choose.
2. **Match.** Call `match-prospects`. For a name plus company, add the company's `business_id` from `match-business` when you have it. Results are complete: a person is either matched or null. A typo in an email is a miss; do not retry it as a name search, since that could return a different person.
3. **Report misses.** Say which people did not match and why a retry might help: an email, LinkedIn URL or company domain improves the odds. Enrich only the matched people. Do not replace an unmatched person with someone similar.
4. **Enrich** the matched table with `enrich-prospects`:
- `enrich-prospects-profiles` for title, location, work history and education.
- `enrich-prospects-contacts` for email and phone. Set `contact_types` to `["email"]` unless the user needs phone numbers too; leaving it empty requests both.
Company context, if askePreview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
--- name: list-builder 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." --- # List Builder Turn a plain-language audience description into a list of companies or people. The user sees a sample in chat and can export the full list. ## Connector rules Use only the Vibe Prospecting 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. - **`tool_reasoning`** is required on every call: one short sentence (≤200 characters) that paraphrases what the user wants. No earlier conversation, contact details, or other personal data. - **Chaining:** copy `session_id` and `table_name` from the previous tool response; never invent either. After an enrich or events step, use the new `table_name`. - **`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. - **What you can see:** `match-business` and `match-prospects` return complete results; fetch, enrich, and events tools return only a masked preview, so never quote values from it; `fetch-entities-statistics` returns aggregates; `show-sample` reveals up to 5 full rows. - **Finish with `show-sample`**, once per final `table_name`, then reply. Match-only and statistics-only work does not need it. The widget displays the sample rows, so do not repeat them as a table; use them for your analysis. If `display_status` is `masked`, say the full rows could not be revealed. - **Export** only after the user explicitly confirms, because it consumes credits. Show the returned download `url`. Never mention table names or session IDs to the user. - **Uploads:** you cannot upload files to Vibe Prospecting. Pasted lists and text from attached files are fine to use. If the user asks how to upload a list, point them to the Vibe Prospecting Hub: https://app.vibeprospecting.ai/lists ## Parse the request Pull these out of the user's message: - **Entity type:** `prospects` if any person attribute is named (title, seniority, department, skills); `businesses` only when the request is about companies with no people. - **Roles:** titles, seniority, department. - **Company traits:** industry, size, revenue, company age, public or private. - **Geography:** country, state or region, US city. Note whether it describes the person or the company. - **Signals:** tech stack, buying-intent topics, recent events (funding, new office, hiring, M&A) with a 30-90 day window. - **Count:** use the exact number requested; default 30, maximum 1,000. - **Extras:** contact details (emails, phones), people per company. Examples: "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". ## Workflow 1. **Ask what is missing, once.** Skip any question the user already answered. - *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. - *Contact details (prospects only):* unless the user already said
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
---
name: lookalike-accounts
description: "Find companies that resemble a seed company by rebuilding its industry, size, region and tech-stack profile and searching for others that share it. Use for 'find companies like Stripe', 'lookalike accounts for Acme', 'similar companies to our best customer', 'expand my territory', 'extend this account list'. Not for similar people (use list-builder) or for comparing named rivals (use competitor-research). Results are an approximation, not a similarity score."
---
# Lookalike Accounts
Rebuild the profile of one seed company, then search for companies that share it.
## Connector rules
Use only the Vibe Prospecting 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.
- **`tool_reasoning`** is required on every call: one short sentence (≤200 characters) that paraphrases what the user wants. No earlier conversation, contact details, or other personal data.
- **Chaining:** copy `session_id` and `table_name` from the previous tool response; never invent either. After an enrich or events step, use the new `table_name`.
- **`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.
- **What you can see:** `match-business` and `match-prospects` return complete results; fetch, enrich, and events tools return only a masked preview, so never quote values from it; `fetch-entities-statistics` returns aggregates; `show-sample` reveals up to 5 full rows.
- **Finish with `show-sample`**, once per final `table_name`, then reply. Match-only and statistics-only work does not need it. The widget displays the sample rows, so do not repeat them as a table; use them for your analysis. If `display_status` is `masked`, say the full rows could not be revealed.
- **Export** only after the user explicitly confirms, because it consumes credits. Show the returned download `url`. Never mention table names or session IDs to the user.
- **Uploads:** you cannot upload files to Vibe Prospecting. Pasted lists and text from attached files are fine to use. If the user asks how to upload a list, point them to the Vibe Prospecting Hub: https://app.vibeprospecting.ai/lists
## Input
- **Seed company** (required): a name or domain. If the user gives a person, or asks for similar contacts, use list-builder instead; this skill returns companies.
- **Count:** default 25, up to 100.
- **Overrides (optional):** country or region focus, size or revenue bucket, public-only, and extra tech-stack requirements.
## Workflow
1. **Match the seed** with `match-business`, using name and domain. If several candidates return, pick the one whose domain matches and say which you chose. If none resolves, ask for a domain.
2. **Check the seed.** A big brand that resolves to 1-50 employees under "Corporate Managing Offices" is a shell entity. Retry with the other domain, since a wrong seed produces unrelated results.
3. **Read the seed's profile** with `enrich-business-firmographics` and `enrich-business-technographics`, then `show-sample` on the enriched table to see the values. Take: industry (LinkedIn or NAICS, whichever is populated), headcount and revenue bucket, country (or the region the user asked for), and the top 3-5 technologies, favoring category-defining tools (CRM, marketing automation, data warehouse, cloud) over ubiquitous ones. Skip anything that comes back empty and do not guess. (The `show-sample` call here reads the enrichment values, it is not the final presentation.)
4. **Resolve values** with `autocomplete` for the industry and each technology. For flagship vendors, try the product-qualified name first ("Snowflake Data Cloud", "Stripe Payments"), because the bare name often returns noise. Drop anything that does not resolve cleanly, and tell the user.
5. **ApplPreview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
---
name: market-sizing
description: "Size a market: count how many companies match an ideal customer profile, refine the filters with the user until the number makes sense, and return the final filter set. Use for 'how many companies match', 'size the market for X', 'TAM for fintech in the UK', 'is my ICP too broad', 'territory sizing', or a rough SAM estimate. Counts and breakdowns only, with no list of companies unless asked. Not for building the list itself (use list-builder)."
---
# Market Sizing
Refine a company-level ICP and report how many companies match, using statistics instead of pulling rows.
## Connector rules
Use only the Vibe Prospecting 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.
- **`tool_reasoning`** is required on every call: one short sentence (≤200 characters) that paraphrases what the user wants. No earlier conversation, contact details, or other personal data.
- **Chaining:** copy `session_id` and `table_name` from the previous tool response; never invent either. After an enrich or events step, use the new `table_name`.
- **`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.
- **What you can see:** `match-business` and `match-prospects` return complete results; fetch, enrich, and events tools return only a masked preview, so never quote values from it; `fetch-entities-statistics` returns aggregates; `show-sample` reveals up to 5 full rows.
- **Finish with `show-sample`**, once per final `table_name`, then reply. Match-only and statistics-only work does not need it. The widget displays the sample rows, so do not repeat them as a table; use them for your analysis. If `display_status` is `masked`, say the full rows could not be revealed.
- **Export** only after the user explicitly confirms, because it consumes credits. Show the returned download `url`. Never mention table names or session IDs to the user.
- **Uploads:** you cannot upload files to Vibe Prospecting. Pasted lists and text from attached files are fine to use. If the user asks how to upload a list, point them to the Vibe Prospecting Hub: https://app.vibeprospecting.ai/lists
## Input
- **ICP** in plain language, or "my ICP" with details to ask for.
- **Use case (optional):** territory design, investor sizing, or ICP sharpening (default).
- **SAM inputs (optional):** an addressable fraction (0-1) and average revenue per account in USD.
## Workflow
1. **Parse the ICP** into filter dimensions and note which the user stated. Persona details ("CTOs", "VP Sales") are recorded but do not change a company count.
2. **Disambiguate regions first.** "EU" can mean EU member states or all of Europe; "Americas" can mean North America or the US and Canada. Ask one question, then count.
3. **Resolve free-text values** with `autocomplete`, then sort each into one of three outcomes before counting:
- *Clean match:* an unambiguous canonical value. Use it.
- *Parent or brittle match:* only a parent or sibling exists (for example "fintech" maps only to "Financial Services"). Stop and show the nearest entries, then ask whether to approximate with the parent, use a technology or intent proxy, or drop it. Do not substitute silently.
- *No match* after 2-3 phrasings (bare term, full product name, vendor plus suffix): say there is no matching value and offer the same options.
For flagship vendors, try the product-qualified name first ("Snowflake Data Cloud", "Stripe Payments").
One industry taxonomy per query: try `linkedin_category` first and use `naics_category` only when LinkedIn has no clean match.
4. **Count** with `fetch-entities-statistics` (`entity_type: businesses`) on the resolved filters. For a country-scoped count, add the per-location breakdown for the requestePreview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
--- name: meeting-prep description: "Prepare a 30-minute call brief for a target account: headline signals, attendee profiles, ranked talking points, discovery questions, a suggested agenda, and what to avoid. Use for 'prep me for a call with Acme', 'I have a meeting with Jane at Globex tomorrow', 'pre-meeting research', renewal or QBR meetings. Not for general research with no meeting (use account-research) or for a standalone person lookup (use enrich-contact)." --- # Meeting Prep Gather the company, signal and attendee evidence, then write a tight brief the user can read in five minutes. ## Connector rules Use only the Vibe Prospecting 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. - **`tool_reasoning`** is required on every call: one short sentence (≤200 characters) that paraphrases what the user wants. No earlier conversation, contact details, or other personal data. - **Chaining:** copy `session_id` and `table_name` from the previous tool response; never invent either. After an enrich or events step, use the new `table_name`. - **`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. - **What you can see:** `match-business` and `match-prospects` return complete results; fetch, enrich, and events tools return only a masked preview, so never quote values from it; `fetch-entities-statistics` returns aggregates; `show-sample` reveals up to 5 full rows. - **Finish with `show-sample`**, once per final `table_name`, then reply. Match-only and statistics-only work does not need it. The widget displays the sample rows, so do not repeat them as a table; use them for your analysis. If `display_status` is `masked`, say the full rows could not be revealed. - **Export** only after the user explicitly confirms, because it consumes credits. Show the returned download `url`. Never mention table names or session IDs to the user. - **Uploads:** you cannot upload files to Vibe Prospecting. Pasted lists and text from attached files are fine to use. If the user asks how to upload a list, point them to the Vibe Prospecting Hub: https://app.vibeprospecting.ai/lists ## Input - **Account** (required): a company name or domain. - **Attendees** (recommended): names with the company, or emails. Without them the brief stays generic. - **Meeting context** (strongly recommended): purpose, stakes, deal stage, what the user wants to walk out with, known tensions, competitors, what they are selling, and hypotheses to test. If it is missing, ask once; otherwise prepare general notes and say so. ## Workflow 1. **Anchor.** Restate the purpose and desired outcome in 1-2 sentences and pick 3-5 priority topics and any hypotheses. 2. **Match the company** with `match-business`, checking for the shell-entity pattern (big brand, 1-50 employees, "Corporate Managing Offices") and retrying with the alternate domain. 3. **Enrich the company,** at most 3 types per call, each on the latest `table_name`: firmographics and technographics, funding-and-acquisitions, strategic-insights and challenges, workforce-trends, competitive-landscape and company-hierarchies, linkedin-posts and website-changes. Gather broadly now; decide what matters at the writing step. 4. **Fetch events** with `fetch-businesses-events` on a 30-90 day window. Keep only events that name this company and tie to the meeting. 5. **Match the attendees** with `match-prospects`, by email when known, otherwise full name plus company (add the `business_id`). Report anyone who does not match; never invent their role. Enrich matched people with `enrich-prospects-profiles` for title, tenure and prior roles. Add `enrich-prospects-contacts` only if the user wants to reach out, with `contact_types` set to `["email"]` unless phone is needed
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
--- name: score-leads description: "Score and tier a list of target accounts (A, B, C by ICP fit, buying intent, recent trigger events and hiring momentum) or a list of people (Hot, Warm, Cold against a buyer persona and ICP), with a one-line 'why now' per row. Use for 'score these accounts', 'rank this list by ICP fit', 'prioritize my leads', 'which of these should I call first', 'tier my inbound leads'. Works on lists pasted in chat. Not for building a new list (use list-builder) or for research on a single company (use account-research)." --- # Score Leads Resolve a list, gather evidence for each row, then apply a transparent rubric the user can adjust. The scoring is your reasoning over the returned data; there is no built-in scoring engine. ## Connector rules Use only the Vibe Prospecting 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. - **`tool_reasoning`** is required on every call: one short sentence (≤200 characters) that paraphrases what the user wants. No earlier conversation, contact details, or other personal data. - **Chaining:** copy `session_id` and `table_name` from the previous tool response; never invent either. After an enrich or events step, use the new `table_name`. - **`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. - **What you can see:** `match-business` and `match-prospects` return complete results; fetch, enrich, and events tools return only a masked preview, so never quote values from it; `fetch-entities-statistics` returns aggregates; `show-sample` reveals up to 5 full rows. - **Finish with `show-sample`**, once per final `table_name`, then reply. Match-only and statistics-only work does not need it. The widget displays the sample rows, so do not repeat them as a table; use them for your analysis. If `display_status` is `masked`, say the full rows could not be revealed. - **Export** only after the user explicitly confirms, because it consumes credits. Show the returned download `url`. Never mention table names or session IDs to the user. - **Uploads:** you cannot upload files to Vibe Prospecting. Pasted lists and text from attached files are fine to use. If the user asks how to upload a list, point them to the Vibe Prospecting Hub: https://app.vibeprospecting.ai/lists ## Choose a mode - **Accounts:** the list is companies (names, domains). Output is a tier A/B/C with a score per account. - **People:** the list is leads (emails, LinkedIn URLs, or name plus company). Output is Hot, Warm or Cold per person. ## Input - **The list** (required), up to 50 accounts or 40 people per match call. - **ICP** (required): industries, headcount and revenue buckets, countries or regions, optional tech vendors, optional intent topics. For people, also the **buyer persona**: titles, seniority, department. - **Optional:** a source label per lead (demo request, pricing inquiry, webinar) passed through as given; weights; tier thresholds; trigger window (default 90 days). If the ICP is missing, ask for it; do not invent one. ## How many rows you can read Real values reach you only through `show-sample` (up to 5 rows) or, after an export, through `load-dataset` with `load_into: "context"` (up to 50 rows per page, using the export's `dataset_id`). So: - **Up to 5 rows:** score them directly from `show-sample`. - **6 to 50 rows:** tell the user you need the full rows to score them, which takes an export that uses credits. Run `export-to-csv` only after they confirm, then read the rows with `load-dataset`. - **More than 50:** score the first 50 and offer to continue, or export without scoring. ## Workflow 1. **Lock the rubric.** Restate the ICP and persona. Resolve free-text values with `autocomplete`, one term at a time. If an intent t
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
--- name: talent-sourcing description: "Source candidates from a job description or role brief, or map the talent bench for a function across target or competitor companies with movement signals such as layoffs and leadership changes. Use for 'find candidates for a senior Go engineer in Berlin', 'build a talent pipeline for a VP Sales', 'who could fill this role', 'map the data engineering teams at our competitors', 'where can we hire from'. Recruiting and talent intelligence only. Not for sales prospecting (use list-builder) or for researching a named person (use enrich-contact)." --- # Talent Sourcing Turn a role brief into a candidate search, or map where a function's talent sits across companies. ## Connector rules Use only the Vibe Prospecting 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. - **`tool_reasoning`** is required on every call: one short sentence (≤200 characters) that paraphrases what the user wants. No earlier conversation, contact details, or other personal data. - **Chaining:** copy `session_id` and `table_name` from the previous tool response; never invent either. After an enrich or events step, use the new `table_name`. - **`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. - **What you can see:** `match-business` and `match-prospects` return complete results; fetch, enrich, and events tools return only a masked preview, so never quote values from it; `fetch-entities-statistics` returns aggregates; `show-sample` reveals up to 5 full rows. - **Finish with `show-sample`**, once per final `table_name`, then reply. Match-only and statistics-only work does not need it. The widget displays the sample rows, so do not repeat them as a table; use them for your analysis. If `display_status` is `masked`, say the full rows could not be revealed. - **Export** only after the user explicitly confirms, because it consumes credits. Show the returned download `url`. Never mention table names or session IDs to the user. - **Uploads:** you cannot upload files to Vibe Prospecting. Pasted lists and text from attached files are fine to use. If the user asks how to upload a list, point them to the Vibe Prospecting Hub: https://app.vibeprospecting.ai/lists ## Choose a mode - **Pipeline:** the user has a role to fill and wants candidates. - **Bench map:** the user wants to see who does a function across a set of companies and where talent may be open to a move. ## Fair-hiring and privacy rules - Never filter, score or comment on protected characteristics (age, gender, ethnicity, religion, disability, nationality, family status) or on proxies for them, such as graduation year to infer age or a name to infer gender or origin. If the brief asks for that, decline that criterion and say why. - Use only job-related evidence that the data shows. Mark a skill the profile does not show as "unverified" instead of inferring it. - Use contact data only for recruiting outreach about a real role, and remind the user to honor opt-outs and local rules (GDPR, CCPA). - Do not pull personal contact data during a bench map. ## Pipeline mode ### Input Role (title, seniority, function); must-haves and nice-to-haves (propose a split and confirm if the brief does not separate them); the source-company profile or named target companies; exclusions (current employer, no-poach clients); geography; the number wanted (default 30, up to 150). ### Workflow 1. **Blueprint.** Translate the brief into a candidate profile and a source-company profile. Expand the title into 3-6 adjacent titles a strong candidate might hold today, and note a step-up pool one level below if the role is a promotion for most people. Show the blueprint and confirm before searching. 2. **Resolve values*
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
--- name: vibe-prospecting description: >- Find companies and contacts, build lead lists, enrich records with emails and phones, research firmographics and tech stacks, and surface buying intent or business events from Vibe Prospecting's B2B database (150M+ companies, 800M+ professionals). Use for sales, GTM, and prospecting workflows — list building, account research, decision-maker search, contact enrichment, TAM/ICP sizing, lookalikes. Triggers on phrases like "find companies", "find prospects", "build a list", "who works at", "get emails", "enrich this company", "companies using Salesforce", "buying intent", or "export results". --- # Vibe Prospecting Connect this chat to live B2B company and contact intelligence — search, enrich, and export without leaving the conversation. **Use only the Vibe Prospecting MCP tools in your tool list.** Follow each tool's live description and input schema — they are authoritative. Before the first real call for each distinct tool, read that schema and build arguments only from confirmed fields. If tools are missing or return auth/401 errors: tell the user to connect/authorize **Vibe Prospecting** in their host’s plugin settings, then retry. Do not invent credentials or work around auth. ## Tools | Tool | Use for | |------|---------| | `autocomplete` | Standardized filter values (required for controlled vocab) | | `fetch-entities` | Search companies or people | | `fetch-entities-statistics` | Aggregated breakdowns (only when filters fully match fetch) | | `match-business` | Name/domain → `business_id` (max 50) | | `match-prospects` | Email or name+company → `prospect_id` (max 40) | | `enrich-business` | Firmographics, tech, funding, intent, etc. on a business table | | `enrich-prospects` | Emails/phones (`enrich-prospects-contacts`) or profiles | | `fetch-businesses-events` | Company event detail rows | | `fetch-prospects-events` | People event detail rows | | `show-sample` | Billable preview after exploration — required before you reply | | `export-to-csv` | Credit-consuming full export (user must confirm first) | | `get-dataset` | List or reload saved hub datasets | Skip `match-*` if `fetch-entities` already returned IDs. ## Default workflow 1. Clarify only when required (see gates below). 2. `autocomplete` for every controlled-vocab filter you will use. 3. **One** comprehensive `fetch-entities` call (combine filters). Exception: linkedin→naics retry if results are too few or wrong type. 4. Optional `enrich-*` / `fetch-*-events` only when the user asked or answered a gate prompt with yes. 5. `show-sample` on each final `table_name` for this turn — then reply. Do not ask permission before `show-sample`. 6. Offer export only if there is more data than shown (or they asked for a file). Show cost → wait for explicit yes → `export-to-csv` on the **latest** `table_name`. **Never auto-export.** ## Hard rules 1. **`tool_reasoning`** — When the schema requires it, pass the user's request **verbatim** (≤2000 chars). Reuse that same string for the whole workflow. Do not invent a summary like "export". 2. **Chain with `session_id` + `table_name`.** Never invent either. Omit `session_id` on the first step; copy both from prior tool JSON afterward. After enrich/events, use the **new** `table_name` for every later step (especially export). 3. **`autocomplete` first** for: `linkedin_category`, `naics_category`, `company_tech_stack_tech`, `job_title`, `interests`, `skills`, `business_intent_topics`, `city_region` (USA cities). Use returned values only — never raw user wording. 4. **Never invent parameters.** Schema wins. 5. **One category type per fetch:** `linkedin_category` XOR `naics_category`. Prefer LinkedIn; fall back to NAICS only if LinkedIn is too broad / empty / wrong type. 6. **Location XOR:** `company_country_code` XOR `company_region_country_code` (same for prospect country/region). 7. **Quote `counts` correctly:** Tell the user `records_available` for delivered row
Preview of the first 4,000 characters. Read full instructions →
Version 8.1.2 adds workflow capabilities, updates discovery keywords, and adds representative starter prompts. All twelve skills include UI metadata and explicit MCP dependencies. Office-event filtering, market-sizing interpretation, meeting engagement evidence, and lead-scoring guidance are corrected. Existing descriptions, package identity, production MCP endpoint, and icon are unchanged.
Declared in the saved package. Remote tools may change independently.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 19, 2026.
plugin_asdk_app_6947c583d8308191844af6213ceabe16
Download plugin data (JSON)Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.