draft-follow-up

draft-follow-up is a skill for Claude Code from Zoominfo/zoominfo-mcp-plugin. It costs 116 tokens per session (732 once invoked), scanned A, original, MIT.

A skill for drafting a follow-up email after a call by identifying the commitments and next steps that were actually agreed. It can use connected calendar, email, or meeting data to find and review the call.

In plain words
What is it for?
Use it to thank attendees, summarize agreements, and confirm next steps for a specific call.
Why use it?
It reduces the effort of turning a conversation into an accurate, concise recap without guessing what was decided.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Part of the zoominfo plugin — 35 skills, 1 MCP server shipped together

Good fit Use it to thank attendees, summarize agreements, and confirm next steps for a specific call.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/zoominfo/zoominfo-mcp-plugin/draft-follow-up
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 draft-follow-up
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.

agentmods badge for draft-follow-up

README.md
[![agentmods](https://agentmods.dev/badge/skills/zoominfo/zoominfo-mcp-plugin/draft-follow-up/github.svg)](https://agentmods.dev/skills/zoominfo/zoominfo-mcp-plugin/draft-follow-up)
Your own site
<a href="https://agentmods.dev/skills/zoominfo/zoominfo-mcp-plugin/draft-follow-up"><img src="https://agentmods.dev/badge/skills/zoominfo/zoominfo-mcp-plugin/draft-follow-up/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.

agentmods 80×15 button for draft-follow-up

Your own site · 80×15
<a href="https://agentmods.dev/skills/zoominfo/zoominfo-mcp-plugin/draft-follow-up"><img src="https://agentmods.dev/badge/skills/zoominfo/zoominfo-mcp-plugin/draft-follow-up.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 116 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 732 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00116 $0.00732
Opus 5 $0.00058 $0.00366
Sonnet 5 $0.00023 $0.00146
Haiku 4.5 $0.00012 $0.00073

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

Security

Grade A, and why

draft-follow-up 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 10d 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/draft-follow-up/SKILL.md · 49 lines

How it starts

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

Draft Follow-Up

Turn what was said on a call into a tight follow-up email: thank, recap, and confirm next steps.

Prerequisites

browse_engagements (to find the call) is free but requires an active calendar/email/meeting integration; conversation_intelligence (to read it) requires at least one connected meeting or email source and consumes AI credits. If no conversation data exists for the call, say so rather than drafting from assumption.

Input

Provided via $ARGUMENTS:

  • Which call (optional) — an account and/or date. If omitted, the skill lists recent calls to pick from.
  • Tone / recipient (optional) — e.g. "warm", "more formal for the exec", "to the whole room". Defaults to friendly-professional, addressed to the primary external attendee.

Workflow

  1. Identify the call. browse_engagements filters by date and by company/contact ID, not by call name, so resolve any named account/contact first via search_companies / search_contacts, then call browse_engagements scoped to that ID and date window and pick the matching meeting. If nothing was named, present a numbered shortlist of recent calls and let the user pick before spending credits. Keep the engagement ID.
  2. Extract what was said. Run conversation_intelligence scoped to that engagement ID for the agreed next steps, commitments on each side, decisions, and any open questions to address in the note. Keep the query scoped to this one engagement.
  3. Confirm direction if ambiguous. If the recipient or tone is unclear, or the call surfaced sensitive points, pause and confirm with the user before drafting.
  4. Draft the email. Write a concise message: a one-line thanks, a 2-3 sentence recap, a clear list of next steps with owners and any dates, and a single call to action. Include only commitments the conversation actually supports; never invent an owner, a date, or a promise. Keep it skimmable.

Output Format

Subject: [specific, references the meeting or its outcome]

Read the full file on GitHub · 49 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.

  1. 10d ago First seen · 49 lines · 116 tokens per session scan A af9a756dc40d

Subscribe to this mod's changes

draft-follow-up is a skill published in the GitHub repository Zoominfo/zoominfo-mcp-plugin (7 stars, last pushed 6d ago), licensed MIT. It adds 116 tokens to every session and 732 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens