Customer Pulse Check Skill for Claude
Synthesizes themes from PayPal disputes, HubSpot tickets, and review exports into a top-3 fixable issues list with drafted response templates. Accepts optional since-date argument.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/anthropics/knowledge-work-plugins --skill customer-pulse-checkWhat it tells the agent to use
found in the instruction textThe instruction itself
7 sections, as written by the authorRun the customer voice synthesis. Pull feedback signals from all connected sources, identify the themes that are actually fixable, and produce drafted responses the owner can review and send.
Parse arguments:
--since(default: last 30 days) — start dateYYYY-MM-DDfor the lookback window
Step 1 — Gather feedback signals
Using the customer-pulse skill workflow:
- Pull PayPal disputes and chargebacks for the period: reason codes, amounts, resolution status.
- Pull HubSpot support tickets and conversation notes for the period.
- If review export files are available (Google Reviews CSV, Yelp export, etc.) in Files: read and parse them.
- Count total signals per source.
Step 2 — Theme extraction
Cluster all signals into recurring themes. For each theme:
- Count how many signals mention it
- Classify: Product quality / Delivery / Billing / Communication / Expectation mismatch / Other
- Rate impact: 🔴 High (revenue risk, churn) / 🟡 Medium / 🟢 Low
Step 3 — Top-3 fixable issues
Using the ticket-deflector skill workflow:
Select the top 3 themes by: frequency × impact rating. For each:
- State the issue in one sentence
- Explain the root cause (where evident)
- Suggest a specific operational fix
- Draft a customer response template
Response template format:
Subject: Re: {issue topic}
Hi {first name},
Thank you for reaching out. {Acknowledgment of their experience in 1-2 sentences}.
{What we're doing about it / what happened / resolution offered}.
{Next step or offer}.
{Sign-off}
Step 4 — Summary table
Format the output as:
Customer Voice — {date range}
Total signals: {n} ({PayPal disputes: n} | {HubSpot tickets: n} | {Reviews: n})
TOP 3 FIXABLE ISSUES
1. {Issue} ({frequency}) — {impact} — Fix: {one-line fix}
2. {Issue} ({frequency}) — {impact} — Fix: {one-line fix}
3. {Issue} ({frequency}) — {impact} — Fix: {one-line fix}
Connector failures
Run with whatever sources are connected — this command degrades gracefully. If PayPal is missing, skip dispute data and note "PayPal not connected — dispute data skipped." If HubSpot is missing, skip ticket data and note it. If no sources are connected at all, stop and tell the owner: "No feedback sources connected. Connect at least one of PayPal, HubSpot, or upload a review export CSV."
Approval gates
- Never send response emails automatically. Present drafts for owner review only.
- Never close HubSpot tickets or resolve PayPal disputes without explicit owner confirmation.
- Never include customer PII in the summary — use first name + last initial only.
Output
Present the summary table, then each response template. Ask the owner which templates they'd like to send, then wait for explicit approval before drafting the send.
Other skills for the same job
different authors, same section of the catalogue
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Set up Tailwind CSS v4 in Expo with react-native-css and NativeWind v5 for universal styling
Use Expo DOM components to run web code in a webview on native and as-is on web. Migrate web code to native incrementally.
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.
Low-level plotting library for full customization. Use when you need fine-grained control over every plot element, creating novel plot types, or integrating with specific scientific workflows. Export to PNG/PDF/SVG for publication. For quick statistical plots use seaborn; for interactive plots use plotly; for publication-ready multi-panel figures with journal styling, use scientific-visualization.
Statistical visualization with pandas integration. Use for quick exploration of distributions, relationships, and categorical comparisons with attractive defaults. Best for box plots, violin plots, pair plots, heatmaps. Built on matplotlib. For interactive plots use plotly; for publication styling use scientific-visualization.
Laboratory automation toolkit for controlling liquid handlers, plate readers, pumps, heater shakers, incubators, centrifuges, and analytical equipment. Use this skill when automating laboratory workflows, programming liquid handling robots (Hamilton STAR, Opentrons OT-2, Tecan EVO), integrating lab equipment, managing deck layouts and resources (plates, tips, containers), reading plates, or creating reproducible laboratory protocols. Applicable for both simulated protocols and physical hardware control.
How to use it
Take anthropics/customer-pulse-check from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.