← 返回 Skills 市场
jk-0001

Customer Feedback

作者 Jatin Khatri · GitHub ↗ · v0.1.0
cross-platform ✓ 安全检测通过
1051
总下载
0
收藏
7
当前安装
1
版本数
在 OpenClaw 中安装
/install customer-feedback
功能描述
Collect, analyze, and act on customer feedback to improve your product and business. Use when building feedback systems, running customer interviews, analyzing feature requests, measuring satisfaction (NPS, CSAT), or closing the feedback loop. Covers feedback collection methods, interview techniques, analysis frameworks, and how to decide what feedback to act on. Trigger on "customer feedback", "collect feedback", "user research", "customer interviews", "NPS", "feature requests", "feedback system".
使用说明 (SKILL.md)

Customer Feedback

Overview

Customer feedback is your compass. It tells you what's working, what's broken, and what to build next. But most solopreneurs either ignore feedback (and build the wrong things) or blindly implement every suggestion (and lose focus). This playbook shows you how to collect high-quality feedback, analyze it systematically, and act on what matters.


Step 1: Build Your Feedback Collection System

Feedback doesn't come automatically. You need channels to capture it consistently.

Feedback channels to set up:

Channel When to Use Setup
In-app feedback widget Capture feedback at the moment of use Tools: Canny, UserVoice, or custom form
Email surveys Periodic check-ins (quarterly or post-milestone) Tools: Typeform, Google Forms
Customer interviews Deep qualitative insights Manual scheduling (Calendly)
Support tickets Capture pain points and bugs Tools: Intercom, Help Scout, Zendesk
NPS surveys Measure overall satisfaction Tools: Delighted, SurveyMonkey
Cancellation surveys Understand why people leave Trigger on cancellation (see customer-retention)
Feature request board Public place for customers to vote on ideas Tools: Canny, ProductBoard

Minimum viable feedback system (for solopreneurs):

  1. In-app feedback button or email address for suggestions
  2. NPS survey sent quarterly to all customers
  3. Cancellation survey on every churn
  4. Monthly customer interview with 2-3 active users

Step 2: Run Customer Interviews That Uncover Truth

Interviews are the highest-value feedback method. But most people ask bad questions and get surface-level answers.

Interview structure (30-45 min):

Part 1: Context (5-10 min)

Understand their situation and workflow.

"Tell me about your role and what a typical day looks like."
"What were you doing before you started using [Product]?"
"What made you look for a solution like ours?"

Part 2: Usage (10-15 min)

Understand how they use your product.

"Walk me through the last time you used [Product]. What were you trying to do?"
"What do you love about [Product]?"
"What's frustrating or confusing?"
"If you could change one thing about it, what would it be?"

Part 3: Outcomes (10-15 min)

Understand the value they're getting (or not getting).

"What problem does [Product] solve for you?"
"How do you measure success when using it?"
"What would happen if you stopped using [Product] tomorrow?"

Part 4: Future (5 min)

Understand what they need next.

"What's the next big challenge you're facing that [Product] doesn't solve yet?"
"If we could build one thing for you, what would make this 10x more valuable?"

Interview best practices:

  • Ask open-ended questions ("How do you...?" not "Do you like...?")
  • Follow up with "Why?" or "Tell me more" to go deeper
  • Listen 80%, talk 20%
  • Don't sell or pitch during the interview — just learn
  • Record with permission (tools: Zoom, Otter.ai) so you can focus on listening

Who to interview:

  • Power users (use it most, see the most value) → understand best-case usage
  • Struggling users (signed up but rarely use) → understand barriers
  • Churned customers (canceled recently) → understand what failed

Goal: 2-3 interviews per month minimum. More if you're making big product decisions.


Step 3: Measure Satisfaction with NPS

NPS (Net Promoter Score) is a simple way to measure overall satisfaction and loyalty.

The question:

"On a scale of 0-10, how likely are you to recommend [Product] to a friend or colleague?"

Follow-up:

"What's the main reason for your score?"

Scoring:

  • 9-10 = Promoters (love your product, will refer others)
  • 7-8 = Passives (satisfied but not enthusiastic)
  • 0-6 = Detractors (unhappy, at risk of churn)

