技术类文章生成

v1.0.0

微信公众号技术文章端到端生成流程。当用户给出一个技术主题,希望生成一篇完整的微信公众号文章时使用此技能。流程包含四步:(1)资料收集与主题分析调研;(2)根据大纲撰写正文;(3)质量检查(目标8.5/10分);(4)错误修复与润色优化。用户需提供主题、大纲(可选)和目标字数。

1· 90·0 current·0 all-time
by@sariel20

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for sariel20/wechat-technical-article-output.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "技术类文章生成" (sariel20/wechat-technical-article-output) from ClawHub.
Skill page: https://clawhub.ai/sariel20/wechat-technical-article-output
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install wechat-technical-article-output

ClawHub CLI

Package manager switcher

npx clawhub@latest install wechat-technical-article-output
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (WeChat technical article generation) align with the SKILL.md: the instructions describe research, drafting, review, and polishing steps. No unexpected binaries, env vars, or installs are requested.
Instruction Scope
The runtime instructions tell the agent to collect external documentation, blogs, and code examples and to mark sources — this matches a research step but implies web access and potential copyright/licensing considerations. The SKILL.md does not direct the agent to read system files, environment variables, or send data to arbitrary endpoints.
Install Mechanism
No install spec or code files are present (instruction-only), so nothing is written to disk or fetched during installation.
Credentials
The skill requires no environment variables, credentials, or config paths — requested access is proportional to the described task.
Persistence & Privilege
always is false and the skill has no install hooks or modifiers that alter other skills or system settings. It does not request elevated or persistent privileges.
Assessment
This skill is instruction-only and internally consistent, so installing it poses minimal system-level risk. Before using it: (1) avoid pasting proprietary or sensitive code into the prompt because the workflow encourages external research and reuse of examples; (2) verify and run any generated code yourself — the skill requires 'runnable' code but LLMs can hallucinate or introduce subtle bugs; (3) be mindful of copyright/licensing when the skill copies examples from external sources — require attribution or rewrite as needed; (4) if your environment disallows outbound web access, confirm the agent's data sources (the SKILL.md assumes ability to search docs/blogs); and (5) ask the skill to list sources and, when needed, shorten or alter reproduced material to avoid verbatim copyrighted text. Overall the skill appears coherent and proportionate, but review outputs for technical accuracy and licensing before publishing.

Like a lobster shell, security has layers — review code before you run it.

latestvk9703j2k6fey4nf2kd2ytr9t2584efbh
90downloads
1stars
1versions
Updated 2w ago
v1.0.0
MIT-0

微信公众号技术文章生成

流程概述

用户输入主题 + 大纲(可选) + 字数目标
    │
    ▼
[Step 1] 资料收集 · 主题分析 · 调研
    │
    ▼
[Step 2] 撰写正文
    │
    ▼
[Step 3] 质量检查(目标 ≥ 8.5/10)
    │
    ▼
[Step 4] 错误修复 · 优化 · 润色
    │
    ▼
输出最终文章

Step 1:资料收集 · 主题分析 · 调研

目标:充分理解主题,收集支撑素材,建立写作基础。

  1. 明确主题范围:与用户确认文章的核心论点和受众群体(初学者 / 有经验的开发者等)
  2. 资料收集
    • 搜索相关文档、官方API资料、技术博客、论文
    • 查找代码示例、开源项目案例
    • 收集统计数据、用户痛点、行业现状
  3. 主题分析
    • 提炼文章的核心价值(解决什么问题)
    • 确定文章的创新点或独特角度
    • 识别技术要点和难点
  4. 整理素材:列出收集到的关键信息点,标注来源,淘汰低质量/重复资料

输出:一份结构化的调研摘要(Key Points + 亮点素材列表),作为Step 2的输入。


Step 2:撰写正文

目标:基于大纲和调研素材,生成完整、通顺、有技术深度的文章正文。

输入要求(用户必须提供)

参数说明
主题文章要讲什么
大纲章节结构(建议提供,如未提供则自行拟定并征得用户确认)
字数目标字数(如 2000~3000 字)

写作要求

  1. 开头:用痛点、问题或有趣的现象切入,吸引读者
  2. 正文结构:逻辑清晰,章节之间有承上启下的过渡
  3. 代码部分:必须可运行,附简要注释;代码块标注语言类型
  4. 案例:包含真实或可验证的示例,增强说服力
  5. 结尾:总结要点,适当升华,可加入延伸阅读建议

Step 3:质量检查(目标 ≥ 8.5/10)

目标:在进入润色前,先做一次结构性和技术性审查。

检查维度(逐项评分,满分10分,目标8.5分)

维度权重检查要点
技术准确性30%概念无误、代码可运行、API描述正确
逻辑连贯性20%章节衔接自然,论点有据可依
内容完整性20%大纲各节点均有展开,无遗漏
可读性15%表达流畅,无病句,阅读体验顺畅
原创性15%有独到见解,非简单翻译或复制

评分标准

  • 9-10分:优秀,技术深度与可读性兼具,可直接发布
  • 8-8.5分:良好,有小瑕疵,Step 4修复后可发布
  • 7-8分:及格偏下,需要较大修改
  • <7分:不达标,需回到Step 2重写

审查流程

  1. 逐维度打分
  2. 列出每维度的具体问题(如"第3节代码块语法错误"、"过渡句缺失")
  3. 计算加权总分,给出是否进入Step 4的判断

Step 4:错误修复 · 优化 · 润色

目标:根据Step 3的评分报告,逐一修复问题并优化成最终版本。

  1. 修复技术错误:更正代码、修正概念错误
  2. 补全遗漏内容:补充残缺的章节或说明
  3. 优化逻辑:调整段落顺序,加强过渡句
  4. 润色表达
    • 简化冗长句式
    • 统一术语和写作风格
    • 提升开头和结尾的吸引力
  5. 格式检查:标题层级、代码块标记、列表格式、图片占位符说明
  6. 最终通读:快速浏览全文确认无遗漏

最终输出

完成Step 4后,输出:

  • 文章标题(可建议多个备选)
  • 正文全文(Markdown格式)
  • 可选配图/代码块位置标注(说明需要哪些插图)
  • 延伸阅读建议(可选)

Comments

Loading comments...