Stats
Actions
Tags
From zoominfo
Produce a full intelligence brief on a target company — firmographics, CRM/account context, intent signals, recent news, scoops, and competitive landscape — framed by your GTM context and led with a TL;DR summary. Identify the account by ZoomInfo account/company ID (preferred) or by company name, domain, or ticker (which triggers a lookup step). Include detailed context on why the brief is being pulled.
How this skill is triggered — by the user, by Claude, or both
Slash command
/zoominfo:account-researchThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Produce a high-signal intelligence brief on a target company. Lead with a synthesized executive summary, suppress sections where data is thin, and tie next steps to specific people and concrete topics surfaced during research.
Produce a high-signal intelligence brief on a target company. Lead with a synthesized executive summary, suppress sections where data is thin, and tie next steps to specific people and concrete topics surfaced during research.
The user will provide via $ARGUMENTS an account identifier (required) plus optional context:
136118787). Use directly as companyId; skip the search step.companyId via search_companies as a first step (see Workflow step 2).account_research query, intent seeding, news/scoops triage, and the TL;DR framing.Anchor on purpose. Read the research context from $ARGUMENTS.
Get GTM context. Call get_gtm_context to retrieve your organization's offerings, ICP, personas, competitors, and strategic priorities. Use this to frame findings throughout. If empty, proceed without — and omit the GTM Fit section.
Resolve the company.
companyId — do not call search_companies.search_companies with the appropriate field (companyWebsite for a domain, companyTicker for a ticker, companyName for a name) and extract companyId from the top match. If no confident match, surface the ambiguity to the user before continuing rather than guessing.Fetch in parallel (retrieval, not filtering). Treat each tool call as a context-retrieval step. Pull broadly now; decide what's relevant during synthesis. Steps that only need the companyId can run in parallel — enrich_companies, account_research, enrich_news (last 90 days, pageSize: 20), enrich_scoops (last 90 days, pageSize: 15), enrich_intent (see below), and find_similar_companies.
account_research query to the brief purpose. Don't pass a generic "tell me about this account" string. Instead, name the purpose and the priority themes — e.g., "Preparing for a QBR. Surface renewal status, contract dates, recent engagement, open expansion conversations, named champions and detractors, and any signs of competitive evaluation." The more context the better.enrich_intent with the companyId only — do not pre-filter by topic. The goal is to see what topics this company is actually expressing intent on, not to confirm hypotheses. Use signalScoreMin: 60 and sort: "-signalScore" so the response is ranked but unconstrained on subject matter. Filtering happens in step 5.Synthesize. Each retrieval is raw context — now decide what makes the brief, framed by the user's stated purpose. Apply these principles:
enrich_intent. Keep topics that map to the brief purpose, the priority themes, your GTM offerings, or that suggest a non-obvious signal worth flagging (e.g., a competitor's category, an adjacent buying motion). Drop topics that are noise or irrelevant to the purpose. If nothing meaningful remains, replace the table with a one-line note.account_research surfaces dates in the past (renewal, contract end, last activity, scheduled meeting), flag them as needing verification — could be active negotiation, stale CRM sync, or a missed milestone.find_similar_companies cohort spans inconsistent industries vs. the target, flag that the peer set is directional rather than exact.Write the exec summary last. Re-read the body, then write the TL;DR at the top. The Situation line must explicitly answer "why this brief, now" against the user's stated purpose — not just "who they are."
Brief purpose: [restate the user's research context in one line, or "general account intelligence (no purpose supplied)" if defaulted].
Situation. [2-4 sentences answering why this brief, now against the stated purpose: who they are, the dominant story now, where the relationship stands, and the specific signal(s) that make this purpose timely.]
Top 3 facts. Three most consequential data points across all sources.
Highest-leverage actions. 1-3 concrete actions, each pointing at a specific person, pilot, topic, or moment.
| Field | Value |
|---|---|
| Website | |
| Industry | |
| Employees | |
| Revenue | |
| HQ | |
| Type | (Public/Private) |
| Ticker | |
| Founded | |
| ZoomInfo ID |
Omit if no GTM context was returned.
Summarize account_research: relationship status, engagement, deal context, named contacts. If any surfaced dates are in the past, note them with a verification prompt (could be active negotiation, stale CRM sync, missed milestone, or closed-deal lag — recommend confirming with the account team). If dates fall within the next 30 days, surface them in the TL;DR instead.
Show only the topics retained after triage in step 5 — topics the company is actively expressing intent on that map to the brief purpose, priority themes, your offerings, or a non-obvious signal worth flagging.
| Topic | Signal Score | Audience Strength | Category | Signal Date |
|---|
Highlight the top 3 and tie them to your offerings or the user's stated context. Replace the table with a one-line note if nothing meaningful survived triage.
Group news by Financial / People / Product / General if 5+ items span categories; otherwise list flat. For each: headline, date, one-line summary, source URL. Then list scoops — group by Leadership Moves / Growth Signals / Strategic Moves / Risk Signals only if 4+ returned, otherwise flat. Call out timing opportunities (e.g., new CTO → vendor evaluation likely).
If the cohort's industries are inconsistent with the target, lead with a one-line caveat that peers are directional. Then show the top 10:
| # | Company | Industry | Employees | Revenue | Country | Similarity |
|---|
Note patterns: direct competitors vs. adjacent players vs. peers; how the target compares on size and market position.
3-5 bullets connecting the dots across sources, framed by the user's stated purpose. Then suggest concrete next actions — each must reference a specific person, pilot, deal, topic, or moment surfaced above, with a clear rationale tied to the brief purpose. No generic skill mentions or boilerplate. Omit any line that doesn't have a concrete target.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Searches MemPalace before answering questions about past work, people, projects, or prior decisions. Returns verbatim stored content instead of guessing from model memory.
npx claudepluginhub zoominfo/zoominfo-mcp-plugin --plugin zoominfo