article-writer
Skill6 starsChanged 6 days agoMITView on GitHub
Use when 用户想写公众号、知乎技术文章、自媒体内容,或基于已有技术文档改写为可发布文章时。
8 other projects use a version of this.
Adopted by
Most recently taken up by
- awaik/direct-mcp-ai-projecttheir own version, first seen Nov 1, 2026
- LDJ-creat/media-skillstheir own version, first seen Oct 9, 2026
- EvovexAI/EvoFlowtheir own version, first seen Oct 8, 2026
- netease-youdao/LobsterAItheir own version, first seen Oct 8, 2026
- ckt520728/claude-skillstheir own version, first seen Jul 1, 2026
- freestylefly/wesighttheir own version, first seen May 7, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- netease-youdao/LobsterAI★ 6.2ksame name
- freestylefly/wesight★ 969same name
- EvovexAI/EvoFlow★ 612same name
- LDJ-creat/media-skills★ 28same name
- awaik/direct-mcp-ai-project★ 17same name
- huangzw9527-stack/openclaw-skills-zh★ 4same name
- ckt520728/claude-skills★ 0same name
- wingeek/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository79 other files it gives its agents.
- AGENTS.mdAGENTS.md
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-bulk-archive-changeSkill
- openspec-continue-changeSkill
- openspec-exploreSkill
- openspec-ff-changeSkill
- openspec-new-changeSkill
- openspec-onboardSkill
- openspec-sync-specsSkill
- openspec-verify-changeSkill
- ai-proxy-disciplineSkill
- analysis-coreSkill
- android-webview-debugSkill
- astrill-controlSkill
- brainstorm-workflowSkill
- browser-debug-toolkitSkill
- clarifying-question-disciplineSkill
- code-design-reviewSkill
- competitive-researchSkill
- completion-evidence-disciplineSkill
- context-budget-disciplineSkill
- decision-fog-disciplineSkill
- delivery-disciplineSkill
- design-approval-gateSkill
- domain-language-disciplineSkill
- effective-web-researchSkill
- essence-diagnosisSkill
- evolution-reviewSkill
- explain-clearlySkill
- feature-branch-closeoutSkill
- figma-pixel-implementSkill
- figma-pixel-verifySkill
- git-branch-protectSkill
- git-commitSkill
- git-conflict-resolveSkill
- git-release-finishSkill
- git-release-startSkill
- git-worktree-disciplineSkill
- goal-driven-queueSkill
- goal-driven-workflowSkill
- go-deploySkill
- hybrid-debugSkill
- intake-interview-disciplineSkill
- jira-fix-queueSkill
- jira-fix-workflowSkill
- jira-readSkill
- jira-status-lifecycleSkill
- jira-status-writebackSkill
- jira-wiki-markupSkill
- known-issue-researchSkill
- learn-and-improveSkill
- merge-disciplineSkill
- multi-agent-debateSkill
- node-version-disciplineSkill
- opsx-jira-fix-queueSkill
- opsx-jira-fix-workflowSkill
- opsx-solve-workflowSkill
- opsx-workspace-gateSkill
- perf-optimize-workflowSkill
- The first 60 shown.
The file
Files
技术文章写作流程
Overview
4 步流程:搜索资料 → 撰写文章 → 生成标题 → 排版优化。适用于公众号、知乎、掘金等平台。REQUIRED: 全文应用中文标点规范(见 Step 2 格式区)。
When to Use
- 写公众号、知乎技术文章、自媒体内容
- 基于已有技术文档改写、发布
- 需要爆款标题、排版建议、多平台适配
When NOT to use: 纯学术论文(用 ml-paper-writing)、小说创作(用 writer-memory)、项目内文档(用 doc-coauthoring)
执行前准备
- 读取项目上下文(CLAUDE.md、AGENTS.md 等,若存在)—— 写作风格、结尾语
- 读取源材料(若指定)—— 已有文档、技术资料
- 确认目标平台—— 公众号/知乎/掘金,字数略有差异
关键动作:必须先读取项目上下文,再读取源材料,最后确认目标平台。
Step 1:搜索资料
主题需补充时用 WebSearch:并行多源、优先最新、深度总结。若用户已提供完整源材料,可跳过。
Step 2:撰写文章
结构模板(按类型选)
| 类型 | 框架 |
| 技术科普 | 科普 → 案例 → 总结 |
| 原理剖析 | 表象 → 深入分析 → 结论 |
| 使用教程 | 效果展示 → 步骤教学 → 升华 |
| 工具测评 | 介绍 → 使用过程 → 评测结论 |
通用结构:效果展示 → 问题描述 → 步骤教学 → 升华总结
撰写要求
- 1000–1500 字;故事化开头或直击痛点;备选标题 2–3 个
- 原则:具体、易落地、可见效(可执行步骤、有对比有数据)
格式
中文标点规范(全文严格遵守):
| 标点 | 使用 | 不使用 |
| 逗号 | , | , |
| 句号 | 。 | . |
| 分号 | ; | ; |
| 冒号 | : | : |
| 问号 | ? | ? |
| 感叹号 | ! | ! |
| 括号 | () | () |
| 书名号 | 《》 | - |
例外(保持原文):技术术语(JavaScript、React 等)、代码/命令、URL/路径、版本号/数字。书名号内的英文标点可保留(如《JavaScript: The Good Parts》)。
代码块前后留白、语法高亮。
Step 3:生成标题
生成 5 个标题,要素:痛点明确、数字吸引、结果导向、情绪调动、悬念设置。
| 要素 | 示例 |
| 痛点 | 「还在手动切换 Node?」 |
| 数字 | 「3 分钟」「5 个技巧」 |
| 结果 | 「效率暴涨 10 倍」 |
可选 Vibe Coding 格式:《Vibe Coding 10X 提效:[成果],[痛点]》
Step 4:排版优化
- 段落:每段 3–5 行,重要数据加粗,金句单独成段
- 配图:标题下封面、步骤后效果图、结尾 CTA
- 代码块:前后留白、语法高亮
- 确保段落长度在 3–5 行之间,便于移动端阅读
Quick Reference
| 阶段 | 关键动作 |
| 准备 | 读项目上下文、源材料、确认平台 |
| 搜索 | 需补充时 WebSearch,有源材料可跳过 |
| 撰写 | 选结构模板、1000–1500 字、中文标点规范 |
| 标题 | 5 个、含痛点/数字/结果 |
| 排版 | 3–5 行/段、配图位、代码留白 |
Common Mistakes
| 错误 | 修正 |
| 跳过项目上下文 | 先读再写,保持风格一致 |
| 忽略中文标点规范 | 中文标点、术语规范必用 |
| 标题泛泛 | 必须含痛点或数字或结果 |
| 有源材料仍大搜 | 以源材料为主,仅补充验证 |
配合 Skill
| Skill | 作用 |
| wechatsync | 多平台同步 |
| doc-coauthoring | 结构化打磨、读者测试 |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