NPS Calculation:

NPS = % Promoters - % Detractors

Example: 50% promoters, 10% detractors → NPS = +40

Benchmarks:

  • NPS > +50 = Excellent
  • NPS +30 to +50 = Good
  • NPS 0 to +30 = Needs work
  • NPS \x3C 0 = Critical (more detractors than promoters)

When to send: Quarterly to all active customers. Or trigger after 30-90 days of usage.

What to do with the data:

  • Follow up with detractors (\x3C 7): "Thanks for the feedback. Can I ask what we could do better?"
  • Celebrate promoters (9-10): "So glad to hear that! Would you be open to leaving a review?"
  • Look for patterns in the "why" responses → These are your action items

Step 4: Organize and Analyze Feedback

Raw feedback is noise. Organized feedback is signal.

How to organize feedback (use a simple spreadsheet or tool like Canny, Notion):

FEEDBACK | SOURCE | CATEGORY | CUSTOMER SEGMENT | PRIORITY | STATUS
"Need bulk export" | In-app | Feature Request | Power users | High | Roadmap
"Onboarding is confusing" | Interview | UX Issue | New users | High | In Progress
"Price is too high" | Cancellation Survey | Pricing | SMB | Medium | Tracking

Categories:

  • Feature request (new functionality)
  • Bug or technical issue
  • UX or usability issue
  • Pricing or billing
  • Docs or support gap

Analysis workflow (monthly, 30 min):

  1. Review all feedback from the past month
  2. Group by theme (which issues or requests are mentioned most?)
  3. Identify the top 3 patterns
  4. Cross-reference with product roadmap (see product-roadmap skill)
  5. Decide what to act on (see Step 5)

Look for:

  • High-frequency requests (10+ people ask for the same thing → strong signal)
  • High-value customer requests (your top 20% of revenue — these carry more weight)
  • Early churn triggers (feedback from users who cancel in first 30 days → onboarding issues)

Step 5: Decide What Feedback to Act On

Not all feedback is equal. Some is gold. Most is noise. Your job is to filter.

Framework: Act on feedback if it meets 2+ of these criteria:

  1. High frequency: 10+ customers mention it
  2. High value: Requested by top 20% of customers (by revenue)
  3. Strategic fit: Aligns with your product vision and roadmap
  4. Prevents churn: Addressing it would keep at-risk customers
  5. Quick win: Low effort, high impact (can ship in \x3C 1 week)

Examples:

Feedback Frequency Value Segment Strategic Fit Act?
"Add bulk export" 15 mentions Power users Yes ✅ Yes (high freq + strategic fit)
"Support Android app" 2 mentions SMB No ❌ No (low freq + not strategic)
"Dashboard loads slowly" 30 mentions All segments Yes ✅ Yes (high freq + prevents churn)
"Can you integrate with [obscure tool]?" 1 mention One user No ❌ No (one-off request)

How to say no to feedback:

"Thanks for the suggestion! We're focused on [current theme] right now, so this
won't make it into the next few months. We'll keep it on the radar and revisit
as priorities evolve."

Step 6: Close the Feedback Loop

The fastest way to lose trust is to ask for feedback and then ignore it. Always close the loop.

What closing the loop looks like:

  1. Acknowledge receipt: "Thanks for the feedback — we've logged it and will review it."
  2. Share progress: If you act on it, tell them. "Hey, remember you asked for X? We just shipped it!"
  3. Explain why not: If you don't act on it, explain why. "We considered X but decided to focus on Y because [reason]."

Communication channels:

  • In-app changelog (announce new features and fixes)
  • Email updates (monthly or quarterly newsletter with what shipped)
  • Direct outreach (for high-value customers who requested something you built)

Why this matters: When customers see their feedback leads to real changes, they feel heard and invested. They become advocates, not just users.


Step 7: Feedback Mistakes to Avoid

  • Not collecting feedback proactively. Waiting for customers to reach out means you only hear from the loudest or most frustrated. Set up regular channels.
  • Asking leading questions. "Would you like it if we added X?" is a bad question. People will say yes to be polite. Ask open-ended questions instead.
  • Acting on every piece of feedback. You're not a feature factory. Filter ruthlessly.
  • Only collecting feedback from happy customers. Churned customers and struggling users have the most valuable insights.
  • Not closing the loop. If you ask for feedback and never act on it or explain your decisions, people stop giving feedback.
  • Treating all feedback equally. Feedback from your best customers (high LTV, engaged, aligned with your ICP) matters 10x more than feedback from low-fit customers.
