baoyu-post-to-wechat
Posts content to WeChat Official Account (微信公众号) via API or Chrome CDP. Supports article posting (文章) with HTML, markdown, or plain text input, and image-text posting (贴图, formerly 图文) with multiple images. Markdown article workflows default to converting ordinary external links into bottom citations for WeChat-friendly output. Use when user mentions "发布公众号", "post to wechat", "微信公众号", or "贴图/图文/文章".
91
92%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that covers all dimensions thoroughly. It provides specific capabilities (article posting, image-text posting, markdown conversion with citation handling), includes bilingual trigger terms that match real user language, explicitly states when to use it, and occupies a clearly distinct niche around WeChat Official Account publishing.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: posting articles via API or Chrome CDP, supporting HTML/markdown/plain text input, image-text posting with multiple images, and converting external links into bottom citations. Very detailed and actionable. | 3 / 3 |
Completeness | Clearly answers both 'what' (posts content to WeChat Official Account with various input formats and posting modes) and 'when' (explicit 'Use when...' clause with specific trigger phrases in both languages). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms in both English and Chinese: '发布公众号', 'post to wechat', '微信公众号', '贴图/图文/文章'. These are exactly what bilingual users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche targeting WeChat Official Account posting specifically. The combination of Chinese terms, WeChat-specific concepts (公众号, 图文), and Chrome CDP makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with clear workflow sequencing and excellent progressive disclosure. The main weakness is moderate verbosity — the User Input Tools preamble, Language section, and some repeated explanations could be trimmed to save tokens. Overall it's a strong skill that provides concrete, executable guidance for a complex multi-method publishing workflow.
Suggestions
Remove or drastically shorten the 'User Input Tools' section — Claude understands tool selection priority without a 3-paragraph explanation; a single sentence like 'Use the runtime's user-input tool (e.g., AskUserQuestion) or fall back to plain-text prompts' suffices.
Remove the 'Language' section — responding in the user's language is default Claude behavior and doesn't need instruction.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long and includes some sections that could be tightened (e.g., the User Input Tools section explains generic tool-selection logic Claude likely knows, and the Language section is boilerplate). However, most content is domain-specific configuration and workflow details that earn their place. | 2 / 3 |
Actionability | Provides fully executable bash commands with specific flags, concrete CLI examples for each posting method, exact API endpoint and payload field names, and specific fallback chains for metadata resolution. Copy-paste ready throughout. | 3 / 3 |
Workflow Clarity | The article posting workflow is clearly sequenced with a checklist, each step has explicit decision logic (detection tables, priority chains), and there are validation checkpoints (e.g., 'never pre-convert markdown to HTML' warning, credential verification, cover image resolution chain with a stop-and-request fallback). Error recovery paths are provided in the troubleshooting table. | 3 / 3 |
Progressive Disclosure | Excellent structure: the main SKILL.md provides a clear overview with concise tables and workflow steps, while detailed topics (multi-account, API setup, image-text posting, first-time setup) are cleanly referenced as one-level-deep markdown files in the references directory. Navigation is well-signaled with a references table at the bottom. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- Repository
- jimliu/baoyu-skills
- Commit
505a7e1
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.