A daily meeting briefing that reviews your schedule and summarizes the current state of each external meeting, its main focus, and needed follow-ups.

Use it to prepare for customer meetings, choose a goal for each conversation, and track follow-up work. It can cover today, another day, or selected meetings.

It removes the need to gather account, contact, and past-conversation details separately before starting your day.

daily-brief — Skill for Claude Code by Zoominfo

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add Zoominfo/zoominfo-mcp-plugin --skill daily-brief

Clone the repo

git clone --depth 1 https://github.com/Zoominfo/zoominfo-mcp-plugin

Made for: Claude Code.

Or install zoominfo, the plugin that ships this one along with the rest of its 35 skills, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/zoominfo/zoominfo-mcp-plugin/daily-brief/github.svg)](https://agentmods.dev/skills/zoominfo/zoominfo-mcp-plugin/daily-brief)

Your own site

<a href="https://agentmods.dev/skills/zoominfo/zoominfo-mcp-plugin/daily-brief"><img src="https://agentmods.dev/badge/skills/zoominfo/zoominfo-mcp-plugin/daily-brief/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/zoominfo/zoominfo-mcp-plugin/daily-brief"><img src="https://agentmods.dev/badge/skills/zoominfo/zoominfo-mcp-plugin/daily-brief.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 130 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 941 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00130	$0.00941
Opus 5	$0.00065	$0.00470
Sonnet 5	$0.00026	$0.00188
Haiku 4.5	$0.00013	$0.00094

Measured 11d ago against content hash 26c36b99ade4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

daily-brief scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/daily-brief/SKILL.md · 48 lines

How it starts

The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Daily Brief

Give the user a fast, per-meeting rundown of their day: where each account stands, the one thing to drive, and what to follow up on.

Prerequisites

browse_engagements (the schedule) requires an active calendar/meeting integration; conversation_intelligence requires at least one connected meeting or email source. account_research, contact_research, and conversation_intelligence all consume AI credits, and this skill calls them once per meeting — so a full day of meetings can be credit-heavy. Confirm scope before fanning out (see Workflow step 2). If no integration is connected, report that and point the user to their ZoomInfo admin.

Input

Provided via $ARGUMENTS:

Day (optional) — defaults to today. "Tomorrow", "Monday", or a date all work.
Filter (optional) — e.g. "customer meetings only", "just external", a specific account. Defaults to external meetings (ones with non-colleague participants).

Workflow

Get the schedule. Call browse_engagements with a window covering the target day (engagementType: MEETINGS, sort: chronological). Drop internal-only meetings (no external participants) unless the user asked for everything.
Size it and confirm. Count the external meetings. Each one fans out three AI-credit calls (account_research, contact_research, conversation_intelligence), so the spend adds up quickly — even a handful of meetings is a non-trivial number of AI credits. If there are more than a few (roughly 3+), tell the user the meeting count, note that each is researched with several AI-credit calls, and offer to scope down (external customer meetings only, the most important few, or a named subset) before proceeding. This pause keeps a packed calendar from turning into a large unprompted credit spend.
Research each meeting (parallel, bounded). For the in-scope meetings, fan out per meeting: account_research (kept light — this is a day view, not a full brief), contact_research for the attendees, and conversation_intelligence scoped to the account or the specific engagement for recent state and open items. Parallelize across meetings, but respect the volume you confirmed in step 2. Keep each CI query scoped to one account or engagement; CI cannot search by topic, filter by call type, or count mentions, and only reasons over the last few engagements — base each card on what it returns, not on it having full history.

Read the full file on GitHub · 48 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

11d ago First seen · 48 lines · 130 tokens per session scan A 26c36b99ade4

Subscribe to this mod's changes

daily-brief is a skill published in the GitHub repository Zoominfo/zoominfo-mcp-plugin (7 stars, last pushed 7d ago), licensed MIT. It adds 130 tokens to every session and 941 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Productivity

orbit-notion

Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…

nexu-io/open-design · 117 tokens

Cortex

Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…

danielmiessler/LifeOS · 196 tokens

pinchtab-mcp

Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.

pinchtab/pinchtab · 52 tokens

daily-brief