{ "schemaVersion": "1.0", "item": { "slug": "customer-feedback", "name": "Customer Feedback", "source": "tencent", "type": "skill", "category": "开发工具", "sourceUrl": "https://clawhub.ai/JK-0001/customer-feedback", "canonicalUrl": "https://clawhub.ai/JK-0001/customer-feedback", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/customer-feedback", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=customer-feedback", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "SKILL.md" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-30T16:55:25.780Z", "expiresAt": "2026-05-07T16:55:25.780Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentDisposition": "attachment; filename=\"network-1.0.0.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/customer-feedback" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/customer-feedback", "agentPageUrl": "https://openagent3.xyz/skills/customer-feedback/agent", "manifestUrl": "https://openagent3.xyz/skills/customer-feedback/agent.json", "briefUrl": "https://openagent3.xyz/skills/customer-feedback/agent.md" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "Overview", "body": "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." }, { "title": "Step 1: Build Your Feedback Collection System", "body": "Feedback doesn't come automatically. You need channels to capture it consistently.\n\nFeedback channels to set up:\n\nChannelWhen to UseSetupIn-app feedback widgetCapture feedback at the moment of useTools: Canny, UserVoice, or custom formEmail surveysPeriodic check-ins (quarterly or post-milestone)Tools: Typeform, Google FormsCustomer interviewsDeep qualitative insightsManual scheduling (Calendly)Support ticketsCapture pain points and bugsTools: Intercom, Help Scout, ZendeskNPS surveysMeasure overall satisfactionTools: Delighted, SurveyMonkeyCancellation surveysUnderstand why people leaveTrigger on cancellation (see customer-retention)Feature request boardPublic place for customers to vote on ideasTools: Canny, ProductBoard\n\nMinimum viable feedback system (for solopreneurs):\n\nIn-app feedback button or email address for suggestions\nNPS survey sent quarterly to all customers\nCancellation survey on every churn\nMonthly customer interview with 2-3 active users" }, { "title": "Step 2: Run Customer Interviews That Uncover Truth", "body": "Interviews are the highest-value feedback method. But most people ask bad questions and get surface-level answers.\n\nInterview structure (30-45 min):" }, { "title": "Part 1: Context (5-10 min)", "body": "Understand their situation and workflow.\n\n\"Tell me about your role and what a typical day looks like.\"\n\"What were you doing before you started using [Product]?\"\n\"What made you look for a solution like ours?\"" }, { "title": "Part 2: Usage (10-15 min)", "body": "Understand how they use your product.\n\n\"Walk me through the last time you used [Product]. What were you trying to do?\"\n\"What do you love about [Product]?\"\n\"What's frustrating or confusing?\"\n\"If you could change one thing about it, what would it be?\"" }, { "title": "Part 3: Outcomes (10-15 min)", "body": "Understand the value they're getting (or not getting).\n\n\"What problem does [Product] solve for you?\"\n\"How do you measure success when using it?\"\n\"What would happen if you stopped using [Product] tomorrow?\"" }, { "title": "Part 4: Future (5 min)", "body": "Understand what they need next.\n\n\"What's the next big challenge you're facing that [Product] doesn't solve yet?\"\n\"If we could build one thing for you, what would make this 10x more valuable?\"\n\nInterview best practices:\n\nAsk open-ended questions (\"How do you...?\" not \"Do you like...?\")\nFollow up with \"Why?\" or \"Tell me more\" to go deeper\nListen 80%, talk 20%\nDon't sell or pitch during the interview — just learn\nRecord with permission (tools: Zoom, Otter.ai) so you can focus on listening\n\nWho to interview:\n\nPower users (use it most, see the most value) → understand best-case usage\nStruggling users (signed up but rarely use) → understand barriers\nChurned customers (canceled recently) → understand what failed\n\nGoal: 2-3 interviews per month minimum. More if you're making big product decisions." }, { "title": "Step 3: Measure Satisfaction with NPS", "body": "NPS (Net Promoter Score) is a simple way to measure overall satisfaction and loyalty.\n\nThe question:\n\n\"On a scale of 0-10, how likely are you to recommend [Product] to a friend or colleague?\"\n\nFollow-up:\n\n\"What's the main reason for your score?\"\n\nScoring:\n\n9-10 = Promoters (love your product, will refer others)\n7-8 = Passives (satisfied but not enthusiastic)\n0-6 = Detractors (unhappy, at risk of churn)\n\nNPS Calculation:\n\nNPS = % Promoters - % Detractors\n\nExample: 50% promoters, 10% detractors → NPS = +40\n\nBenchmarks:\n\nNPS > +50 = Excellent\nNPS +30 to +50 = Good\nNPS 0 to +30 = Needs work\nNPS < 0 = Critical (more detractors than promoters)\n\nWhen to send: Quarterly to all active customers. Or trigger after 30-90 days of usage.\n\nWhat to do with the data:\n\nFollow up with detractors (< 7): \"Thanks for the feedback. Can I ask what we could do better?\"\nCelebrate promoters (9-10): \"So glad to hear that! Would you be open to leaving a review?\"\nLook for patterns in the \"why\" responses → These are your action items" }, { "title": "Step 4: Organize and Analyze Feedback", "body": "Raw feedback is noise. Organized feedback is signal.\n\nHow to organize feedback (use a simple spreadsheet or tool like Canny, Notion):\n\nFEEDBACK | SOURCE | CATEGORY | CUSTOMER SEGMENT | PRIORITY | STATUS\n\"Need bulk export\" | In-app | Feature Request | Power users | High | Roadmap\n\"Onboarding is confusing\" | Interview | UX Issue | New users | High | In Progress\n\"Price is too high\" | Cancellation Survey | Pricing | SMB | Medium | Tracking\n\nCategories:\n\nFeature request (new functionality)\nBug or technical issue\nUX or usability issue\nPricing or billing\nDocs or support gap\n\nAnalysis workflow (monthly, 30 min):\n\nReview all feedback from the past month\nGroup by theme (which issues or requests are mentioned most?)\nIdentify the top 3 patterns\nCross-reference with product roadmap (see product-roadmap skill)\nDecide what to act on (see Step 5)\n\nLook for:\n\nHigh-frequency requests (10+ people ask for the same thing → strong signal)\nHigh-value customer requests (your top 20% of revenue — these carry more weight)\nEarly churn triggers (feedback from users who cancel in first 30 days → onboarding issues)" }, { "title": "Step 5: Decide What Feedback to Act On", "body": "Not all feedback is equal. Some is gold. Most is noise. Your job is to filter.\n\nFramework: Act on feedback if it meets 2+ of these criteria:\n\nHigh frequency: 10+ customers mention it\nHigh value: Requested by top 20% of customers (by revenue)\nStrategic fit: Aligns with your product vision and roadmap\nPrevents churn: Addressing it would keep at-risk customers\nQuick win: Low effort, high impact (can ship in < 1 week)\n\nExamples:\n\nFeedbackFrequencyValue SegmentStrategic FitAct?\"Add bulk export\"15 mentionsPower usersYes✅ Yes (high freq + strategic fit)\"Support Android app\"2 mentionsSMBNo❌ No (low freq + not strategic)\"Dashboard loads slowly\"30 mentionsAll segmentsYes✅ Yes (high freq + prevents churn)\"Can you integrate with [obscure tool]?\"1 mentionOne userNo❌ No (one-off request)\n\nHow to say no to feedback:\n\n\"Thanks for the suggestion! We're focused on [current theme] right now, so this\nwon't make it into the next few months. We'll keep it on the radar and revisit\nas priorities evolve.\"" }, { "title": "Step 6: Close the Feedback Loop", "body": "The fastest way to lose trust is to ask for feedback and then ignore it. Always close the loop.\n\nWhat closing the loop looks like:\n\nAcknowledge receipt: \"Thanks for the feedback — we've logged it and will review it.\"\nShare progress: If you act on it, tell them. \"Hey, remember you asked for X? We just shipped it!\"\nExplain why not: If you don't act on it, explain why. \"We considered X but decided to focus on Y because [reason].\"\n\nCommunication channels:\n\nIn-app changelog (announce new features and fixes)\nEmail updates (monthly or quarterly newsletter with what shipped)\nDirect outreach (for high-value customers who requested something you built)\n\nWhy this matters: When customers see their feedback leads to real changes, they feel heard and invested. They become advocates, not just users." }, { "title": "Step 7: Feedback Mistakes to Avoid", "body": "Not collecting feedback proactively. Waiting for customers to reach out means you only hear from the loudest or most frustrated. Set up regular channels.\nAsking 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.\nActing on every piece of feedback. You're not a feature factory. Filter ruthlessly.\nOnly collecting feedback from happy customers. Churned customers and struggling users have the most valuable insights.\nNot closing the loop. If you ask for feedback and never act on it or explain your decisions, people stop giving feedback.\nTreating all feedback equally. Feedback from your best customers (high LTV, engaged, aligned with your ICP) matters 10x more than feedback from low-fit customers." } ], "body": "Customer Feedback\nOverview\n\nCustomer 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.\n\nStep 1: Build Your Feedback Collection System\n\nFeedback doesn't come automatically. You need channels to capture it consistently.\n\nFeedback channels to set up:\n\nChannel\tWhen to Use\tSetup\nIn-app feedback widget\tCapture feedback at the moment of use\tTools: Canny, UserVoice, or custom form\nEmail surveys\tPeriodic check-ins (quarterly or post-milestone)\tTools: Typeform, Google Forms\nCustomer interviews\tDeep qualitative insights\tManual scheduling (Calendly)\nSupport tickets\tCapture pain points and bugs\tTools: Intercom, Help Scout, Zendesk\nNPS surveys\tMeasure overall satisfaction\tTools: Delighted, SurveyMonkey\nCancellation surveys\tUnderstand why people leave\tTrigger on cancellation (see customer-retention)\nFeature request board\tPublic place for customers to vote on ideas\tTools: Canny, ProductBoard\n\nMinimum viable feedback system (for solopreneurs):\n\nIn-app feedback button or email address for suggestions\nNPS survey sent quarterly to all customers\nCancellation survey on every churn\nMonthly customer interview with 2-3 active users\nStep 2: Run Customer Interviews That Uncover Truth\n\nInterviews are the highest-value feedback method. But most people ask bad questions and get surface-level answers.\n\nInterview structure (30-45 min):\n\nPart 1: Context (5-10 min)\n\nUnderstand their situation and workflow.\n\n\"Tell me about your role and what a typical day looks like.\"\n\"What were you doing before you started using [Product]?\"\n\"What made you look for a solution like ours?\"\n\nPart 2: Usage (10-15 min)\n\nUnderstand how they use your product.\n\n\"Walk me through the last time you used [Product]. What were you trying to do?\"\n\"What do you love about [Product]?\"\n\"What's frustrating or confusing?\"\n\"If you could change one thing about it, what would it be?\"\n\nPart 3: Outcomes (10-15 min)\n\nUnderstand the value they're getting (or not getting).\n\n\"What problem does [Product] solve for you?\"\n\"How do you measure success when using it?\"\n\"What would happen if you stopped using [Product] tomorrow?\"\n\nPart 4: Future (5 min)\n\nUnderstand what they need next.\n\n\"What's the next big challenge you're facing that [Product] doesn't solve yet?\"\n\"If we could build one thing for you, what would make this 10x more valuable?\"\n\n\nInterview best practices:\n\nAsk open-ended questions (\"How do you...?\" not \"Do you like...?\")\nFollow up with \"Why?\" or \"Tell me more\" to go deeper\nListen 80%, talk 20%\nDon't sell or pitch during the interview — just learn\nRecord with permission (tools: Zoom, Otter.ai) so you can focus on listening\n\nWho to interview:\n\nPower users (use it most, see the most value) → understand best-case usage\nStruggling users (signed up but rarely use) → understand barriers\nChurned customers (canceled recently) → understand what failed\n\nGoal: 2-3 interviews per month minimum. More if you're making big product decisions.\n\nStep 3: Measure Satisfaction with NPS\n\nNPS (Net Promoter Score) is a simple way to measure overall satisfaction and loyalty.\n\nThe question:\n\n\"On a scale of 0-10, how likely are you to recommend [Product] to a friend or colleague?\"\n\n\nFollow-up:\n\n\"What's the main reason for your score?\"\n\n\nScoring:\n\n9-10 = Promoters (love your product, will refer others)\n7-8 = Passives (satisfied but not enthusiastic)\n0-6 = Detractors (unhappy, at risk of churn)\n\nNPS Calculation:\n\nNPS = % Promoters - % Detractors\n\n\nExample: 50% promoters, 10% detractors → NPS = +40\n\nBenchmarks:\n\nNPS > +50 = Excellent\nNPS +30 to +50 = Good\nNPS 0 to +30 = Needs work\nNPS < 0 = Critical (more detractors than promoters)\n\nWhen to send: Quarterly to all active customers. Or trigger after 30-90 days of usage.\n\nWhat to do with the data:\n\nFollow up with detractors (< 7): \"Thanks for the feedback. Can I ask what we could do better?\"\nCelebrate promoters (9-10): \"So glad to hear that! Would you be open to leaving a review?\"\nLook for patterns in the \"why\" responses → These are your action items\nStep 4: Organize and Analyze Feedback\n\nRaw feedback is noise. Organized feedback is signal.\n\nHow to organize feedback (use a simple spreadsheet or tool like Canny, Notion):\n\nFEEDBACK | SOURCE | CATEGORY | CUSTOMER SEGMENT | PRIORITY | STATUS\n\"Need bulk export\" | In-app | Feature Request | Power users | High | Roadmap\n\"Onboarding is confusing\" | Interview | UX Issue | New users | High | In Progress\n\"Price is too high\" | Cancellation Survey | Pricing | SMB | Medium | Tracking\n\n\nCategories:\n\nFeature request (new functionality)\nBug or technical issue\nUX or usability issue\nPricing or billing\nDocs or support gap\n\nAnalysis workflow (monthly, 30 min):\n\nReview all feedback from the past month\nGroup by theme (which issues or requests are mentioned most?)\nIdentify the top 3 patterns\nCross-reference with product roadmap (see product-roadmap skill)\nDecide what to act on (see Step 5)\n\nLook for:\n\nHigh-frequency requests (10+ people ask for the same thing → strong signal)\nHigh-value customer requests (your top 20% of revenue — these carry more weight)\nEarly churn triggers (feedback from users who cancel in first 30 days → onboarding issues)\nStep 5: Decide What Feedback to Act On\n\nNot all feedback is equal. Some is gold. Most is noise. Your job is to filter.\n\nFramework: Act on feedback if it meets 2+ of these criteria:\n\nHigh frequency: 10+ customers mention it\nHigh value: Requested by top 20% of customers (by revenue)\nStrategic fit: Aligns with your product vision and roadmap\nPrevents churn: Addressing it would keep at-risk customers\nQuick win: Low effort, high impact (can ship in < 1 week)\n\nExamples:\n\nFeedback\tFrequency\tValue Segment\tStrategic Fit\tAct?\n\"Add bulk export\"\t15 mentions\tPower users\tYes\t✅ Yes (high freq + strategic fit)\n\"Support Android app\"\t2 mentions\tSMB\tNo\t❌ No (low freq + not strategic)\n\"Dashboard loads slowly\"\t30 mentions\tAll segments\tYes\t✅ Yes (high freq + prevents churn)\n\"Can you integrate with [obscure tool]?\"\t1 mention\tOne user\tNo\t❌ No (one-off request)\n\nHow to say no to feedback:\n\n\"Thanks for the suggestion! We're focused on [current theme] right now, so this\nwon't make it into the next few months. We'll keep it on the radar and revisit\nas priorities evolve.\"\n\nStep 6: Close the Feedback Loop\n\nThe fastest way to lose trust is to ask for feedback and then ignore it. Always close the loop.\n\nWhat closing the loop looks like:\n\nAcknowledge receipt: \"Thanks for the feedback — we've logged it and will review it.\"\nShare progress: If you act on it, tell them. \"Hey, remember you asked for X? We just shipped it!\"\nExplain why not: If you don't act on it, explain why. \"We considered X but decided to focus on Y because [reason].\"\n\nCommunication channels:\n\nIn-app changelog (announce new features and fixes)\nEmail updates (monthly or quarterly newsletter with what shipped)\nDirect outreach (for high-value customers who requested something you built)\n\nWhy this matters: When customers see their feedback leads to real changes, they feel heard and invested. They become advocates, not just users.\n\nStep 7: Feedback Mistakes to Avoid\nNot collecting feedback proactively. Waiting for customers to reach out means you only hear from the loudest or most frustrated. Set up regular channels.\nAsking 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.\nActing on every piece of feedback. You're not a feature factory. Filter ruthlessly.\nOnly collecting feedback from happy customers. Churned customers and struggling users have the most valuable insights.\nNot closing the loop. If you ask for feedback and never act on it or explain your decisions, people stop giving feedback.\nTreating all feedback equally. Feedback from your best customers (high LTV, engaged, aligned with your ICP) matters 10x more than feedback from low-fit customers." }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/JK-0001/customer-feedback", "publisherUrl": "https://clawhub.ai/JK-0001/customer-feedback", "owner": "JK-0001", "version": "0.1.0", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/customer-feedback", "downloadUrl": "https://openagent3.xyz/downloads/customer-feedback", "agentUrl": "https://openagent3.xyz/skills/customer-feedback/agent", "manifestUrl": "https://openagent3.xyz/skills/customer-feedback/agent.json", "briefUrl": "https://openagent3.xyz/skills/customer-feedback/agent.md" } }