wechat-publisher
一键发布 Markdown 到微信公众号草稿箱。基于 wenyan-cli，支持多主题、代码高亮、图片自动上传。
67
55%
Does it follow best practices?
Impact
89%
3.06xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/0731coderlee-sudo/wechat-publisher/wechat-publisher/SKILL.mdQuality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is strong in specificity and distinctiveness, clearly identifying a niche workflow (Markdown to WeChat Official Account drafts) with concrete features. However, it lacks an explicit 'Use when...' clause which caps completeness, and could benefit from additional trigger term variations including English equivalents for bilingual users.
Suggestions
Add an explicit 'Use when...' clause, e.g., '当用户需要将 Markdown 文章发布到微信公众号、提到 WeChat 公众号排版、或需要使用 wenyan-cli 时使用。'
Include common trigger term variations such as 'WeChat', 'MP platform', '公众号排版', '公众号发文', '微信文章' to improve matching for different user phrasings.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: publishing Markdown to WeChat Official Account drafts, multi-theme support, code highlighting, and automatic image uploading. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (publish Markdown to WeChat drafts with themes, code highlighting, image upload), but lacks an explicit 'Use when...' clause or equivalent trigger guidance for when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes good domain-specific terms like 'Markdown', '微信公众号' (WeChat Official Account), '草稿箱' (draft box), 'wenyan-cli', '代码高亮' (code highlighting), but misses common user variations like 'WeChat', 'MP', 'wechat article', or English equivalents that users might naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct niche combining Markdown publishing specifically to WeChat Official Account drafts via wenyan-cli. This is unlikely to conflict with other skills due to the highly specific platform and toolchain mentioned. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is highly actionable with concrete, executable commands and useful real-world troubleshooting, but severely undermined by extreme verbosity and repetition. The same information (especially frontmatter requirements) is repeated multiple times, and the document is a monolithic wall that could be 60% shorter with better organization and progressive disclosure.
Suggestions
Eliminate repeated content: the frontmatter requirements (title + cover mandatory) appear 3+ times — consolidate into a single authoritative section.
Split into multiple files: move theme catalog to THEMES.md, troubleshooting to TROUBLESHOOTING.md, and keep SKILL.md as a concise overview with references.
Remove content that doesn't help Claude: feature checklist, changelog, license section, and explanatory emoji-heavy marketing copy add no instructional value.
Add a validation step after publishing (e.g., check API response or confirm draft appeared) to create a proper feedback loop in the workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with heavy repetition. The frontmatter requirements (title + cover mandatory) are explained at least 3 times with nearly identical content. Cover image options are listed twice. Error examples are redundant. Feature checklist, changelog, and license add no value for Claude. Hardcoded user paths (/Users/leebot/, /Users/bruce/) are specific but wasteful. | 1 / 3 |
Actionability | Provides fully executable commands throughout: installation, environment setup, publish commands with real flags, theme customization, and troubleshooting with specific error messages and fixes. All code blocks are copy-paste ready. | 3 / 3 |
Workflow Clarity | The 3-step workflow (prepare → publish → review) is listed but shallow. There's no validation checkpoint after publishing (e.g., checking the API response for success/failure). The publish.sh script is mentioned as auto-detecting wenyan-cli but no detail on what happens on failure. Troubleshooting is separate rather than integrated into the workflow as checkpoints. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to separate files. Everything is inline — theme lists, troubleshooting, format requirements, custom themes, examples — all in one massive document. Theme options, advanced customization, and troubleshooting could easily be split into separate referenced files. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 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 |
Total | 9 / 11 Passed | |
- Repository
- NeverSight/skills_feed
- Commit
f772de4
- 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.