Exec Brief

作者 Zoominfod07402feb2b9无许可证收录于 2026年10月8日更新于 2026年10月8日

Produce a succinct one-pager for an executive dropping into a call with zero context. Blends account_research (who they are, deal state), conversation_intelligence (what has been discussed and what is open), and contact_research (who is in the room). Identify the account by ZoomInfo company ID (preferred) or name/domain (triggers a lookup); name the key attendees if known. Use when someone says "brief the VP for the Acme call", "exec one-pager for tomorrow", "my SVP is joining cold", or needs a tight pre-call brief for a senior stakeholder. Built to be read in two minutes.

AI 生成的概览

根据调研与对话数据,为高管生成一页式的通话前客户简报。

功能
为毫无背景信息即加入通话的高管生成简洁的一页式简报。它通过 ZoomInfo 公司 ID 或名称/域名确定客户,再整合客户调研、限定该客户的对话情报,以及针对已知参会人的联系人调研。输出采用固定格式:核心结论、当前进展、与会人员、高管应采取的行动,以及需要避开的雷区。
适用场景
适用于高层利益相关者需要一份紧凑的通话前简报时,例如为某客户通话向副总裁做简报,或高级副总裁临时加入的情况。其设计目标是约两分钟读完。
运行要求
需要 ZoomInfo 能力:account_research、contact_research 和 conversation_intelligence,其中后者需要至少一个已连接的会议或邮件来源。这些会消耗 AI 额度。该技能不附带脚本,仅为说明文档。

Exec Brief

One page an executive can absorb in the elevator: who, why now, where we stand, and the one thing to do in the room.

Prerequisites

conversation_intelligence requires at least one connected meeting or email source; account_research, contact_research, and conversation_intelligence consume AI credits. If no conversation data exists, build from research and note that the "where we stand" view is research-based only, pointing the user to their ZoomInfo admin.

Input

Provided via $ARGUMENTS:

  • Account (required) — ZoomInfo company ID (preferred), or a name/domain to resolve via search_companies.
  • The exec and the meeting (recommended) — who is being briefed, the meeting's purpose, and the attendees, so the one-pager is framed for their role.

Workflow

  1. Resolve the account (and key attendees, if named). Use ZoomInfo IDs directly, or resolve via search_companies / search_contacts.
  2. Gather, then compress. Run account_research (company + deal context) and account-scoped conversation_intelligence (recent state, open threads, commitments) in parallel. Run contact_research only for attendees the user named or that research surfaces as the key deal contacts; if no attendees are known, ask before spending contact_research credits rather than researching the whole account. Keep CI scoped to the account; it sees only the last few engagements.
  3. Write for an exec. Ruthlessly compress to one page. Lead with why this account matters and why now. Give the exec the single most useful thing to do or say, and the landmines to avoid. Cut firmographic detail that does not change how they show up. Every line earns its place; attribute the relationship claims.

Output Format

Exec brief — [Company]

Bottom line (2-3 sentences) — who they are, why this meeting matters, and where the relationship stands right now.

Where we stand — 2-3 bullets on the deal/relationship state and what is currently open (from CI + research).

In the room — the attendees in one line each: name, role, and what they care about.

Your move — the one thing for the exec to do or say to move this forward.

Landmines — one or two things to avoid (a sore point, a competitor, an unresolved issue), each with a reason.

Keep the whole thing to roughly one page. If a section has nothing high-signal, drop it rather than padding.

When there is no data

If conversation data is unavailable, build the one-pager from research and state that the current-state view is not grounded in recent conversations.

来源与署名

来源:Zoominfo/zoominfo-mcp-plugin位于skills/exec-brief提交d07402f

许可证: 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架