best-skills is a collection of reusable skills for coding agents, including tools for writing papers, creating diagrams and presentations, generating code documentation, and other tasks. Users install its skills into agents such as Cursor, Claude Code, Codex, or OpenClaw so those agents can recognize relevant requests and run the corresponding workflows. The catalogue entries are examples of the skills included in the collection.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add xstongxue/best-skills --skill wechat-article-writergit clone --depth 1 https://github.com/xstongxue/best-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/xstongxue/best-skills/wechat-article-writer)<a href="https://agentmods.dev/skills/xstongxue/best-skills/wechat-article-writer"><img src="https://agentmods.dev/badge/skills/xstongxue/best-skills/wechat-article-writer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/xstongxue/best-skills/wechat-article-writer"><img src="https://agentmods.dev/badge/skills/xstongxue/best-skills/wechat-article-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
- Snyk warn
- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 111 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium MCP Rug Pull · line 155 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00105 | $0.03536 |
| Opus 5 | $0.00053 | $0.01768 |
| Sonnet 5 | $0.00021 | $0.00707 |
| Haiku 4.5 | $0.00011 | $0.00354 |
Grade A, and why
wechat-article-writer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 13d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
公众号/自媒体创作
一、任务识别
根据用户需求选择执行路径：
| 任务类型 | 触发词 | 执行 |
|---|---|---|
| 仅封面/结尾图 | 封面图、公众号封面、B站封面、小红书配图 | 读取 cover_guide.md |
| 仅正文插图 | 插图、步骤图、演示图、流程示意、前后对比 | 读取 illustration_guide.md |
| 撰写文章 | 写公众号、写文章、自媒体写作、爆款文章、内容创作 | 执行 Step 2–6 |
| 风格提取 | 分析写作风格、克隆文风、模仿某篇、提取风格、范文转风格指南 | 执行「四、风格提取流程」 |
二、写作风格
撰写文章时，按用户指定选择风格文件；未指定则用默认风格。
| 序号 | 风格 | 触发词（互不重复） | 参考文件 | 篇幅 |
|---|---|---|---|---|
| 1 | 默认 | （未指定时） | writing_style.md | 2000–4000 字 |
| 2 | 高流量/爆款 | 高流量、爆款、像 Skills 那篇 | viral_style.md 7 | 2500–4000 字 |
| 3 | 清单体/方法论 | 清单体、方法论、干货、步骤 | checklist_methodology_style.md | 2000–4000 字 |
| 4 | 资源盘点 | 盘点、替代方案、合集 | resource_roundup_style.md | 3000–6000 字 |
| 5 | 个人实测推荐 | 个人实测、亲身推荐 | personal_tool_review_style.md | 4000–7000 字 |
| 6 | 认知颠覆 | 认知颠覆、反常识、观点文 | contrarian_opinion_style.md | 2000–3500 字 |
| 7 | 身份共鸣/逆袭 | 身份共鸣、逆袭、你也行、转行经历 | identity_transformation_style.md | 2500–4000 字 |
| 8 | 故事化/情感共鸣 | 故事化、情感共鸣、人物故事 | story_emotional_style.md | 2500–4500 字 |
| 9 | 深度随笔 | 深度思考、随笔、像日记那篇、个人感悟 | personal_essay_style.md | 4000–7000 字 |
What ships with it
18 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- .env.example 626 B
- package.json 803 B
- README.md 8.3 KB
- reference/checklist_methodology_style.md 2.6 KB
- reference/contrarian_opinion_style.md 2.5 KB
- reference/cover_guide.md 4.2 KB
- reference/extraction_dimensions.md 2.6 KB
- reference/identity_transformation_style.md 2.5 KB
- reference/illustration_guide.md 1.5 KB
- reference/personal_essay_style.md 4.5 KB
- reference/personal_tool_review_style.md 3.4 KB
- reference/README.md 1.8 KB
- reference/resource_roundup_style.md 2.9 KB
- reference/story_emotional_style.md 3.0 KB
- reference/viral_style.md 3.3 KB
- reference/writing_style.md 2.6 KB
- scripts/export-drawio.sh 3.7 KB runs code
- scripts/upload-to-wechat.js 8.7 KB runs code
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 13d ago First seen · 251 lines · 105 tokens per session scan A 061cb39f1ae9
wechat-article-writer is a skill published in the GitHub repository xstongxue/best-skills (2,814 stars, last pushed 18d ago), licensed Apache-2.0. It adds 105 tokens to every session and 3,536 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
gh-pr-review
Automated Cherry Studio review for local branches, PRs, commits, files, architecture docs, and repository skills. Use for code or documentation reviews that need project-specific naming, main/renderer/shared placement and dependency rules, IpcApi and DataApi boundaries, lifecycle/service ownership, renderer hooks…
prepare-release
Prepare a new release by collecting commits, generating bilingual release notes, updating version files, and creating a release branch. Use when asked to prepare/create a release, bump version, or run /prepare-release.
claude-automation-recommender
Analyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Claude Code setup, mentions improving Claude Code workflows, asks how to first set up Claude Code for a project, or wants to know what…
gh-create-issue
Use when user wants to create a GitHub issue for the current repository. Must read and follow the repository's issue template format.
gh-create-pr
Create or update GitHub pull requests using the repository-required workflow and template compliance. Use when asked to create/open/update a PR so the assistant reads .github/pullrequesttemplate.md, fills every template section, preserves markdown structure exactly, and marks missing data as N/A or None instead of…