wechat-publisher

一键发布 Markdown 到微信公众号草稿箱。基于 wenyan-cli，支持多主题、代码高亮、图片自动上传。

3.06x

Quality

48%

Does it follow best practices?

Impact

89%

3.06x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./data/skills-md/0731coderlee-sudo/wechat-publisher/wechat-publisher/SKILL.md

Quality

Content

42%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is information-rich and mostly actionable but suffers from heavy duplication, a broken primary script reference with hardcoded personal paths, and no validation checkpoint in the publish workflow.

Suggestions

Provide the missing ./scripts/publish.sh (or remove '方式 1' and lead with the working direct wenyan-cli command), and replace hardcoded /Users/leebot paths with portable examples.

De-duplicate the frontmatter/cover guidance into one authoritative section and remove the repeated relative/absolute/network cover examples.

Add an explicit validation step to the publish workflow (e.g. verify the draft appears in the 公众号草稿箱 before reporting success) so workflow clarity can exceed the destructive-operation cap.

Dimension	Reasoning	Score
Conciseness	The same guidance is repeated nearly verbatim across multiple sections — the frontmatter/cover requirement appears three times (quick start, Markdown 格式要求, 故障排查) and the relative/absolute/network cover examples are duplicated at lines 80-89 and 190-218 — making this noticeably padded rather than lean.	2 / 5
Actionability	Provides many concrete executable commands (npm install, wenyan publish with theme/highlight flags, export env vars, curl ifconfig.me), but the prominently recommended '方式 1' invokes ./scripts/publish.sh which does not exist in the bundle and hardcodes a personal path (/Users/leebot/.openclaw/workspace), a key missing detail in the headline workflow.	3 / 5
Workflow Clarity	A quick-start sequence and a 工作流程 section are present, but the publish-to-a-live-account operation has no validation/verification checkpoint (e.g. confirm the draft landed in the WeChat backend); per the destructive/batch cap, workflow clarity cannot exceed 3.	3 / 5
Progressive Disclosure	The body is well sectioned with headers, but it is a single monolithic ~320-line file with no bundle files, and references to ./scripts/publish.sh and ./assets/default-cover.jpg point to nonexistent paths, so structure is only partially organized.	3 / 5
	Total	11 / 20 Passed

Description

53%Weight 40%Scale 1-5

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 states a clear purpose and several concrete features but omits any explicit 'when to use' guidance, capping completeness. Trigger terms are relevant but lack synonym coverage.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers (e.g. 'Use when publishing Markdown articles to a WeChat Official Account / 公众号 draft box').

Include synonyms and the .md extension in the description to improve trigger-term coverage.

Reframe supported features as concrete actions (convert, upload images, push to draft) for stronger specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ('Markdown 到微信公众号草稿箱') and several concrete capabilities ('多主题、代码高亮、图片自动上传'), but these are feature flags rather than a comprehensive action list and omit core actions like format conversion that the body later reveals.	3 / 5
Completeness	Has a clear 'what' (一键发布 Markdown 到微信公众号草稿箱) but no explicit 'Use when...' trigger clause, so per the boundary guidance completeness is capped at 3 with 'when' only weakly implied.	3 / 5
Trigger Term Quality	Contains relevant natural terms ('Markdown', '微信公众号', '草稿箱', '发布') a user would say, but misses common variations and synonyms (e.g. 'WeChat', '公众号', .md extension).	3 / 5
Distinctiveness Conflict Risk	The WeChat draft-publishing niche is clear and distinct with low conflict risk, though the absence of explicit trigger guidance leaves minor overlap with generic Markdown-publishing skills.	4 / 5
	Total	13 / 20 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 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
relative_links	Relative link issues: 1 missing, 1 suspicious	Warning

	Total	13 / 16 Passed

Repository: NeverSight/skills_feed
Path: data/skills-md/0731coderlee-sudo/wechat-publisher/wechat-publisher/SKILL.md
Commit: 2f57aec

Reviewed: about 23 hours ago

Table of Contents

Discovery Implementation Validation

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.