New to Claude Skills? Learn how to install them →

anthropics on GitHub

Customer Pulse

OfficialFree

Aggregate customer feedback into actionable insights.

Get this skill

Free · Opens the source repo

What Customer Pulse does

Customer Pulse is a skill designed to help businesses understand customer sentiment by aggregating feedback from multiple sources. It pulls data from PayPal disputes, HubSpot tickets, Gmail threads, and Intercom conversations over a specified date range, typically the last 30 days. This skill is particularly useful for customer support teams and product managers who need to gauge customer feelings and identify recurring issues quickly.

When activated, Customer Pulse organizes the collected data into 3 to 5 themes, each accompanied by verbatim quotes from customers, ensuring that the feedback is presented accurately and without paraphrasing. This focus on direct quotes helps maintain the integrity of the customer voice, making it easier for teams to understand the specific concerns being raised. Additionally, users can enhance their reports by pasting Google or Yelp reviews, allowing for a more comprehensive view of customer sentiment.

The output generated by Customer Pulse is structured and actionable. It includes a summary of the sources used, highlights key themes identified from the feedback, and provides a prioritized list of three actionable steps for the team to take in response to the insights. This structured approach not only saves time but also directs attention to the most pressing customer issues, facilitating a more responsive and customer-centric business strategy.

Overall, Customer Pulse is an essential tool for any organization looking to leverage customer feedback effectively. By providing a clear picture of customer sentiment and actionable recommendations, it empowers teams to make informed decisions that enhance customer satisfaction and drive improvements in service delivery.

When to use it

Use this skill when you need to assess customer feelings based on recent feedback and disputes, especially for regular reporting and analysis.

When not to use it

This skill is not suitable for real-time customer interaction or for modifying records, as it is strictly read-only and does not engage with customers directly.

What you can build with it

Monthly Customer Sentiment Review

Use Customer Pulse at the end of each month to analyze customer feedback trends and adjust strategies accordingly.

Post-Launch Product Feedback Analysis

After launching a new product, employ Customer Pulse to gather and analyze customer feedback to identify areas of improvement.

Weekly Customer Support Insights

Integrate Customer Pulse into your weekly reports to provide your team with insights on customer issues and actionable next steps.

How to install Customer Pulse

View source

1. Install with the skills CLI

npx skills add anthropics/knowledge-work-plugins/customer-pulse --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by anthropics

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

Frequently asked questions about Customer Pulse

Similar skills