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 via wenyan-cli) with concrete features. However, it lacks an explicit 'Use when...' clause, which weakens completeness, and could benefit from additional natural trigger terms users might use when requesting this functionality.
Suggestions
Add an explicit 'Use when...' clause, e.g., '当用户需要将 Markdown 文章发布到微信公众号、排版公众号文章、或提到 wenyan/微信排版时使用。'
Include common user trigger variations such as 'WeChat article', '公众号排版', '微信文章发布', 'MP platform' to improve discoverability across different 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, which caps this at 2 per the rubric. | 2 / 3 |
Trigger Term Quality | Includes good domain-specific terms like 'Markdown', '微信公众号' (WeChat Official Account), '草稿箱' (drafts), 'wenyan-cli', '代码高亮' (code highlighting), but misses common user variations like 'WeChat', 'MP', 'publish article', or English equivalents that users might naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct niche: the combination of Markdown, WeChat Official Account (微信公众号), wenyan-cli, and draft publishing is highly specific and unlikely to conflict with other skills. | 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 provides highly actionable, executable guidance with concrete commands and real error messages, which is its main strength. However, it is severely undermined by extreme verbosity and repetition—the frontmatter requirements alone are stated three times with examples. The content would benefit greatly from being cut by 50%+ and split into separate reference files for themes, troubleshooting, and format requirements.
Suggestions
Remove duplicate sections: the frontmatter requirements with examples appear in both '准备 Markdown 文件' and 'Markdown 格式要求'—consolidate into one location.
Extract theme options, custom theme management, and troubleshooting into separate reference files (e.g., THEMES.md, TROUBLESHOOTING.md) and link from the main skill.
Remove the changelog, license section, feature checklist, and '参考资料' section—these don't help Claude execute the task and waste tokens.
Add a validation step after publishing (e.g., check the API response or verify the 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 are mandatory) are explained at least 3 separate times with nearly identical content. The cover image path options are shown twice. Feature checklists, changelog, license, and emoji-heavy formatting add significant bloat without new information for Claude. | 1 / 3 |
Actionability | Provides fully executable, copy-paste ready commands throughout: installation, environment setup, publish commands with various theme options, custom theme management, and troubleshooting with specific error messages and fixes. All code examples are concrete and runnable. | 3 / 3 |
Workflow Clarity | The high-level workflow (prepare → publish → review) is listed but lacks validation checkpoints. There's no explicit step to verify environment variables are set correctly before publishing, no feedback loop for handling upload failures, and the publish script's auto-detection of wenyan-cli is mentioned but not integrated into a clear workflow sequence. | 2 / 3 |
Progressive Disclosure | Everything is in a single monolithic file with no references to separate documents for detailed content. The theme options, troubleshooting, custom themes, and markdown format requirements could all be split into separate files. The inline repetition of frontmatter requirements makes the document harder to navigate. | 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
e437c3c
- 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.