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 for publishing Markdown to WeChat via wenyan-cli, with concrete commands and good troubleshooting coverage. However, it is severely bloated by repetition (frontmatter requirements stated 3 times, cover options shown twice), unnecessary content (changelog, license, feature checklists), and lacks any progressive disclosure structure. Trimming repetition and splitting into referenced sub-files would dramatically improve quality.
Suggestions
Remove duplicate sections: the frontmatter requirements and cover image options are repeated 3 times — consolidate into a single authoritative section.
Remove changelog, license, feature checklist, and reference links — these don't help Claude execute the task and waste tokens.
Split theme documentation and troubleshooting into separate referenced files (e.g., THEMES.md, TROUBLESHOOTING.md) to reduce the main skill to a concise overview.
Add a post-publish verification step (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 separate times with nearly identical content. The cover image options (relative/absolute/network) are shown twice. Feature checklist, changelog, license, and emoji-heavy formatting add significant bloat. Hardcoded user paths (/Users/leebot/) are included. Much content explains things Claude already knows (what Markdown is, how env vars work, how code blocks render). | 1 / 3 |
Actionability | Provides fully executable commands throughout: installation, publishing, theme configuration, troubleshooting. All code examples are copy-paste ready with concrete CLI commands and proper Markdown frontmatter examples. The publish workflow has three concrete methods with exact commands. | 3 / 3 |
Workflow Clarity | The high-level workflow (prepare → publish → review) is listed but lacks validation checkpoints. There's no explicit step to verify the article was successfully pushed to drafts, no error recovery loop after publishing, and no verification that environment variables are correctly set before attempting publish. The troubleshooting section partially compensates but is reactive rather than proactive. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no bundle files to reference. All content (quick start, themes, custom themes, troubleshooting, format requirements, changelog, license) is crammed into a single file. The frontmatter section and troubleshooting could easily be separate files. Content is repeated inline rather than referenced, and the document is well over 200 lines with no clear layering. | 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
aa009ea
- 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.