Customer Complaint Signal

Q: What does the Customer Complaint Signal AI skill do?

当用户在产品/服务改进上缺乏方向、想要驱动创新却苦于没有灵感来源、 或是忽视客户反馈的信号价值时，应调用此skill。 不适用于：已有明确创新方向的研发驱动型团队、紧急危机公关处理、 客户访谈只是走过场的合规要求。 Trigger信号："客户总是抱怨这个但不知道是不是真的重要"、"创新没有方向"、 "我们的产品迭代靠老板拍脑袋"、"问客户想要什么他们说不清楚"、 "竞争对手有什么动向我们总是最后一个知道"。

Community

ace3000chao

customer-complaint-signal

当用户在产品/服务改进上缺乏方向、想要驱动创新却苦于没有灵感来源、或是忽视客户反馈的信号价值时，应调用此skill。不适用于：已有明确创新方向的研发驱动型团队、紧急危机公关处理、客户访谈只是走过场的合规要求。 Trigger信号："客户总是抱怨这个但不知道是不是真的重要"、"创新没有方向"、 "我们的产品迭代靠老板拍脑袋"、"问客户想要什么他们说不清楚"、 "竞争对手有什么动向我们总是最后一个知道"。

Overview

Publisher	ace3000chao
Repository	`book2startup`
Skill name	`customer-complaint-signal`
Stars	93
Forks	14
Bundled files	1
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by ace3000chao on GitHub. Read the source before you install it.

Installation

Install the Customer Complaint Signal AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/ace3000chao/book2startup/tree/master/ScalingUp-skills/customer-complaint-signal
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/ace3000chao/book2startup/tree/master/ScalingUp-skills/customer-complaint-signal

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/ace3000chao/book2startup.git /tmp/book2startup
mkdir -p .claude/skills
cp -r /tmp/book2startup/ScalingUp-skills/customer-complaint-signal .claude/skills/customer-complaint-signal

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Customer Complaint Signal in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Customer Complaint Signal on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Customer Complaint Signal is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Customer Complaint Signal（客户投诉是最好的创新信号）

R — 原文 (Reading)

"Each senior leader formally ask customers questions that are more about gathering market intel, especially about competitors, than discerning whether they like your particular product."

— Verne Harnish, Scaling Up, 第1章 Overview

I — 方法论骨架 (Interpretation)

Harnish提出的市场情报收集原则与常规 wisdom 相反：与其问客户"喜不喜欢你的产品"，不如问"竞争对手在做什么"以及"客户在抱怨什么"。

为什么"喜不喜欢"这个问题价值有限？

客户的"喜欢"是滞后的情感指标——他们基于过去使用经验做判断，无法预见新可能的解决方案。更重要的是，客户通常不擅长表达他们真正需要什么（Henry Ford："如果你问顾客想要什么，他们会说是更快的马"）。

为什么"抱怨"比"喜欢"更有价值？

客户投诉是未被满足需求的直接信号。每一次投诉背后都藏着一个真实的问题，这个问题往往被投诉的表达方式掩盖了，但问题的存在是真实的。

两类高价值信号：

客户抱怨："你们的产品XXX太差了" → 背后是未被满足的需求
竞品动态：客户在流失给你的竞品 → 背后是竞品做对了什么

实操方法论：

高管亲自做客户访谈（每月至少2次），不是销售团队代劳
问题设计不是为了"满意度调研"，而是为了"情报收集"
特别关注客户提到的竞品——这比内部竞品分析更及时、更真实

A1 — 书中的应用 (Past Application)

案例 1: Intuit 的"客户在你家后院"深度访谈

问题: Intuit在1980年代是小型财务软件公司，不知道下一步产品方向
方法论的使用: CEO Scott Cook没有依赖传统调研公司，而是亲自去用户家里观察他们如何管理财务账目
- 发现：用户最头疼的不是"算账"，而是"找不到收据"
- 围绕"找不到收据"这个高频抱怨开发了QuickBooks
结论: 抱怨背后藏着产品方向，抱怨高频处即是市场机会所在
结果: QuickBooks成为小型企业财务软件市场领导者

案例 2: 某SaaS公司的"竞品流失预警"

问题: 销售团队发现好几个客户在续费时要求折扣，但没说原因；续费率开始下滑
方法论的使用: CEO没有直接打折，而是安排高管做流失客户访谈
- 发现：流失客户转向了竞品，原因是"竞品的报表功能更强"
- 内部研发评估：报表功能开发难度不大，但一直没有优先级
结论: 客户流失是竞品动态的预警信号，比任何内部报告都及时
结果: 快速迭代报表功能，续费率在Q3回升

案例 3: Amazon AWS 的"抱怨即需求"案例

问题: 2000年代初，开发者社区频繁抱怨IT基础设施部署复杂、成本高
方法论的使用: Bezos要求所有高管必须每月参加客户支持轮值，直接听客户投诉
- 发现：开发者抱怨的核心是"我不想管服务器，我只想用服务"
- 这直接导向了AWS的核心理念：基础设施即服务（IaaS）
结论: 大型创新往往源于听到了重复性、高频的抱怨，而非传统市场调研
结果: AWS开创了云计算行业，成为Amazon最赚钱的业务

A2 — 触发场景 (Future Trigger) ★

用户会在什么情境下需要这个 skill?

