Update to ZoomInfo

{
  "name": "engagement-timeline",
  "description": "Build a timeline of engagements (meetings and emails) with an account or contact over a date range. Identify the account or contact by ZoomInfo ID (preferred), or by name or domain (triggers a lookup), or omit both to time-line your own recent engagements. Defaults to the last 90 days and can slide the window further back for a longer history. Returns a chronological timeline, a breakdown by engagement type, and a participant list with per-person engagement counts — and keeps each engagement's ID in context so you can immediately double-click any one to ask what was discussed. Use when someone asks \"when did we last meet with X\", \"how often have we engaged this account\", \"show me the history with this contact\", or wants a relationship timeline before a call.",
  "included_files": [],
  "skill_md_contents": "---\nname: engagement-timeline\ndescription: Build a timeline of engagements (meetings and emails) with an account or contact over a date range. Identify the account or contact by ZoomInfo ID (preferred), or by name or domain (triggers a lookup), or omit both to time-line your own recent engagements. Defaults to the last 90 days and can slide the window further back for a longer history. Returns a chronological timeline, a breakdown by engagement type, and a participant list with per-person engagement counts — and keeps each engagement's ID in context so you can immediately double-click any one to ask what was discussed. Use when someone asks \"when did we last meet with X\", \"how often have we engaged this account\", \"show me the history with this contact\", or wants a relationship timeline before a call.\n---\n\n# Engagement Timeline\n\nBuild a timeline of meetings and emails with an account or contact, then let the user double-click any engagement to see what was discussed.\n\n## Prerequisites\n\n`browse_engagements` reads from the calendar, email, and meeting providers connected to ZoomInfo. It requires at least one active calendar, email, or meeting integration in the workspace. If nothing is connected, `browse_engagements` returns no results — say so plainly and point the user to their ZoomInfo admin rather than implying there has been no contact.\n\n`browse_engagements` is free (no credits). The optional double-click step uses `conversation_intelligence`, which consumes AI credits.\n\n## Input\n\nProvided via `$ARGUMENTS`:\n\n- **Scope** — one of:\n  - An **account**: ZoomInfo company ID (preferred), or a company name/domain (resolve via `search_companies`).\n  - A **contact**: ZoomInfo contact ID (preferred), or a name + company (resolve via `search_contacts`).\n  - **Neither**: time-line the current user's own recent engagements across all accounts.\n- **How far back** (optional) — default is the last 90 days. \"Last quarter\", \"this year\", \"since January\", or a specific range all work; for anything beyond 90 days the window slides (see Workflow).\n- **Type** (optional) — meetings only, emails only, or both (default both).\n\n## Workflow\n\n1. **Resolve scope.** Use a supplied ZoomInfo ID directly as `zoominfoCompanyId` or `zoominfoContactId`. Otherwise resolve a name/domain via `search_companies` / `search_contacts` and confirm the top match if it is ambiguous. With no scope, call `browse_engagements` with no ID to get the user's own engagements.\n\n2. **Set the window.** `browse_engagements` accepts a date range up to 90 days wide (`engagementDateStart`, `engagementDateEnd`), ending no more than a month in the future. Default to the last 90 days. For a longer history, **slide the window backward in 90-day chunks** (e.g. 0-90 days ago, then 90-180, then 180-270) and merge the results, stopping when a chunk comes back empty or you reach the user's requested horizon. Tell the user when you are looking back across multiple windows so the wait is expected.\n\n3. **Pull engagements.** Call `browse_engagements` with the resolved scope, `engagementType` (default `EMAILS_AND_MEETINGS`), `sort: -chronological` (newest first), and `engagementLimit` up to 50 per call. Set `userIntent` to the user's actual request. If a window is full at the limit, narrow it and page rather than silently truncating.\n\n4. **Aggregate.** From the merged set compute: total engagements and the date range actually covered; a split by type (meetings vs emails); and a participant list with a count of engagements per person (name, and account where it differs). Retain each engagement's ID and the account/contact IDs in your working context — do **not** print raw IDs in the user-facing timeline, but keep them so the user can pick one to analyze.\n\n## Output Format\n\n### Summary\n\nOne line: who this is for, how many engagements over what actual date range, and the split (e.g. \"14 engagements with Acme over the last 88 days — 9 meetings, 5 emails\").\n\n### Timeline\n\nNewest first. One line per engagement: date, type, title/subject, and the key participants. Group by month if the range spans several months. Flag the most recent engagement and the gap since (e.g. \"last contact 12 days ago\").\n\n### Participants\n\nA short table, most-engaged first:\n\n| Person | Account | Engagements |\n|--------|---------|-------------|\n\nNote anyone who has gone quiet (engaged early in the window, absent recently) — that is often the signal worth acting on.\n\n### Double-click any engagement\n\nClose by offering the next step: the user can name any engagement above (\"the demo on the 14th\", \"the last email\") and you will pass its engagement ID to `conversation_intelligence` to answer what was discussed, what was decided, or what is still open. Keep CI scoped to that single engagement; do not use it to search the timeline by topic or to count mentions (it cannot).\n\n### When there is no data\n\nIf `browse_engagements` returns nothing, do not present an empty timeline as \"no relationship\". State that no engagements were found for the scope and window, that this may mean no connected integration covers them, and suggest widening the window or checking integration status with the ZoomInfo admin.\n"
}