wechat-article-writer
- Repo stars 295
- Author updated Live
- Author repo happy-claude-skills
- Domain
- Writing
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @iamzhihuix · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: wechat-article-writer
description: 使用 WebSearch 工具搜索主题相关资料: 帮我写一篇关于 Claude Code 使用技巧的公众号文章 runs entirely locally. Works with Claude…
category: writing
runtime: no special runtime
---
# wechat-article-writer output preview
## PART A: Task fit
- Use case: 使用 WebSearch 工具搜索主题相关资料: 帮我写一篇关于 Claude Code 使用技巧的公众号文章 runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Step 1: 搜索资料 / Step 2: 撰写文章 / Step 3: 生成标题” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “使用 WebSearch 工具搜索主题相关资料: 帮我写一篇关于 Claude Code 使用技巧的公众号文章 runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Step 1: 搜索资料 / Step 2: 撰写文章 / Step 3: 生成标题” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “Step 1: 搜索资料 / Step 2: 撰写文章 / Step 3: 生成标题”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: wechat-article-writer
description: 使用 WebSearch 工具搜索主题相关资料: 帮我写一篇关于 Claude Code 使用技巧的公众号文章 runs entirely locally. Works with Claude…
category: writing
source: iamzhihuix/happy-claude-skills
---
# wechat-article-writer
## When to use
- 使用 WebSearch 工具搜索主题相关资料: 帮我写一篇关于 Claude Code 使用技巧的公众号文章 4 步完成高质量公众号文章:搜索资料 → 撰写文章 → 生成标题 → 排版优化 使用 WebSearch 工具搜索主题相关资…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Step 1: 搜索资料 / Step 2: 撰写文章 / Step 3: 生成标题” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "wechat-article-writer" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Step 1: 搜索资料 / Step 2: 撰写文章 / Step 3: 生成标题
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} 公众号文章写作流程
4 步完成高质量公众号文章:搜索资料 → 撰写文章 → 生成标题 → 排版优化
Step 1: 搜索资料
使用 WebSearch 工具搜索主题相关资料:
搜索要求:
1. 并行搜索多个来源(官方文档、X/Twitter、Reddit、技术论坛)
2. 优先获取最新资料(当月/当季)
3. 可启动多个并行 Task 加速搜索
4. 深度总结搜索结果
Step 2: 撰写文章
必须先读取用户的 CLAUDE.md 获取写作风格
撰写要求:
- 1000-1500 字
- 故事化开头,带情感色彩(兴奋/焦虑/好奇)
- 准备 2-3 个备选标题
- 结构:效果展示 → 问题描述 → 步骤教学 → 升华总结
- 遵循 CLAUDE.md 中定义的写作风格和结尾语
Step 3: 生成标题
生成 5 个爆款标题,特点:
- 痛点明确:直击读者痛处("还在手动...")
- 数字吸引:具体数字更有说服力("3分钟"、"5个技巧")
- 结果导向:承诺具体收益("效率暴涨10倍")
- 情绪调动:惊、神技、秘籍等词汇
- 悬念设置:引发好奇心
Step 4: 排版优化
优化建议:
- 段落结构:每段 3-5 行,重要数据单独成段加粗
- 配图位置:标题下方封面图、步骤后效果图、结尾总结图
- 代码块:前后留白,语法高亮
- 金句:单独成段,增强记忆点
示例
用户请求:
帮我写一篇关于 Claude Code 使用技巧的公众号文章
执行流程:
- 搜索 Claude Code 最新功能和使用技巧
- 读取 CLAUDE.md 获取写作风格
- 撰写 1200 字左右的教程文章
- 生成 5 个爆款标题供选择
- 提供排版和配图建议
Decide Fit First
Design Intent
How To Use It
Boundaries And Review