Menu
Generate Zhihu article in the style of 22-庖丁解牛专题页-知乎图文终版.md
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when a project needs a standard .claude workspace initialized or repaired incrementally. This skill audits the existing .claude folder, adds missing files and directories without overwriting existing rules/skills/settings, and can optionally evolve the structure over time for the current project.
Use when the user wants to search GitHub repositories by keyword, inspect ranked candidates, compare likely matches, and optionally clone the selected repository into a specified local directory. Good for prompts like “帮我搜 GitHub 上相关仓库”, “帮我找并下载一个相关仓库”, “搜索 GitHub 上的项目然后拉到 reference”, or “按关键词找仓库并 clone 到指定位置”.
Use when the task is to build or maintain a repo-local 热门话题/AI日报专项, aggregate multiple public hot-topic sources such as AIbase Daily or RSS feeds, normalize them into a reusable snapshot, route the findings into the best existing site hotspot pages, and keep the hot-topic hub updated over time.
Use when the task is to take a user-provided keyword, search the web for relevant articles, summarize and cluster the findings, choose the most appropriate existing `site/` topic or hotspot page in this project, and draft a publish-ready Markdown article with explicit image prompt placeholders or Mermaid notes.
Use when a task should advance through repeated plan-driven loop cycles for an engineering project, paper, or long-running repo change. loloop wraps the official /loop idea with the repo's loop-in-loop method: read the current plan, inspect prior evolution notes, execute the current iteration, write a new evolution record, draft the next plan when a version is complete, and prepare the next /loop handoff.
Automatically fix, enhance, and optimize other skills when problems occur. Use when a skill fails or produces unexpected results. Prevents similar issues in the future.
| name | gen-zhihu-article |
| description | Generate Zhihu article in the style of 22-庖丁解牛专题页-知乎图文终版.md |
| user-invocable | true |
根据指定主题生成知乎风格文章。
不要把所有文章都写成同一种模板。生成前先判断最适合的风格，并在同批次文章里避免连续重复同一种开场和收束。
知乎发文时，要主动压低 AI 味，尤其避免那种过度整齐、过度解释、像模板机生成的对照句。
默认禁用或强烈避免这类句式：
不是 xxx，而是 xxx不只是 xxx，而是 xxx真正重要的不是 xxx，而是 xxx它看起来像 xxx，但本质上是 xxx除非用户明确要求保留这种修辞，否则优先改写成更自然的表达：
可优先在这些风格里选一类：
参考 wemedia/zhihu/articles/22-庖丁解牛专题页-知乎图文终版.md，但不要机械复制这一个模板。
# 找到一个不错的 [主题名]：[一句话价值点]
也可以根据风格切换成：
最近看到一个值得拆的 [主题名]：...如果你正想解决 [问题]，这套 [主题名] 值得先看把 [主题名] 这条链路走通之后，我觉得最值得记住的是 ...一、[第一个价值点]
内容 + 图片引用
二、[第二个价值点]
内容 + 图片引用
...
不要每篇都硬套完全相同的节奏。允许根据题材切换成：
问题 -> 方案 -> 价值 -> 适用人群背景 -> 拆解 -> 判断 -> 建议发布点 -> 关键变化 -> 影响 -> 实操建议论文问题 -> 方法 -> 结果 -> 启发
如果文章的判断依赖仓库实现、脚本逻辑、协议细节或源码结构，不要只写文件路径。
默认做法：
推荐写法：
在 tools/foo.py 里，关键逻辑是：
def should_resume(task_state):
return task_state in {"active", "blocked"}
这里真正说明的是：系统会优先续跑未完成任务，而不是每轮随机挑新任务。
避免这种写法：
tools/foo.py文章保存到 wemedia/zhihu/articles/ 目录，文件名格式：
NN-[主题关键词]-知乎图文.md
文章主题来自以下专题页面：
site/topic-paoding-jieniu.html - 庖丁解牛专题总页site/topic-cc-unpacked-zh.html - Claude Code 解构site/topic-superset-unpacked.html - Superset 解构site/topic-sourcemap.html - Source Map 源码专题site/topic-source-derived.html - 源码反推思想site/topic-cc-buddy.html - Buddy 彩蛋site/topic-openharness.html - OpenHarnesssite/topic-cc-release-watch.html - 发版监督site/s01.html ~ site/d12.html - S/D 课程讲义/gen-zhihu-article [主题名或页面路径]
例如：
/gen-zhihu-article topic-superset-unpacked
/gen-zhihu-article S01 Agent Loop
/gen-zhihu-article 源码反推思想
wemedia/zhihu/articles/STYLE-AUDIT.mdSTYLE-AUDIT.md 已经指出最近 2 到 5 篇存在明显的开头、正文节奏或结尾重复，优先换一种风格再写去 AI 味 自检，特别检查是否出现了模板化的 不是……而是…… 连续对照句纯干货 / 原理型在交给 zhihu-publish 之前，默认再做一次最终文案审核。至少检查这四项：
不是……而是…… / 不只是……而是…… / 真正重要的不是……而是……