Power your chat with B2B data: lead lists, company research, contact enrichment, and outreach personalization.
- GitHub stars
- 298
Install
/plugin install vpai@vibeprospectingRun it inside Claude Code after adding the marketplace with /plugin marketplace add explorium-ai/vibeprospecting-plugin.
Contents
Discovered from sourceSkills 2
Vibe Prospecting → HubSpot field mapping
Vibe Prospecting prospects map to HubSpot Contacts. Vibe Prospecting businesses map to HubSpot Companies.
Vibe Prospecting field names are the column names in Vibe Prospecting results. HubSpot properties are shown with their label and internal name.
When this mapping applies. Whenever Vibe-sourced fields are written to HubSpot (insert or update), use the destinations in these tables, even if the user did not ask about mapping. This rule only decides where Vibe-sourced fields go. It does not authorize a write, and it does not add records or fields beyond what the user asked for.
Property definitions are the user's to manage
- Never create or modify HubSpot property definitions or enumeration options.
- Before writing, check that each mapped destination exists on the correct object (Contacts for prospects, Companies for businesses).
- For ordinary mapped fields, if a destination is missing or cannot accept the raw value (for example an invalid enumeration option), omit that field, report its HubSpot label and internal name, and continue with the other mapped fields. The list name below is required by default; skip it only when the user explicitly requests that exception.
- Do not silently substitute another destination, and do not transform, split, truncate or derive values to make them fit. The only scoped exception is the additional-phone extraction described below; do not apply it to other fields.
Custom destinations are marked (custom) and must be created by the user in HubSpot before they can receive data. They use the VP label prefix and vp_ internal-name prefix. Users may change these defaults in their own skill instance.
To change a destination: create the property yourself in HubSpot (Settings → Properties), or pick an existing one. Then edit the row in this file: update the HubSpot label, internal name, type and the custom marker. Keep the Vibe Prospecting field name unchanged. Reinstall the updated skill.
If you edit a destination in a mapping table, use that row's edited label, internal name, and type—not the default property names mentioned elsewhere in this file.
List name before export
By default, before each new export for a HubSpot push, suggest a list name based on the user's request and conversation, then ask the user to approve it or provide a different name. Do not offer the dataset name as a default. If the user already explicitly supplied a name for this export, that is their confirmation; do not ask again. Do not proceed with an unconfirmed or blank name, or silently reuse one from a different export.
The default destination on Contacts and Companies is VP List Name (vp_list_name, single-line text, custom). The user may explicitly choose a different existing destination for this push or explicitly ask to skip the list-name field. Honor that choice for this push without requiring a skill edit or reinstall. Do not infer permission to skip or change the destination from a missing property or general export approval. For a lasting change to the default, the user may edit this destination in the skill and reinstall it.
Unless the user explicitly asked to skip the list name, check the chosen destination's live HubSpot property definition on every target object type before export. It must exist and accept the confirmed name. If missing or incompatible, identify its label, internal name, and object type, and ask the user to create/fix it manually, choose another existing property, or explicitly request skipping the list-name field. Stop the push before export until a usable destination is verified or the user explicitly requests skipping it. Never create properties or silently substitute a destination.
When the list name is not skipped, write the confirmed name unchanged on every contact and company inserted or updated. Recheck the chosen destination before record writes; if it is no longer usable, stop until resolved or the user explicitly requests skipping it. If the user explicitly requests skipping it, omit the field and reflect that choice in the pre-write report. The name approval or skip request is not approval for export cost or HubSpot writes; retain the existing approval requirements. This is a field only: do not create a HubSpot list or add list memberships. Other fields retain ordinary mapping/reporting behavior without dedicated missing-field prompts.
Show the field mapping before writing to HubSpot (required)
After the Vibe Prospecting data is exported and before any record is created or updated in HubSpot, always show the user a field-mapping report for this specific push. Build it from a live check of the target HubSpot account, not from this file alone:
- Check every destination in the relevant table(s) below against the account. For enumeration destinations such as Lead Status, also confirm the required option exists.
- Check the exported data: note which Vibe fields actually have values for the rows being pushed.
- Present one table per object type being written, with these columns:
| Vibe Prospecting field | HubSpot label | Internal name | In HubSpot? | Written in this push? |
|---|
- In HubSpot?: ✅ Exists (mark standard vs custom where useful) or ❌ Missing.
- Written in this push?: ✅ Yes; ➖ No data (destination exists but the field is empty for these rows, with a short reason, e.g. "emails only were requested"); or ❌ Skipped (destination missing or cannot accept the value).
- Include every mapped field from the table, not only the ones being written, so the user sees what exists and what does not.
- One report row per mapping-table row; never merge rows (e.g. VP Additional Phone Number 1–3 are three rows).
- Put the list-name row first in each contact/company report table and bold its label and value so it stands out from other fields. Show the chosen destination or that the user explicitly requested skipping it. Unless explicitly skipped, stop if it cannot be written. Add rows for Lead Status on new contacts and associations being created (e.g. contact → existing company, with its ID).
- Then ask for approval of the write as usual. The mapping report does not replace the HubSpot record-level confirmation; show both, or combine them in one message.
Contacts: Vibe Prospecting prospect → HubSpot Contact
| Vibe Prospecting field | HubSpot label | HubSpot internal name | Type |
|---|---|---|---|
prospect_first_name | First Name | firstname | Single-line text |
prospect_last_name | Last Name | lastname | Single-line text |
contact_professional_email | email | Single-line text | |
contact_mobile_phone | Mobile Phone Number | mobilephone | Single-line text |
contact_phone_numbers (additional number 1; see extraction below) | VP Additional Phone Number 1 (custom) | vp_additional_phone_number_1 | Single-line text |
contact_phone_numbers (additional number 2; see extraction below) | VP Additional Phone Number 2 (custom) | vp_additional_phone_number_2 | Single-line text |
contact_phone_numbers (additional number 3; see extraction below) | VP Additional Phone Number 3 (custom) | vp_additional_phone_number_3 | Single-line text |
prospect_job_title | Job Title | jobtitle | Single-line text |
prospect_company_name | Company Name | company | Single-line text |
prospect_company_website | Website URL | website | Single-line text |
prospect_city | City | city | Single-line text |
prospect_region_name | State/Region | state | Single-line text |
prospect_country_name | Country/Region | country | Single-line text |
prospect_linkedin | LinkedIn URL | hs_linkedin_url | Single-line text |
prospect_id | VP Prospect ID (custom) | vp_prospect_id | Single-line text |
business_id | VP Business ID (custom) | vp_business_id | Single-line text |
prospect_full_name | VP Full Name (custom) | vp_full_name | Single-line text |
prospect_job_department | VP Job Department (custom) | vp_job_department | Single-line text |
prospect_job_seniority_level | VP Job Seniority Level (custom) | vp_job_seniority_level | Single-line text |
contact_professional_email_status | VP Email Status (custom) | vp_email_status | Single-line text |
prospect_experience | VP Experience (custom) | vp_experience | Multi-line text |
prospect_skills | VP Skills (custom) | vp_skills | Multi-line text |
prospect_interests | VP Interests (custom) | vp_interests | Multi-line text |
Lead Status. For contacts newly created from Vibe Prospecting data, set Lead Status (hs_lead_status) to the option labelled New, internal value NEW. Never change Lead Status on existing contacts. If hs_lead_status in the target account has no option labelled New, skip it and report; do not create or substitute an option.
Additional phone extraction
Keep contact_mobile_phone → mobilephone unchanged. Extra numbers come from the separate contact_phone_numbers export column, not from splitting contact_mobile_phone.
In the VP CSV export, contact_phone_numbers is a JSON-encoded array of phone-number strings, not an array of objects. Read the CSV with a proper CSV parser first, then JSON-decode the cell once; CSV quote escaping is not part of the JSON value. If the data reader already decoded the cell, use the array of strings directly. Walk its string items in array order. Do not split on commas, inspect object values, stringify other types, or extract numbers from arbitrary text. An empty cell is ordinary no data. A malformed JSON cell, non-array value (including a single plain-text phone number), or non-string array item leaves the additional-phone fields unmapped for that row rather than guessing a format.
For comparison only, trim surrounding whitespace and remove spaces, parentheses, hyphens, and dots from each number; preserve a leading + and any explicit country code. Exclude every value with the same comparison key as contact_mobile_phone, skip blank values, and deduplicate the remaining values by that key in first-occurrence order. The primary can occur anywhere in the array or be absent: do not drop the first item by position or require the primary to be present. Do not infer a country code, convert 00 prefixes, or drop extensions to force equality. Write each retained value exactly as supplied, not its comparison key.
Map the first three retained values to VP Additional Phone Number 1, 2, and 3 respectively. The limit is three additional numbers, beyond the primary. Omit unused destinations without clearing existing values; ignore excess values. A missing destination keeps its assigned slot: do not shift its number into another property. Phone fields use the same pre-write mapping report and skip/no-data handling as ordinary fields—no extra prompts, missing-phone warnings, or overflow counts.
The array may not be included in a particular export. If contact_phone_numbers is absent or empty, handle it as ordinary unavailable source data and preserve the primary mapping. Never invent extra numbers or fetch a different data source just to fill these fields.
Companies: Vibe Prospecting business → HubSpot Company
| Vibe Prospecting field | HubSpot label | HubSpot internal name | Type |
|---|---|---|---|
business_name | Company name | name | Single-line text |
business_domain | Company Domain Name | domain | Single-line text |
business_website | Website URL | website | Single-line text |
business_city_name | City | city | Single-line text |
business_region | State/Region | state | Single-line text |
business_country_name | Country/Region | country | Single-line text |
business_business_description | Description | description | Multi-line text |
prospect_company_linkedin | LinkedIn Company Page | linkedin_company_page | Single-line text |
business_logo | Logo URL | hs_logo_url | Text (string) |
business_number_of_employees_range | Employee range | hs_employee_range | Text (string) |
business_yearly_revenue_range | Revenue range | hs_revenue_range | Text (string) |
business_id | VP Business ID (custom) | vp_business_id | Single-line text |
business_naics | VP NAICS Code (custom) | vp_naics_code | Single-line text |
business_naics_description | VP NAICS Description (custom) | vp_naics_description | Single-line text |
business_sic_code | VP SIC Code (custom) | vp_sic_code | Single-line text |
business_sic_code_description | VP SIC Code Description (custom) | vp_sic_code_description | Single-line text |
business_business_intent_topics | VP Intent Topics (custom) | vp_intent_topics | Multi-line text |
Employee and revenue ranges go only to the range properties above, as the raw range text. Never write them to the numeric numberofemployees or annualrevenue properties.
row_num and created_at are export metadata and are not mapped.
Vibe Prospecting
B2B prospecting — companies, contacts, enrichment, events.
Platform
Before any prospecting work, detect your host using the rules below, read exactly one platform guide, and follow it for auth, workflow, flags, and troubleshooting.
Detecting your runtime (mandatory, in order)
- Host identity in your system context (check this first — overrides tool names):
- Claude Code — context explicitly says you are Claude Code / Anthropic's CLI. → read
claude-code.mdonly. Do not readclaude-chat.mdorcowork.md. MCP tools in the list (mcp__*__fetch-entities) do not change this. - OpenAI Codex — context identifies Codex or
CODEX_SHELL=1. →codex.md - OpenClaw — context identifies OpenClaw or
OPENCLAW_CLI=1/OPENCLAW_SHELL. →openclaw.md - Grok Build — context identifies Grok Build / xAI's CLI. →
other.md, using thevpaiCLI workflow.
- Claude Code — context explicitly says you are Claude Code / Anthropic's CLI. → read
- Only if step 1 did not match — no CLI host identity, no shell:
- Claude Cowork — Cowork workspace,
.plugininstall, connector store. →cowork.md - Claude Chat — claude.ai or Claude desktop MCP connector (not Cowork). →
claude-chat.md
- Claude Cowork — Cowork workspace,
- Fallback: terminal, scripts, CI, or unknown host →
other.md
Never infer platform from MCP tool names alone (mcp__claude_ai_*, mcp__*__fetch-entities, etc.). Tool prefixes are not a host signal when step 1 already identified Claude Code, Codex, OpenClaw, or Grok Build. A generic CLI Environment block (cwd, shell, platform) establishes shell access, not host identity; without an explicit host match, use the fallback guide.
| Platform | Read now |
|---|---|
| Claude Code | claude-code.md — vpai CLI |
| OpenAI Codex | codex.md |
| OpenClaw gateway | openclaw.md |
| Grok Build | other.md — vpai CLI |
| Claude Cowork | cowork.md — MCP connector; not Claude Code |
| Claude Chat (claude.ai, Claude desktop) | claude-chat.md — MCP connector; not Cowork or Claude Code |
| Other (terminal, scripts, CI, generic hosts) | other.md |
CLI hosts use vpai — each platform guide is self-contained (Sample Gate, stdout/csv_path, CSV upload). Chat/Cowork follow each MCP tool's description and input schema only.
Hard Rules
tool_reasoning(or platform equivalent) on every real call. Use the user's request verbatim. Reuse across the whole workflow. Skip only when inspecting a tool's input schema with no real execution.- Chain via session + CSV, never paste IDs. Each step returns
session_idandcsv_path(names may vary slightly by host). Never inventsession_id— on the first step omit it and use the value MCP returns; on later steps copy it exactly from the prior tool JSON. Pass--csv-path(CLI) from the priorcsv_path. Do not paste raw ID lists into tool arguments when the platform reads IDs from the source CSV. Forfetch-entitiesprospects scoped to earlier companies, pass the prior business output'scsv_pathvia--businesses-csv-pathper your platform guide. - You may edit the CSV between steps — keep the ID column. On CLI hosts, read the file at
csv_path, filter/dedupe/add columns, or rewrite rows, then pass the result to the next step via--csv-path. Always retain the entity ID column:business_idfor business workflows,prospect_idfor prospect workflows. Every row you want processed next must have a non-empty ID in that column. Do not rename or drop those headers — the CLI reads them verbatim for ID injection and joins. autocompletefirst for:naics_category,linkedin_category,company_tech_stack_tech,job_title,interests,skills,business_intent_topics,city_region. Use returned standardized values, not raw user wording.- Never invent tool parameters. Before the first real execution of each distinct tool in a workflow, read that tool's live input schema (from the connector or your platform's schema discovery). Do this even when the planned call looks obvious — schemas drift. Re-read when tools, filters, or shapes change materially. Build each call only from fields confirmed by that schema.
- Session continuity. Reuse
session_idfrom prior tool JSON on every subsequent step in the same workflow — never make one up. Reuse the prior step'scsv_pathvia--csv-path(CLI) when chaining enrich, events, or scoped fetch. Start a new session only for a genuinely new task. fetch-entities-statisticsonly when stats supports the full fetch. Compare your plannedfetch-entitiespayload to the input schema forfetch-entities-statistics. Call statistics only if every filter key, value shape,entity_type, and scope you rely on (including session-scoped business CSVs) is accepted the same way as forfetch-entities. If any part is missing, unsupported, or needs a different shape, skip stats — do not call it with a partial or guessed subset. When you do call it, reuse the same filter object (and supported scope) asfetch-entities, plustool_reasoningwhere required. Call stats again before a full-scale fetch if filters or scope changed and the full fetch filter set still fits statistics.
Tool Mechanics
Behavior and caveats the live input schema may not spell out. For allowed filter values, enum strings, and enrichment type names, always use each tool's input schema.
Autocomplete
Requires autocomplete: linkedin_category, naics_category, company_tech_stack_tech, job_title, interests, skills, business_intent_topics, city_region.
Does not require autocomplete: company_country_code (ISO Alpha-2), company_region_country_code (ISO 3166-2), fixed buckets (company_size, company_revenue, company_age, job_level, job_department — exact allowed strings come from fetch-entities / fetch-entities-statistics input schema), website_keywords (free text).
Mutual exclusions: linkedin_category and naics_category — use one, not both. company_region_country_code and company_country_code — use one.
Picking values: Autocomplete may return noisy variants. Pick the canonical clean value (usually the first clean result). Multiple values broaden with OR logic; avoid near-duplicates unless you want a wider search.
Fetch
job_titleis substring-match, not exact. For executive searches, combine withjob_level(usuallyc-suite) to remove assistants, advisors, and office-of roles.company_sizeuses fixed buckets with no exact numeric cutoff. For "over N employees", approximate with adjacent buckets or enrich withfirmographicsfor exact headcount.- Business location filters (
company_country_code,company_region_country_code,city_region) match headquarters only — not branch or operating locations. - Prospects at prior companies: For
fetch-entitieswithentity_type: prospectsscoped to businesses from an earlier step, chain via session and pass the prior business step'scsv_pathas--businesses-csv-pathper your platform guide. - Row limits and pagination: per your platform guide (CLI:
--number-of-results; Chat/Cowork: MCP tool docs). max_per_company: auto-applied on prospect fetches so results spread across companies (not all from one big employer); omit from--argsunless the user sets it — their value overrides the auto cap.
Events (fetch-businesses-events / fetch-prospects-events)
- Chain from the prior step's session and source CSV with
business_id(business events) orprospect_id(prospect events). - When IDs come from the source CSV, do not also pass
business_ids/prospect_idsinline. - Batching is capped at 20 IDs per request; hosts may chunk and merge automatically.
- Output columns are
event_<event_type>: each cell is a JSON array string for that type (newest-first, capped per type), or empty when no events exist for that type.
Match
- Skip match if you already ran
fetch-entities— those results include IDs. - CSV file upload is CLI only — see your platform guide.
Enrich
financial-metricsrequiresparameters.date(see input schema for format).website-keywordsrequiresparameters.keywords.- Enrichment alone does not find people at a company — use
fetch-entitieswithentity_type: prospects(scoped to prior companies when needed) instead. - When chaining from a source CSV,
business_ids/prospect_idsneed not appear in tool arguments.
Filter Pattern
{ "values": ["v1", "v2"], "negate": false } // include or exclude
{ "gte": 6, "lte": 24 } // range
true | false | null // boolean (not wrapped)
Exception — business_intent_topics: use { "topics": ["Category:Topic"], "negate": false } (not values). Topics must come from autocomplete.
Location matching: Business location filters (company_country_code, company_region_country_code, city_region) match a company's headquarters only — not branch/operating locations. A search for "companies in the UK" returns companies HQ'd in the UK, and excludes e.g. a foreign company that merely operates there. This is the default for all fetch-entities / fetch-entities-statistics business queries and is not user-configurable.
Limits
| Tool | Limit |
|---|---|
match-business | 50 per call |
match-prospects | 40 per call |
enrich-business | 50 IDs per call |
enrich-prospects | 50 IDs per call |
fetch-businesses-events / fetch-prospects-events | Up to 20 IDs per request when batching. Pass event_types and timestamp_from. When chaining, IDs come from the source CSV — not inline ID arrays. |
Troubleshooting
| Error | Solution |
|---|---|
| Auth, connector setup, CLI invocation, flags, or chaining syntax | Read the matching platform guide from the Platform table |
| Empty results | Check filter values; run autocomplete for controlled-vocab fields; re-read the tool's input schema |
linkedin_category + naics_category together | Mutually exclusive — use one |
| Invented or unconfirmed parameters | Re-read the live input schema before calling; build arguments only from confirmed fields |
Support
When the user asks a support-related question (for example: how to contact support, who to contact, they have an issue, or something isn't working), reply briefly and point them here — do not dig into Explorium internals or over-explain.
For support, please reach out to the Vibe Prospecting team via the contact page:
Commands 1
Skip sample (this request only)
Hosts: Claude Code, Codex, OpenClaw, and other CLI hosts only (claude-code.md, codex.md, openclaw.md, other.md). Not Claude Chat or Cowork — those have no Sample Gate.
The user's query is:
$ARGUMENTS
First: load the normal Vibe Prospecting skill (vibe-prospecting / /vpai:vibe-prospecting), detect the host, and read the matching CLI platform guide. Follow that skill for install, auth, schema discovery, autocomplete, chaining, and export rules.
Then, for this user turn only, override Sample Gate:
- Do not run the 5-entity sample preview.
- Do not wait for approval before full scale.
- Run the complete prospecting workflow at the user's requested scale immediately.
- This does not persist — later messages without an explicit skip return to sample-first mode.
- After full scale, copy
csv_pathto the working directory with a proper name based on the user's question.
Treat $ARGUMENTS as the normal prospecting request. If $ARGUMENTS is empty, ask what they want to fetch or enrich at full scale.
Sponsors
Details
- Marketplace
- explorium-ai/vibeprospecting-plugin
- Source
- explorium-ai/vibeprospecting-plugin
- Category
- Data
- License
- MIT
- Keywords
- b2b, prospecting, leads, sales, enrichment, companies, contacts
