customer-empathy

Overview of customer-empathy skill

customer-empathy is a lightweight customer-thinking prompt skill that helps you pause before building and reason from the user’s point of view. It is best for product teams, founders, designers, and Customer Success operators who need clearer decisions about onboarding, UX, feature priorities, or messaging. The real job-to-be-done is not “write empathy copy”; it is to turn vague product work into a sharper answer to: who is this for, what are they trying to accomplish, and where is the biggest friction?

When customer-empathy is the right fit

Use the customer-empathy skill when you need a faster, more disciplined way to evaluate a change through customer value. It is especially useful for early-stage products, onboarding redesigns, support-driven product fixes, and feature planning where assumptions are still fuzzy. It is a good fit for customer-empathy for Customer Success because it centers on adoption blockers, perceived value, and the moments where customers decide whether to continue.

What makes customer-empathy different

This skill is not a generic brainstorming prompt. It pushes you to separate what the customer cares about from what the team cares about, then translate that into practical product choices. The value is in the structure: role, context, desired outcome, emotional state, friction, and “magic” moments that create confidence. That makes the output more decision-useful than a broad “think like a user” prompt.

When not to use it

If you already have strong customer research, this skill should refine it rather than replace it. It is not a substitute for interviews, analytics, or support ticket analysis. Skip it when you need implementation specs, brand copy, or technical architecture; customer-empathy is meant to improve the problem framing first.

How to Use customer-empathy skill

Install customer-empathy in your workflow

Use the customer-empathy install command in your Claude Code skills workflow, then keep the skill available for product and support-related tasks. A typical install looks like npx skills add rameerez/claude-code-startup-skills --skill customer-empathy. After install, load the skill before asking for strategy, UX critique, onboarding copy, or prioritization help so the model has an explicit empathy framework to follow.

Feed it a real decision, not a vague topic

The customer-empathy usage works best when you provide a concrete situation: the user segment, the product area, the action you want them to take, and the friction you suspect. Strong prompts name the customer and the job. For example: “Use customer-empathy to analyze first-time activation for small agency admins who connected their account but stopped before inviting teammates. Identify what they care about, what they may not understand, and the fastest path to value.” That gives the skill something operational to reason about.

Read these files first

Start with SKILL.md to understand the exercise structure and then inspect any repository context that explains how the skill is intended to be used. In this repo, the key file is the skill body itself; there are no supporting scripts, references, or extra rules folders. That means the customer-empathy guide is intentionally simple, so the main job is to adapt the question prompts to your own product context rather than searching for hidden implementation details.

A practical prompt pattern

A useful input pattern is: customer segment + scenario + desired outcome + known blocker + output format. For example: “Apply customer-empathy to enterprise trial users who have completed signup but not created a project. Summarize their mental state, top concerns, what they do not care about, and the single best action to help them reach value.” This structure usually produces better results than asking for generic empathy notes because it anchors the skill to a real adoption problem.

customer-empathy skill FAQ

Is customer-empathy only for Customer Success?

No. customer-empathy for Customer Success is a strong use case, but the skill also fits product management, UX, onboarding, lifecycle messaging, and support-led product improvement. Any work that depends on understanding customer motivation, confusion, or perceived value can benefit from it.

Do I need research data to use it well?

You do not need a full research pack, but the skill works better when you can supply even rough evidence: a persona, a support theme, an analytics drop-off point, or a common objection. Without that, the output may still be useful, but it will be more hypothetical. If you have customer quotes or usage data, include them to reduce guesswork.

How is this different from a normal prompt?

A normal prompt can ask for empathy once; the customer-empathy skill gives you a repeatable structure for asking the right questions in the right order. That matters when you want consistent output across different product areas or team members. It is less about creativity and more about forcing better framing before action.

Is the customer-empathy skill beginner-friendly?

Yes. The prompts are simple and the sections are easy to apply even if you are not a product expert. The main beginner mistake is keeping the request too broad. If you name the customer, the step in the journey, and the obstacle, the customer-empathy install is easy to use and usually produces more actionable guidance.

How to Improve customer-empathy skill

Make the customer segment narrower

The strongest results come from specific customer definitions, not “users” in general. Instead of asking about all customers, describe the exact person and situation: “new nonprofit admins importing donor data on day one” or “paid users trying to get their team to adopt the product after solo setup.” Narrow inputs make the customer-empathy skill easier to ground in real behavior.

Add friction, stakes, and desired success

The model will be more useful if you tell it what is blocked and what success looks like from the customer’s side. Include the moment where they stall, what they may fear, and the outcome they actually want. This helps the skill move beyond surface-level empathy into adoption design, which is where customer-empathy for Customer Success becomes most valuable.

Ask for a decision-shaped output

Improve the customer-empathy usage by requesting an output that can drive action: top customer need, biggest confusion, key reassurance, and the single next move. If the first output is too abstract, ask it to rewrite the answer as onboarding priorities, in-app guidance, or support follow-up recommendations. That keeps the skill tied to decisions, not just observations.

Iterate with real evidence after the first pass

After the first response, feed back one real customer quote, a support pattern, or a conversion drop-off point and ask the skill to revise. This is the fastest way to improve accuracy because it replaces assumptions with evidence. For the best customer-empathy guide outcomes, use the first pass to frame the problem and the second pass to pressure-test it against actual customer signals.