- name
- headphone-review
- description
- Use this skill when the user wants a buyer-facing long review of a headphone, IEM, earbud, or TWS model by name. Use AskUserQuestion in option mode first for language and description mode, then turn multilingual reviews and official specs into a pure-Markdown article with a strong but concise disagreement section and more human-sounding prose.
Headphone Review
Use this skill when the user names a headphone, IEM, earbud, or TWS model and wants a buyer-facing long review: what it sounds like, who it fits, who should skip it, and where reviewers agree or disagree.
When web lookup is needed, also use $web-access or the environment's browsing tools.
Trigger Hints
- Model-name requests such as
WH-1000XM5,IE 900,Blessing 3,Susvara - Questions like
这耳机适合谁,什么声音,值不值得买,fit,sound signature,should I buy - Requests to aggregate multilingual reviews into one conclusion
Do not use this skill for pure repair, firmware, pairing, or EQ-only tasks unless the user also wants a buying summary.
Workflow
- Ask the missing preference questions first with
AskUserQuestionin option mode, not as free-form text.
Language options: 中文, English Description mode options: 客观（偏理性、直接）, 情绪化抽象（偏氛围、意象） Read rules/intake.md.
- Gather multilingual evidence and reduce it into facts, consensus, and uncertainty.
Read rules/research.md.
- Write the review in pure Markdown with the chosen language and description mode.
Read rules/output.md and rules/humanize.md.
- If you are validating sample outputs, score them against the eval rules.
Read rules/eval.md.
Done When
The review clearly answers:
- what it sounds like
- strengths and weaknesses
- who should buy it
- who should avoid it
- where reviewers disagree and why
- confidence level and evidence boundary