feat: add GTM AI marketplace skills

README.md

@@ -64,20 +64,40 @@ git clone https://github.com/Zoominfo/zoominfo-mcp-plugin.git
 
 | Skill | Description |
 |---|---|
+| `account-prioritization` | Rank accounts by ICP fit, intent, trigger signals, whitespace, and explainable next-best action. |
 | `account-research` | Produce an account intelligence brief with firmographics, relationship context, intent, news, and next actions |
 | `build-list` | Build targeted account or contact lists from natural-language criteria |
+| `build-tam` | Build a market or territory TAM using ZoomInfo company search counts, reusable ICP filters, sample accounts, and assumption notes. |
+| `business-case-builder` | Draft a buyer-specific business case using account scale, pain hypotheses, relevant signals, stakeholders, and measurable outcome assumptions. |
 | `buying-committee` | Map decision-makers, influencers, champions, and coverage gaps at a target account |
+| `campaign-builder` | Turn an ICP, trigger, or product motion into a segmented campaign audience with personas, proof points, messaging angles, and activation fields. |
+| `champion-tracking` | Track champion movement, title changes, departures, influence, and replacement contacts across target or customer accounts. |
+| `clay-migration` | Convert Clay-style enrichment tables and workflows into governed ZoomInfo MCP skill runs with equivalent outputs and fewer manual provider chains. |
+| `competitive-battlecard` | Build an account- or competitor-specific battlecard from firmographics, news, scoops, intent, buying committee, and positioning evidence. |
 | `competitor-analysis` | Create fact-led competitor briefs using ZoomInfo data plus public context |
+| `crm-cleanup` | Audit and repair CRM account/contact data using ZoomInfo matching, confidence scoring, duplicate detection, and safe writeback recommendations. |
+| `deal-qualification` | Qualify an account or opportunity using firmographics, buyer fit, urgency signals, stakeholder coverage, and data confidence. |
+| `deal-risk-scorer` | Score deal risk using account context, stakeholder coverage, trigger evidence, competitor signals, and missing buying-committee roles. |
+| `demo-scripting` | Create account-specific demo talk tracks using company context, persona priorities, trigger signals, and competitive angles. |
+| `discovery-brief` | Prepare a discovery-call brief with account context, buyer hypotheses, recent signals, personas, questions, and talk tracks. |
 | `enrich-company` | Look up company profiles, firmographics, financials, structure, and growth signals |
 | `enrich-contact` | Look up professional contact profiles, title, department, contact data, and accuracy signals |
 | `find-similar` | Find lookalike companies or contacts based on a reference account or person |
+| `icp-definition` | Derive a reusable ICP from target accounts, winners, hypotheses, or market criteria using ZoomInfo firmographic and signal data. |
 | `meeting-prep` | Prepare for upcoming calls with account, attendee, relationship, and talking-point context |
 | `personalize-email` | Draft outreach grounded in account, contact, intent, and trigger signals |
+| `pipeline-hygiene` | Inspect open pipeline for stale deals, bad data, missing stakeholders, weak timing signals, and account-risk indicators. |
+| `procurement-prep` | Prepare for procurement by mapping stakeholders, account structure, risk signals, vendor/contract clues, and negotiation angles. |
 | `recommend-contacts` | Get AI-ranked contact recommendations at a target company |
+| `renewal-risk-brief` | Assess renewal or expansion risk using account signals, champion status, stakeholder gaps, growth/contraction clues, and next actions. |
 | `score-accounts` | Prioritize accounts by ICP fit, intent, trigger signals, and explainable scoring |
 | `score-leads` | Rank inbound leads by fit, urgency, verified contact data, and recommended action |
+| `stakeholder-mapper` | Map stakeholders at a target account by role, seniority, likely influence, buying-committee coverage, and recommended outreach order. |
 | `tam-sizer` | Size a market or territory and produce a reusable ICP filter set |
 | `tech-stack-snapshot` | Summarize detected technologies, displacement angles, and integration plays |
+| `territory-planning` | Design or rebalance territories using ZoomInfo account counts, fit, coverage, trigger density, and rep-actionable segments. |
+| `trigger-based-list-build` | Build account or contact lists around buying triggers such as intent, scoops, news, funding, hiring, technology, and leadership changes. |
+| `waterfall-enrich` | Enrich company and contact records with ZoomInfo-first matching, field-level confidence, provenance, unresolved rows, and activation-ready output. |
 
 ## Project Structure
 

skills/account-prioritization/SKILL.md

