customer-pulse-check

Q: How do I install customer-pulse-check?

Run npx skills add https://github.com/anthropics/knowledge-work-plugins --skill customer-pulse-check in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/customer-pulse-check/ (personal) or .claude/skills/customer-pulse-check/ (project).

by anthropics OfficialCode Quality & Workflow

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.

Installs: 1.3K
Last 24h: —
Trending rank: —
Security: Not audited

Install

Works with every agent the skills CLI supports.

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

01
Install
Run the command in your project. The CLI asks which agents to install for.
02
Describe the task
Ask your agent for something this skill covers. It loads customer-pulse-check automatically when relevant.
03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Run 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 date YYYY-MM-DD for 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.

FAQ

What does the customer-pulse-check skill do?

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.

How do I install customer-pulse-check?

Run npx skills add https://github.com/anthropics/knowledge-work-plugins --skill customer-pulse-check in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/customer-pulse-check/ (personal) or .claude/skills/customer-pulse-check/ (project).

Which AI agents can use customer-pulse-check?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is customer-pulse-check safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains customer-pulse-check?

It is published by anthropics in anthropics/knowledge-work-plugins, and it is an official skill from the maker of the technology it covers. It has 1,327 recorded installs.