CtrlK
BlogDocsLog inGet started
Tessl Logo

wechatsync-publisher

自媒体创作者在进行全网内容分发时,使用此技能可智能筛选优质选题、AI生成多版本文章,并一键自动适配格式发布至微信公众号、知乎、掘金等6大平台,轻松实现从创作到推送的全流程自动化,大幅提升多平台运营效率!

51

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/wechatsync-publisher/wechatsync-publisher/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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 skill is highly actionable with real, executable scripts and a well-structured bundle of one-level-deep references, and the workflow sequence is clear. Its main weaknesses are systematic redundancy across sections and the complete absence of validation/verification checkpoints for what is a batch, externally-visible publishing operation.

Suggestions

Consolidate the per-platform format/length/cover-ratio tables (currently repeated in 步骤二, 分支B, and 注意事项) into a single table or into references/platform-requirements.md, and delete the 更新日志 section.

Add validation checkpoints after each publish step — e.g. check the HTTP response JSON for success, confirm the draft appears in the platform draft box, and on failure surface the error and retry/abort — since batch publishing without verification caps workflow clarity.

Replace placeholder arguments like --content "HTML内容" with one realistic worked example (a short actual HTML snippet) so the publish command is copy-paste runnable end to end.

DimensionReasoningScore

Conciseness

The body is noticeably verbose through redundancy: per-platform length/format/cover-ratio specs are repeated at least three times (步骤二, 分支B 差异化要点, 注意事项), the '需配置接口' caveat is repeated in nearly every section, and sections like 更新日志, 高级功能, and 使用示例 restate content already covered — matching the 'several unnecessary explanations or padded sections' anchor. It is not 3 because the duplication is systematic rather than occasional, and not 1 because the core sections do stay on-task without explaining general concepts Claude already knows.

2 / 5

Actionability

Provides concrete, executable commands with real arguments for all three scripts (filter_topics.py --topics/--threshold, search_images.py --keyword/--count/--size, publish.py --platform/--title/--content/--cover-image/--tags), and all referenced files (6 references, 3 scripts) actually exist in the bundle — matching 'mostly executable guidance with minor gaps'. Not 5 because examples pass placeholders like "HTML内容" and "文章标题" instead of a realistic worked example, and the customization snippets (publish_zhihu stub with 'YOUR_ZHIHU_API_URL') are pseudocode rather than runnable code.

4 / 5

Workflow Clarity

The sequence is well laid out (选题筛选 → 内容生成 → 一键发布, plus branches A/B/C for quick, multi-platform, and manual-review flows), matching the 'steps listed but validation gaps' anchor: publishing to external platforms is a batch, outward-facing operation, yet there is no step to check the API response, confirm the draft landed, or retry/handle failure — the rubric explicitly caps workflow clarity at 3 for batch operations without validation. Not 4 because validation is entirely absent rather than a minor gap.

3 / 5

Progressive Disclosure

The SKILL.md body acts as an overview with six references and three scripts, each reference linked with an explicit '何时读取' (when to read) signal, and all referenced paths resolve to real files one level deep — matching 'good structure, most content appropriately placed, references mostly clear'. Not 5 because the body still inlines considerable detail that belongs in those files (troubleshooting, advanced features, and the repeated platform-spec tables), making the overview itself heavy.

4 / 5

Total

13

/

20

Passed

Description

58%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 communicates a fairly specific capability set with named platforms, but lacks an explicit 'Use when' trigger clause and pads it with promotional fluff. Trigger keyword coverage is partial — platform names are present but natural request phrasings are missing.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to publish or distribute articles to WeChat Official Account (微信公众号), Zhihu, Juejin, Xiaohongshu, or other Chinese content platforms (多平台发布、一键推送、内容分发).'

Remove promotional filler like '轻松实现…全流程自动化,大幅提升多平台运营效率!' and state capabilities in plain third person (e.g. 'Filters topic candidates, generates platform-adapted article versions, and publishes drafts to 6 platforms').

Include the natural request phrasings users would actually say ('发布到公众号', '多平台分发', '一键推送') as trigger terms alongside the platform names.

DimensionReasoningScore

Specificity

Lists several concrete actions — "智能筛选优质选题" (filter quality topics), "AI生成多版本文章" (generate multi-version articles), "自动适配格式" (auto-adapt format), "一键...发布" (one-click publish) — with named platforms (微信公众号、知乎、掘金), matching the 'several specific actions, minor gaps' anchor. It is not 5 because the tail is marketing padding ("轻松实现...全流程自动化,大幅提升多平台运营效率!") that adds no capability, and the '使用此技能' framing reads as second-person guidance rather than plain third-person capability statements, which per the rubric reduces this score by 1.

4 / 5

Completeness

The 'what' is clear (filter topics, generate multi-version content, adapt format, publish to 6 platforms), but there is no explicit 'Use when...' trigger clause — the only 'when' signal is the scenario framing "在进行全网内容分发时", which is weakly implied rather than explicit, matching the 'clear what but when missing or only weakly implied' anchor. The rubric explicitly caps completeness at 3 for a missing 'Use when...' clause, so it cannot be 4.

3 / 5

Trigger Term Quality

Contains some relevant natural keywords users would say — "微信公众号", "知乎", "掘金", "多平台", "全网内容分发" — but misses the common phrasings users actually type like "发布文章到公众号", "多平台发布", "一键推送", and no file/format synonyms, matching the 'some relevant keywords but missing common variations' anchor. Not 4 because the natural request phrasings (e.g. "把这篇文章发到知乎") are absent.

3 / 5

Distinctiveness Conflict Risk

The named Chinese platforms (微信公众号、知乎、掘金等) plus the specific workflow (topic scoring → multi-version generation → multi-platform publishing) carve out a distinct niche with minimal conflict risk against general writing or generic publishing skills, matching 'mostly distinct; minor overlap risk'. Not 5 because it could still mildly overlap with a generic content-creation or article-writing skill since no sharp trigger phrase distinguishes it.

4 / 5

Total

14

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
anbeime/skill
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.