@@ -0,0 +1,54 @@
+---
+name: account-prioritization
+description: Rank accounts by ICP fit, intent, trigger signals, whitespace, and explainable next-best action.
+---
+
+# Account Prioritization
+
+Rank accounts by ICP fit, intent, trigger signals, whitespace, and explainable next-best action.
+
+## Input
+
+The user will describe the job via `$ARGUMENTS`. Capture any supplied accounts, contacts, domains, companies, CRM rows, segments, territories, product motion, timeframe, output format, or activation target.
+
+If a required entity is missing, ask one concise clarifying question. If the request is broad but actionable, proceed with a stated assumption rather than blocking.
+
+## MCP Tool Selection
+
+Use free discovery before credit-consuming depth:
+
+- `search_companies`: normalize or build the account universe.
+- `search_intent`: discover accounts already researching relevant topics.
+- `search_scoops`: discover accounts with recent events that create urgency.
+- `enrich_companies`: deepen only the accounts being scored.
+- `enrich_intent`, `enrich_scoops`, `enrich_news`: add why-now evidence for known accounts.
+- `find_recommended_contacts`: include reachability/stakeholder strength in the score when seller actionability matters.
+- `account_research`: use for synthesized context when CRM/conversation history can change the ranking.
+
+## Workflow
+
+1. **Capture the prioritization goal**: new logo, expansion, renewal, competitive takeout, territory focus, or campaign audience.
+2. **Normalize the input account list or build one with `search_companies`; resolve all filters with `lookup`.**
+3. **Enrich accounts with firmographics, technologies, hierarchy, growth, and department data via `enrich_companies`.**
+4. **Pull intent, scoops, and news where relevant; keep only signals that map to the prioritization goal.**
+5. **Score accounts with transparent factors**: ICP fit, timing/urgency, reachable personas, data confidence, and strategic value.
+6. **Assign each account to an action tier with a concise why-now rationale and recommended owner action.**
+
+## Output Format
+
+Return a concise operator-ready artifact:
+
+- **Objective**: what this run is solving
+- **Inputs used**: accounts, contacts, filters, timeframe, and assumptions
+- **ZoomInfo workflow**: MCP tools used and why
+- **Results**: Ranked account list with score breakdown, evidence, confidence, action tier, and next-best action.
+- **Evidence**: source fields, signal dates, confidence, and caveats
+- **Next actions**: the 3-5 highest-leverage follow-ups
+
+## Quality Bar
+
+- Resolve taxonomy-backed fields with `lookup` before search or enrichment.
+- Prefer stable identifiers: ZoomInfo IDs, company domains, and emails before fuzzy names.
+- Keep confidence visible. Do not hide unmatched, ambiguous, stale, or conflicting records.
+- Separate verified ZoomInfo data from inference and recommendations.
+- Do not invent customer pain, internal initiatives, tools, budgets, or competitor usage without evidence.

skills/build-tam/SKILL.md