产品迭代方向不清晰 — 研发团队做了很多功能但客户使用率不高，不知道真正该做什么
竞争对手有新动作但反应总是慢半拍 — 内部竞品分析渠道有限，总是被市场推着走
客户满意度分数高但续费率低 — NPS和实际留存行为脱节，"满意但不买单"的假象
创新投入没有市场回报 — 做了很多创新项目但客户不买单，浪费了大量研发资源
高管与客户脱节 — 高管层不了解一线客户真实想法，只听汇报，信息层层衰减

语言信号 (用户的话里出现这些就应激活)

"客户总是抱怨这个但不知道是不是真的重要"
"创新没有方向"
"我们的产品迭代靠老板拍脑袋"
"竞争对手有什么动向我们总是最后一个知道"
"客户流失了但不知道为什么"
"调研说客户满意但他们还是走了"

与相邻 skill 的区分

与 routine-sets-you-free 的区别: routine-sets-you-free聚焦于建立客户反馈的收集节奏（如每周审视一次），本skill聚焦于"如何解读客户抱怨里的创新信号"。Routine解决"收集机制"，本skill解决"解读方法"。
与 data-driven-decisions 的区别: data-driven-decisions强调量化数据的收集和分析，本skill强调"定性信号"（抱怨、流失、口碑）的解读。两者互补：数据告诉你"发生了什么"，抱怨告诉你"为什么发生"。

E — 可执行步骤 (Execution)

当 skill 被激活后，agent 应按以下步骤执行:

建立高管客户访谈机制
- 完成标准：CEO和高管团队每月至少2次亲自做客户深度访谈（每次30-60分钟），非委托销售/客服代劳
- 访谈问题模板（3类）：
  - "最近有没有用竞争对手的产品？和我们的产品比哪里不同？"
  - "最近一次让你失望的经历是什么？"（聚焦抱怨而非满意度）
  - "你最希望我们改进的一件事是什么？"
- 判停条件：若高管团队无法抽出时间参与访谈，说明此问题优先级本身不够高
抱怨/竞品信号提炼
- 完成标准：每次访谈后提炼3个可操作的信号（抱怨/竞品/流失），录入"市场信号池"
- 分类：P1（影响当前收入的）/P2（影响未来竞争力的）/P3（长期观察项）
- 判停条件：若连续3个月没有P1信号，可能说明当前产品与市场匹配度较高，创新紧迫性低
将信号转化为产品/战略迭代
- 完成标准：P1信号在下一个产品迭代周期内必须有对应行动项
- 机制：月度产品-市场联席会议，用抱怨/竞品信号PK现有产品路线图
- 判停条件：若P1信号连续2个迭代周期没有落地，需要复盘是信号本身质量问题还是执行障碍

B — 边界 (Boundary) ★

不要在以下情况使用此 skill

紧急危机公关：客户正在公开投诉产品质量/安全事故，此时应该先处理危机而非"收集信号"——危机处理和信号收集是不同优先级的行动
过度迎合小众客户：某些高频抱怨来自小众人群，满足他们可能伤害大多数客户——需要评估抱怨背后的客户规模
技术团队的"完美主义"：工程师可能把客户正常的使用障碍解读为"抱怨"，需要区分"操作不便"和"战略信号"

作者在书中警告的失败模式

"调研幻觉"：做了大量客户调研但没有行动——Harnish强调"问问题不如去观察"，被动调研的质量远不如主动观察
抱怨≠需求：客户抱怨的是症状（"软件太慢"），但真正的问题是根因（"我的工作流需要多任务切换"）——只看表面抱怨容易开错药方

作者的盲点 / 时代局限

Harnish的框架假设CEO有时间亲自做客户访谈，但现代大企业CEO日程极度繁忙，这一实践的执行成本被低估了
数字时代的客户反馈渠道（社交媒体、App评分）产生的数据量远超个别访谈的颗粒度，AI辅助的反馈分析工具在书中未讨论

容易混淆的邻近方法论

NPS（净推荐值）：NPS是一个量化指标，关注"推荐意愿"；本skill关注"抱怨内容"——NPS告诉你客户整体情绪，抱怨分析告诉你具体改进方向
用户研究/UX Research：UX研究是系统性的用户行为研究方法论，本skill是CEO/高管的直接市场情报收集习惯——两者精度不同但互补

审计信息

验证通过: V1 ✓ / V2 ✓ / V3 ✓
测试通过率: 待填充
蒸馏时间: 2026-04-26

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

test-prompts.json3 KB

Frequently asked questions

What does the Customer Complaint Signal AI skill do?

Why use Customer Complaint Signal on TypingMind?

Because you install it once and use it with any model. Customer Complaint Signal is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Customer Complaint Signal in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/ace3000chao/book2startup/tree/master/ScalingUp-skills/customer-complaint-signal. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Customer Complaint Signal?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Customer Complaint Signal?

As many as you like. As long as a model supports skills, you can use Customer Complaint Signal with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Customer Complaint Signal AI skill free?

Yes. It is published on GitHub by ace3000chao under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Clawsweeper

openclaw

OrganizationPopular

Use for all ClawSweeper work: OpenClaw issue/PR sweep reports, repair jobs, cloud fix PRs, @clawsweeper maintainer mention commands, trusted ClawSweeper-reviewed autofix/automerge, GitHub Actions…

Openclaw Ci Limits

Manage OpenClaw GitHub Actions and Blacksmith CI capacity, runner-registration budgets, fanout caps, main-push single-flight, shard sizing, hosted-runner offload, queue health, and safe…

Openclaw Testing

Choose proportional OpenClaw tests and checks, diagnose failures, and route environment-sensitive or release proof to its owner.

Wizard

Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar…

Customer Complaint Signal

Overview