Zhihu High-Engagement Answer Structurer

Problem This Skill Solves

This skill turns scattered opinions, personal experience, or business context into a Zhihu-style high-engagement answer structure, rather than generic Q&A. It targets Zhihu answers, opinion posts, story openings, and actionable how-to structures, focusing on the gap where the user has a point but the output feels thin, weakly argued, or useless beyond a first read. The result should be a reusable conclusion, body copy, notes, and self-check list.

How It Works

The skill starts with scene recognition to decide whether the user needs creation from zero, draft rewriting, checklist generation, concept explanation, option comparison, or diagnostic review. If context is missing, it first asks for audience, goal, existing material, local constraints such as platform/city/industry/role/time, and desired output format. It then applies localization using Chinese workflows and common platforms like WeChat, Lark, DingTalk, Tencent Docs, WPS, Taobao, Douyin, and Xiaohongshu, avoiding generic Western phrasing or placeholders like 'Company A / Product B'.

The main output should include:
- Position setup: break input into checkable fields; quantify where possible and explain judgment where not;
- Argument structure: produce paste-ready body content and avoid empty phrases like 'continue optimizing' or 'strengthen execution';
- Storytelling: add steps, boundary conditions, and common pitfalls;
- Save-worthy checklist: provide a checklist, review metrics, and risk controls;
- Risk review: flag false promises, speculation written as fact, and high-stakes areas such as law, medical, finance, government, or visa matters.

Boundaries and Cautions

It fits Chinese content creation where the deliverable must be directly usable, especially for Zhihu, WeChat Official Accounts, and Xiaohongshu. It should not fabricate personal experience, institutional data, or expert identity. If the user asks for illegal, deceptive, fraudulent, platform-bypassing, or regulatory-evasion content, the skill should refuse and provide a compliant alternative. The task ends when the output is usable and risk notes are complete, not when extra filler is added.