@@ -0,0 +1,53 @@
+---
+name: build-tam
+description: Build a market or territory TAM using ZoomInfo company search counts, reusable ICP filters, sample accounts, and assumption notes.
+---
+
+# Build TAM
+
+Build a market or territory TAM using ZoomInfo company search counts, reusable ICP filters, sample accounts, and assumption notes.
+
+## Input
+
+The user will describe the job via `$ARGUMENTS`. Capture any supplied accounts, contacts, domains, companies, CRM rows, segments, territories, product motion, timeframe, output format, or activation target.
+
+If a required entity is missing, ask one concise clarifying question. If the request is broad but actionable, proceed with a stated assumption rather than blocking.
+
+## MCP Tool Selection
+
+Use TAM tools by job type:
+
+- `lookup`: mandatory for industries, locations, technologies, job functions, and other controlled filters.
+- `search_companies`: primary TAM counter and sample-account source; use `meta.totalResults` for counts.
+- `find_similar_companies`: expand from seed/won accounts into lookalike ICP hypotheses before sizing.
+- `search_intent`: size in-market subsegments when the TAM is topic-led or demand-led.
+- `search_scoops`: size event-triggered subsegments such as funding, hiring, leadership changes, projects, or pain points.
+- `enrich_companies`: enrich representative samples, not the whole TAM, unless the user explicitly approves credit-consuming enrichment.
+
+## Workflow
+
+1. **Translate the user request into an explicit ICP**: industries, geography, employee count, revenue, technologies, growth/funding, ownership, and exclusions.
+2. **Use `lookup` for every taxonomy-backed field before search. For industries, fuzzy-match each term separately and prefer specific sub-industries over broad parents.**
+3. **Run `search_companies` with `pageSize**: 1` to capture `meta.totalResults` for the headline TAM count.
+4. **Run segmented counts for the dimensions that matter most**: region, employee band, industry, revenue band, or technology.
+5. **Pull representative accounts with `search_companies` using sorted views such as `-employeeCount` or `-revenue`; label samples as illustrative, not a census.**
+6. **Stress-test assumptions**: run a broader and narrower variant and show sensitivity of TAM to the highest-leverage filters.
+
+## Output Format
+
+Return a concise operator-ready artifact:
+
+- **Objective**: what this run is solving
+- **Inputs used**: accounts, contacts, filters, timeframe, and assumptions
+- **ZoomInfo workflow**: MCP tools used and why
+- **Results**: TAM estimate, applied filters, sensitivity ranges, segment breakdowns, sample accounts, exclusions, and reusable ICP filter set.
+- **Evidence**: source fields, signal dates, confidence, and caveats
+- **Next actions**: the 3-5 highest-leverage follow-ups
+
+## Quality Bar
+
+- Resolve taxonomy-backed fields with `lookup` before search or enrichment.
+- Prefer stable identifiers: ZoomInfo IDs, company domains, and emails before fuzzy names.
+- Keep confidence visible. Do not hide unmatched, ambiguous, stale, or conflicting records.
+- Separate verified ZoomInfo data from inference and recommendations.
+- Do not invent customer pain, internal initiatives, tools, budgets, or competitor usage without evidence.

skills/business-case-builder/SKILL.md

@@ -0,0 +1,52 @@
+---
+name: business-case-builder
+description: Draft a buyer-specific business case using account scale, pain hypotheses, relevant signals, stakeholders, and measurable outcome assumptions.
+---
+
+# Business Case Builder
+
+Draft a buyer-specific business case using account scale, pain hypotheses, relevant signals, stakeholders, and measurable outcome assumptions.
+
+## Input
+
+The user will describe the job via `$ARGUMENTS`. Capture any supplied accounts, contacts, domains, companies, CRM rows, segments, territories, product motion, timeframe, output format, or activation target.
+
+If a required entity is missing, ask one concise clarifying question. If the request is broad but actionable, proceed with a stated assumption rather than blocking.
+
+## MCP Tool Selection
+
+Use data tools to size and de-risk assumptions:
+
+- `account_research`: preferred when CRM, opportunity, or conversation context can inform the business case.
+- `enrich_companies`: scale, revenue, employee footprint, technology, funding, and hierarchy assumptions.
+- `enrich_intent`, `enrich_scoops`, `enrich_news`: urgency and executive narrative.
+- `find_recommended_contacts` and `search_contacts`: identify economic, technical, finance, and executive stakeholders.
+- `contact_research`: use for named buyer-specific priorities when relationship history is relevant.
+
+## Workflow
+
+1. **Clarify buyer persona, product, desired outcome, account, and any known metric assumptions.**
+2. **Enrich company data to size the opportunity**: employee count, revenue, locations, departments, growth, technologies, and hierarchy.
+3. **Pull news, scoops, and intent to support urgency and business relevance.**
+4. **Map stakeholders who will care about financial, operational, technical, and risk outcomes.**
+5. **Build the case with explicit assumptions; use ranges when inputs are uncertain and do not fabricate ROI numbers.**
+6. **Recommend proof points or data the seller should collect next to tighten the case.**
+
+## Output Format
+
+Return a concise operator-ready artifact:
+
+- **Objective**: what this run is solving
+- **Inputs used**: accounts, contacts, filters, timeframe, and assumptions
+- **ZoomInfo workflow**: MCP tools used and why
+- **Results**: Business case outline with account context, value drivers, stakeholder lens, quantified assumptions, risk notes, and next data asks.
+- **Evidence**: source fields, signal dates, confidence, and caveats
+- **Next actions**: the 3-5 highest-leverage follow-ups
+
+## Quality Bar
+
+- Resolve taxonomy-backed fields with `lookup` before search or enrichment.
+- Prefer stable identifiers: ZoomInfo IDs, company domains, and emails before fuzzy names.
+- Keep confidence visible. Do not hide unmatched, ambiguous, stale, or conflicting records.
+- Separate verified ZoomInfo data from inference and recommendations.
+- Do not invent customer pain, internal initiatives, tools, budgets, or competitor usage without evidence.