Token导航 LogoToken导航

Agent Skill · 开发

wechat-business-article-writer(微商文章作者)

wechat-business-article-writer 用于补充开发相关能力,适合在 OpenClaw 中需要让 Agent 承接开发相关任务时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

wechat-business-article-writer 是开发类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为只读;许可证为 MIT-0,第三方扫描已通过,按安装量在开发类的 21,746 个 Skill 里排第 10,454。

总安装 2,234周安装 95GitHub Stars 公开资料未说明下载 783核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.0.0

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:wechat-business-article-writer(微商文章作者)
来源仓库:https://github.com/openlark/wechat-business-article-writer
安装命令:
openclaw skills install wechat-business-article-writer
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install wechat-business-article-writer

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

创作微信公众号风格的商业与技术类文章,语气专业又通俗易懂。适合技术传播、产品推广或企业知识分享场景。wechat-business-article-writer 属于开发类 Skill,可作为该场景下的辅助能力补充。通过 clawhub 安装后,输入主题即可生成结构化内容草稿。

需结合品牌调性调整输出风格,避免模板化表达。建议人工复核内容准确性与版权风险后再对外发布。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install wechat-business-article-writer;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

wechat-business-article-writer 怎么安装?

在终端执行 openclaw skills install wechat-business-article-writer。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

wechat-business-article-writer 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

wechat-business-article-writer 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

wechat-business-article-writer 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

wechat-business-article-writer 用的人多吗?

公开数据是累计安装 2,234 次,近一周安装 95 次,下载 783 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

wechat-business-article-writer 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
wechat-business-article-writer

微商文章作者 · 本页

2,234—只读MIT-0通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
wechat-business-article-writer
description
Create WeChat public account style business and technology articles with professional yet approachable tone.

WeChat Business Article Writer

Overview

This skill helps create high-quality WeChat public account style articles that blend professional insights with approachable language. The writing style is based on personal observations and experiences, avoiding corporate jargon and AI-generated robotic tones.

Use Cases

  • Business observations and tech reviews
  • Product thinking and analysis
  • Serious but not rigid professional writing style
  • Occasional small humor to engage readers
  • Plain language explanations of complex topics
  • Avoiding AI-like robotic tone

Writing Style Guidelines

Core Style Dimensions

  1. Tone & Position: Serious professional but not rigid, confident yet humble, authoritative but approachable
  2. Rhetoric & Wording: Plain language over technical jargon, vivid metaphors, occasional humor
  3. Structure & Rhythm: Clear logical flow, engaging hooks, conversational pacing
  4. Content Focus: Business observations, tech reviews, product thinking
  5. Reader Engagement: Personal perspective, relatable examples, practical insights
  6. Voice Consistency: Authentic human voice, avoid AI-like perfection

Key Characteristics

  • Professional but not stiff: Treat complex topics seriously but avoid academic dryness
  • Occasional humor: Small, natural humor to keep readers engaged without being distracting
  • Plain language: Use everyday language to explain technical concepts
  • Personal perspective: Share observations and experiences, not just facts
  • Practical insights: Focus on what readers can learn and apply
  • Conversational flow: Write as if speaking to a knowledgeable friend

Article Structure Templates

Standard Business/Tech Article Structure

1. Hook
   - Interesting observation or question
   - Personal anecdote or experience
   - Current industry context

2. Main Content
   - Clear thesis or main point
   - Supporting evidence and examples
   - Analysis and insights
   - Counterpoints and considerations

3. Practical Takeaways
   - Actionable insights
   - Lessons learned
   - Future implications

4. Conclusion
   - Summary of key points
   - Final thought or reflection
   - Call to action or open question

Product Review Structure

1. First Impressions 
   - Personal experience with the product
   - Initial reactions and expectations

2. Detailed Analysis
   - Strengths and advantages
   - Weaknesses and limitations
   - Comparison with alternatives

3. Practical Value 
   - Who should use this
   - Best use cases
   - Cost-benefit analysis

4. Final Recommendation 
   - Overall assessment
   - Specific recommendations
   - Future outlook

Writing Process

Step 1: Define Your Perspective

  • What's your unique angle or experience?
  • What observations can you share that others might miss?
  • What personal insights can you provide?

Step 2: Structure Your Content

  • Choose appropriate template based on article type
  • Plan the flow from hook to conclusion
  • Identify key points and supporting evidence

Step 3: Write with Authentic Voice

  • Use "I" and "we" when sharing personal experiences
  • Be honest about limitations and uncertainties
  • Include occasional personal asides and humor
  • Avoid corporate buzzwords and AI-generated phrases

Step 4: Edit for Readability

  • Simplify complex technical concepts
  • Break up long paragraphs
  • Use conversational transitions
  • Ensure natural flow between ideas

References

See WRITING_GUIDELINES.md for detailed writing principles and examples.

Common Pitfalls to Avoid

  • AI-like tone: Avoid overly formal, perfect, or robotic language
  • Corporate jargon: Use plain language instead of business buzzwords
  • Pure information: Always add personal perspective and insights
  • Academic dryness: Keep it engaging and conversational
  • Excessive humor: Use humor sparingly and naturally
  • Lack of depth: Balance accessibility with substantive content

Quality Checklist

Before publishing, ensure your article:

  • [ ] Has an engaging hook that draws readers in
  • [ ] Uses plain language to explain complex concepts
  • [ ] Includes personal perspective and experiences
  • [ ] Provides practical, actionable insights
  • [ ] Maintains consistent, authentic voice throughout
  • [ ] Occasional natural humor (not forced)
  • [ ] Clear structure with logical flow
  • [ ] Avoids AI-generated corporate-speak

平台分布

OpenClaw

75.21%
按下载量换算589

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills