CtrlK
BlogDocsLog inGet started
Tessl Logo

wechat-publisher

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

70

3.06x
Quality

60%

Does it follow best practices?

Impact

89%

3.06x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./configs/microservice/bff-service/configs/agent-skills/clawhub/wechat-publisher/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 body is actionable with concrete commands, but it is held back by significant redundancy and a failure to use the existing reference files: themes and troubleshooting content is duplicated inline rather than referenced. The publish workflow also lacks an explicit validation step.

Suggestions

Replace the inlined 主题选项 and 故障排查 sections with short summaries that link to references/themes.md and references/troubleshooting.md, eliminating the duplicated content.

Add an explicit validation checkpoint to the publish workflow — e.g. run `wenyan render -f article.md` to preview before `wenyan publish`, and verify IP whitelist/credentials before publishing.

Remove the duplicated frontmatter explanations (keep one canonical statement) and trim the changelog/decorative emoji padding to respect the token budget.

DimensionReasoningScore

Conciseness

Noticeably verbose with several padded/duplicated sections: the frontmatter cover/title requirement is explained three times (快速开始, Markdown 格式要求, 故障排查), and the troubleshooting and themes content is inlined despite existing as separate reference files; a changelog and heavy emoji decoration add further padding.

2 / 5

Actionability

Provides concrete, executable commands (npm install -g @wenyan-md/cli, wenyan publish -f … -t lapis -h solarized-light, wenyan theme --add) covering common cases; the main gap is hardcoded /Users/leebot/… paths that won't generalize.

4 / 5

Workflow Clarity

A numbered 快速开始 sequence exists, but the main 工作流程 is high-level with no explicit validation checkpoint; the recommended wenyan render preview gate appears only in troubleshooting's best practices rather than the publish workflow.

3 / 5

Progressive Disclosure

Section structure is clear, but reference files (references/themes.md, references/troubleshooting.md) exist and are never linked from the body, while their content is inlined — references are not signaled and content that should be separate remains inline.

3 / 5

Total

12

/

20

Passed

Description

70%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 is specific and clearly occupies a distinct niche, but it omits any explicit "Use when…" trigger guidance, which caps its completeness. Adding a trigger clause would raise the score meaningfully.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user wants to publish a Markdown article to a WeChat Official Account draft box."

Add common synonyms/file extensions users might say (e.g. 公众号, .md) to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Lists several concrete capabilities — "一键发布…草稿箱", "多主题", "代码高亮", "图片自动上传" — naming the domain and multiple specific actions, though not exhaustive enough for a 5.

4 / 5

Completeness

The "what" is clear, but there is no "Use when…" clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric.

3 / 5

Trigger Term Quality

Contains natural user-facing terms ("Markdown", "微信公众号", "草稿箱", "发布") that a user would actually say, with only minor synonym variations missing.

4 / 5

Distinctiveness Conflict Risk

Targets a very specific niche (publishing Markdown to the WeChat Official Account draft box) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

16

/

20

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.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
UnicomAI/wanwu
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.