customer-pulse
$
npx mdskill add anthropics/knowledge-work-plugins/customer-pulseAnalyzes customer sentiment across multiple channels to identify key themes and actionable insights
- Summarizes PayPal disputes, HubSpot tickets, email sentiment, and reviews into customer themes
- Uses PayPal, HubSpot, Gmail, and Intercom APIs to gather data
- Groups feedback into 3-5 themes with verbatim examples and prioritizes urgent actions
- Delivers a concise report with a 'do these three things this week' action list
SKILL.md
.github/skills/customer-pulseView on GitHub ↗
---
name: customer-pulse
version: 0.2.0
description: >
Aggregates PayPal disputes, HubSpot feedback and tickets, and email
sentiment (plus pasted or exported Google/Yelp reviews) into a themes
report with verbatim evidence and a "do these three things this week"
list. Use when the user asks how customers are feeling, for review
analysis, what people are saying, or about disputes.
---
# 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](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](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](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
- [reference/gotchas.md](reference/gotchas.md) — PayPal rate limits, HubSpot empty state, verbatim quote requirement, Gmail keyword drift
- [reference/examples/example-report.md](reference/examples/example-report.md) — full worked example output
More from anthropics/knowledge-work-plugins
- accessibility-reviewRun a WCAG 2.1 AA accessibility audit on a design or page. Trigger with "audit accessibility", "check a11y", "is this accessible?", or when reviewing a design for color contrast, keyboard navigation, touch target size, or screen reader behavior before handoff.
- account-research"Research a company using Common Room data. Triggers on 'research [company]', 'tell me about [domain]', 'pull up signals for [account]', 'what's going on with [company]', or any account-level question."
- analyzeAnswer data questions -- from quick lookups to full analyses. Use when looking up a single metric, investigating what's driving a trend or drop, comparing segments over time, or preparing a formal data report for stakeholders.
- architectureCreate or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.
- audit-supportSupport SOX 404 compliance with control testing methodology, sample selection, and documentation standards. Use when generating testing workpapers, selecting audit samples, classifying control deficiencies, or preparing for internal or external audits.
- brand-reviewReview content against your brand voice, style guide, and messaging pillars, flagging deviations by severity with specific before/after fixes. Use when checking a draft before it ships, when auditing copy for voice consistency and terminology, or when screening for unsubstantiated claims, missing disclaimers, and other legal flags.
- brand-voice-enforcement>
- briefGenerate contextual briefings for legal work — daily summary, topic research, or incident response. Use when starting your day and need a scan of legal-relevant items across email, calendar, and contracts, when researching a specific legal question across internal sources, or when a developing situation (data breach, litigation threat, regulatory inquiry) needs rapid context.
- build-dashboardBuild an interactive HTML dashboard with charts, filters, and tables. Use when creating an executive overview with KPI cards, turning query results into a shareable self-contained report, building a team monitoring snapshot, or needing multiple charts with filters in one browser-openable file.
- build-zoom-botBuild a Zoom meeting bot, recorder, or real-time media workflow. Use when joining meetings programmatically, processing live media or transcripts, or combining Meeting SDK, RTMS, and backend services.