CD market-customer-analysis
以ST分析（细分市场-目标客户-应用场景）、APPEALS需求七维度、KANO需求分类三大模型为核心，综合收敛出高价值细分市场与尚未被满足的蓝海机会，最终交付HTML交互式单页报告。当用户需要进行市场与客户分析、ST分析、市场细分、客户细分、目标客户、客户画像、应用场景、APPEALS、KANO、卡诺模型、需求分析、客户需求、刚需、痛点分析、爆款基因、蓝海市场、蓝海机会、未被满足需求、客户洞察、市场机会、客户需求分类、购买决策因素分析时使用。Triggers: market and customer analysis, ST analysis, market segmentation, targeting, customer persona, scenario analysis, APPEALS, KANO model, needs analysis, unmet needs, blue ocean, customer insight, market opportunity.
以ST分析（细分市场-目标客户-应用场景）、APPEALS需求七维度、KANO需求分类三大模型为核心，综合收敛出高价值细分市场与尚未被满足的蓝海机会，最终交付HTML交互式单页报告。当用户需要进行市场与客户分析、ST分析、市场细分、客户细分、目标客户、客户画像、应用场景、APPEALS、KANO、卡诺模型、需求分析、…
As a process D 35/100 · Unfinished process — References files that are not bundled: templates/report.html, references/st-model.md, references/appeals-model.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 4, column 14: description: 以ST分析（细分市场-目标客户-应用场景）、APPEALS需求七维度、KANO需求分类三大模型为核心，综合收敛出高价值细分市场与尚未… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: templates/report.html - warning
missing-refreference to a missing file: references/st-model.md - warning
missing-refreference to a missing file: references/appeals-model.md - warning
missing-refreference to a missing file: references/kano-model.md - warning
missing-refreference to a missing file: references/blue-ocean-strategy.md - note
frontmatter-keyunknown frontmatter key "display_name" - note
frontmatter-keyunknown frontmatter key "display_name_en" - note
frontmatter-keyunknown frontmatter key "agent_created"
Process rating: all ten parameters 35/100
- 0Tools and files. 5 referenced file(s) missing: templates/report.html, references/st-model.md, references/appeals-model.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 100Steps. 58 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1969 tokens
- 100Running it twice. No mutating operations
- low 11 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 444: enough signal without eating the budget
- +4Structure: 23 headings
- +3Step-by-step instructions: 58 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 47.