mcpField
C
customer-pulse

customer-pulse

github.com/anthropicsData & databases33.6k1.3k installsUpdated 1d ago
Repository

About customer-pulse

customer-pulse is a read-only skill for owners who want a concise view of recent customer feedback. It gathers evidence from PayPal, HubSpot, Gmail and Intercom, groups it into themes, and suggests three actions.

Key features

  1. 01Collects recent disputes, tickets, email and conversations
  2. 02Groups feedback into evidence-backed themes
  3. 03Includes verbatim customer quotes and signal counts
  4. 04Ranks themes and proposes three actions
  5. 05Accepts pasted Google and Yelp reviews

Use cases

  1. 01Reviewing customer sentiment over a chosen period
  2. 02Finding recurring issues across support channels
  3. 03Choosing weekly actions based on feedback

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/anthropics/knowledge-work-plugins --skill customer-pulse

After installing, type/customer-pulsein Claude Code to confirm it loaded.

Bundled filesreference/examples/example-report.mdreference/gotchas.md

Details

From the project README

Customer Pulse

Quick start

Ask: "How are customers feeling this month?"

Claude pulls disputes, tickets, email threads, and Intercom conversations for the last 30 days, groups them into 3–5 themes with verbatim evidence, and delivers a "do these 3 things this week" action list.

To include Google/Yelp reviews, paste them after triggering — or say "I have some reviews to add."

Workflow

  1. Set the date window. Default: last 30 days. If the user specifies a range, use it.

  2. Pull PayPal disputes. Fetch disputes opened in the window. If the PayPal API returns a rate-limit error, skip and add PayPal: rate-limited — not included to the Sources section. Do not retry; do not error. See reference/gotchas.md for the rate-limit pattern.

  3. Pull HubSpot tickets and feedback. Fetch open and recently closed tickets. If 0 tickets exist, record HubSpot tickets: 0 and continue — do not surface a warning.

  4. Pull Gmail threads. Search for threads in the window containing: refund cancel unhappy issue problem disappointed frustrated broken late slow wrong missing. Extract subject lines and 1–2 sentence excerpts per thread.

  5. Pull Intercom conversations. Call search_conversations to fetch open and recently closed conversations. Then call get_conversation for each conversation ID returned to access the full conversation_parts. Extract parts where author.type === 'user' — these are customer messages. Exclude parts where author.type is admin or bot.

  6. Accept pasted reviews (optional). If the user pastes Google or Yelp review text, include it in the source pool tagged as [Review]. No connector required.

  7. Extract themes. Group all evidence into 3–5 recurring themes. Each theme must include:

    • A one-sentence label (e.g., "Shipping delays causing repeat complaints")
    • 2–3 verbatim quotes with source tags: [PayPal], [HubSpot], [Gmail], [Intercom], or [Review]
    • A signal count (how many items touch this theme)

    Verbatim quotes are non-negotiable — never paraphrase. See reference/gotchas.md for the verbatim anti-pattern.

  8. Generate the "do these 3 things" list. Rank themes by signal count. Pick the top 3 and write one concrete, owner-actionable step per theme. Format as a numbered checklist.

  9. Deliver the report. Structure the output with these sections in order:

    • Header — H2 with "Customer Pulse" and the date range.
    • Sources pulled — Bullet list with signal counts per source (PayPal disputes, HubSpot tickets, Gmail threads, Intercom conversations, pasted reviews). Note any source that was rate-limited and skipped.
    • Themes — For each theme, show a bold numbered theme label with the signal count, followed by two verbatim quotes as blockquotes, each attributed to its source.
    • Do these 3 things this week — Numbered list of three concrete, owner-actionable steps, each tied to one of the top themes.

    For a complete worked example, see reference/examples/example-report.md.

Approval gates

This skill is read-only — it does not post, send, reply, or modify any records. No approval gate is required.

Reference

Comments

Markdown supported