安全使用建议
This skill is a written playbook and appears coherent with its stated purpose — low technical risk. Before using it operationally: (1) ensure you obtain explicit consent before recording or storing interviews and follow applicable privacy laws (GDPR, CCPA); (2) vet and configure any third-party tools you use (Canny, Typeform, Zoom, Calendly, Otter.ai) and avoid embedding API keys or customer PII in public documents; (3) enforce minimal data retention and access controls for spreadsheets/Notion where feedback is stored and anonymize sensitive feedback when possible; (4) if you allow an agent to act autonomously with this skill, restrict its ability to send outreach (surveys, emails) without human review to avoid accidental contact or data leaks. Overall the skill is coherent and low-risk, but operational privacy and third-party tool configuration are the main items to check before use.
功能分析
Type: OpenClaw Skill Name: customer-feedback Version: 0.1.0 The skill bundle contains only a metadata file and a markdown document. The `SKILL.md` provides comprehensive, well-structured advice on customer feedback management. There is no executable code, no prompt injection attempts against the AI agent, no external resource fetching, and no indications of malicious intent or vulnerabilities. All content is informational and aligns with the stated purpose.
能力评估
Purpose & Capability
The name/description (customer feedback collection and analysis) matches the SKILL.md content. Recommended tools (Canny, Typeform, Calendly, Zoom, Otter.ai, Notion, spreadsheets) are appropriate for this purpose and no unrelated resources are requested.
Instruction Scope
The instructions are procedural and stay within feedback collection/analysis (interview scripts, NPS guidance, organizing feedback). They recommend using third-party services and recording interviews with permission — this is expected but raises data-privacy considerations (consent, storage, PII handling) which the user should address before operational use.
Install Mechanism
No install spec and no code files (instruction-only). Nothing will be written to disk or installed by the skill itself.
Credentials
The skill declares no required environment variables, credentials, or config paths. It does not request access to unrelated services or secrets.
Persistence & Privilege
always is false and the skill is user-invocable; it does not request persistent or elevated platform privileges beyond normal agent invocation.
如何使用
  1. 确保已安装 OpenClaw(本地或 Docker 部署)
  2. 在对话框中输入安装命令:/install customer-feedback
  3. 安装完成后,直接呼叫该 Skill 的名称或使用 /customer-feedback 触发
  4. 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
版本历史
v0.1.0
Initial release: customer-feedback skill for end-to-end feedback management. - Provides a complete playbook for collecting, analyzing, and acting on customer feedback. - Covers feedback channels, customer interview methods, and NPS measurement. - Offers frameworks for organizing, prioritizing, and responding to feature requests and user insights. - Designed for solopreneurs and small teams, with actionable best practices and tool recommendations.
元数据
Slug customer-feedback
版本 0.1.0
许可证
累计安装 7
当前安装数 7
历史版本数 1
常见问题

Customer Feedback 是什么?

Collect, analyze, and act on customer feedback to improve your product and business. Use when building feedback systems, running customer interviews, analyzing feature requests, measuring satisfaction (NPS, CSAT), or closing the feedback loop. Covers feedback collection methods, interview techniques, analysis frameworks, and how to decide what feedback to act on. Trigger on "customer feedback", "collect feedback", "user research", "customer interviews", "NPS", "feature requests", "feedback system". 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 1051 次。

如何安装 Customer Feedback?

在 OpenClaw 或 Claude Code 对话框中运行命令「/install customer-feedback」即可一键安装,无需额外配置。

Customer Feedback 是免费的吗?

是的,Customer Feedback 完全免费(开源免费),可自由下载、安装和使用。

Customer Feedback 支持哪些平台?

Customer Feedback 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(cross-platform)。

谁开发了 Customer Feedback?

由 Jatin Khatri(@jk-0001)开发并维护,当前版本 v0.1.0。

💬 留言讨论