ClaudeSuperPower
SubmitLog in

email-thread-summarizer

Skill

Summarize a long email thread into its current state, the decisions and key points, and the open questions. Finds the thread with browse_engagements (emails), then uses conversation_intelligence with includeContent to read the actual thread body. Name the account, contact, or subject if you know it,

0Writing

Install

git clone https://github.com/Zoominfo/zoominfo-mcp-plugin.git ~/.claude/skills/email-thread-summarizer

What is email-thread-summarizer?

Summarize a long email thread into its current state, the decisions and key points, and the open questions. Finds the thread with browse_engagements (emails), then uses conversation_intelligence with includeContent to read the actual thread body. Name the account, contact, or subject if you know it, or let the skill list recent threads to pick from. Use when someone says "summarize this email thread", "what's the state of the Acme thread", "catch me up on this email chain", or faces a long back-and-forth before replying. Summarizes one thread at a time.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~140 tokens of context used while enabled, before you invoke anything

Documentation

README · ~2 min read

Email Thread Summarizer

Collapse a long email chain into what matters: where it stands, what was decided, and what is still open.

Prerequisites

browse_engagements (to find the thread) requires a connected email integration; conversation_intelligence (to read the body) requires at least one connected email source and consumes AI credits. If the thread's content is not available to read, say so rather than guessing at its contents.

Input

Provided via $ARGUMENTS:

  • Which thread (optional) — an account, contact, or subject. If omitted, the skill lists recent email threads to pick from.
  • Emphasis (optional) — e.g. "what do they need from me", "just the decisions". Shapes the output.

Workflow

  1. Find the thread. Call browse_engagements with engagementType: EMAILS (scoped to the account/contact if known, sort: -chronological). If the target is ambiguous, present a short numbered shortlist (subject, participants, date) and let the user pick before spending credits. Keep the chosen engagement ID.

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.

Subagents

All subagents →

claude-security

The dedicated Claude Security orchestrator. Hand it an unattended job — "fully scan this repository and patch what you find; I understand it will use a lot of tokens" — and it runs the whole thing itself: capturing the revision, driving the multi-agent scan through the claude-security:scan workflow,

32.8K stars

agent-sdk-verifier-ts

Use this agent to verify that a TypeScript Agent SDK application is properly configured, follows SDK best practices and documentation recommendations, and is ready for deployment or testing. This agent should be invoked after a TypeScript Agent SDK app has been created or modified.

32.8K stars

comment-analyzer

Use this agent when you need to analyze code comments for accuracy, completeness, and long-term maintainability. This includes (1) after generating large documentation comments or docstrings, (2) before finalizing a pull request that adds or modifies comments, (3) when reviewing existing comments fo

32.8K stars