CtrlK
BlogDocsLog inGet started
Tessl Logo

wechat-hotspot-publisher

智能采集热点话题,10分制筛选优质选题,AI生成爆款内容(标题/封面/标签/图片/HTML排版),支持素材上传和草稿箱发布,一键发布到微信公众号、小红书、B站等多平台

58

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

61%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 action-oriented with executable commands and a reasonable reference structure, but it suffers from verbatim repetition across sections and lacks explicit validation checkpoints before destructive multi-platform publishing. Consolidating duplicated sections and adding a pre-publish verification step would improve conciseness and workflow clarity.

Suggestions

Remove the verbatim-duplicated '默认模式' (阶段一 vs 注意事项) and '发布后操作' blocks; reference a single source instead.

Add an explicit pre-publish validation checkpoint (e.g. confirm platform list, preview HTML, verify cover/required fields) before any --mode publish/custom_api call, to satisfy the destructive/batch-operation feedback-loop requirement.

Link the currently-orphaned bundle files (wechat/xiaohongshu/bilibili-api-guide.md, content-template.md, auto_publisher.py, fetch_sources.py) from the 资源索引 so all bundle assets are discoverable.

DimensionReasoningScore

Conciseness

Mostly actionable rather than padded explanation, but several sections repeat the same guidance verbatim — '默认模式' reappears in 阶段一, 注意事项, and 使用示例, and '发布后操作' is duplicated — so it could be tightened.

3 / 5

Actionability

Provides concrete executable commands with arguments (publish_wechat.py --mode custom_api --title ... --content ..., JSON file format, filter_topics.py invocations), with only minor gaps such as unspecified return-value handling.

4 / 5

Workflow Clarity

Two phases are sequenced with a preview/adjust loop, but batch/destructive multi-platform publishing lacks an explicit validation checkpoint before publish — only a general '人工确认' note — so the destructive-operation cap of 3 applies.

3 / 5

Progressive Disclosure

Good structure with a 资源/领域参考 index pointing to real one-level-deep reference files (viral-content-templates.md, html-layout-guide.md, sources-config.md), though several bundle files (content-template.md, wechat-api-guide.md, xiaohongshu-api-guide.md, bilibili-api-guide.md, auto_publisher.py, fetch_sources.py) are not referenced from the body.

4 / 5

Total

14

/

20

Passed

Description

71%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 action-rich with good trigger nouns, but it omits any explicit 'Use when...' guidance, which limits completeness and leaves the trigger conditions implied rather than stated. Adding a concrete 'when to use' clause would raise completeness and trigger quality.

Suggestions

Append an explicit 'Use when...' clause, e.g. 'Use when the user wants to turn trending topics into platform-ready content or publish drafts to WeChat / Xiaohongshu / Bilibili.'

Add common synonyms/file extensions or phrasings users actually say (e.g. '公众号草稿', '小红书笔记', '热点选题') to broaden trigger coverage.

Keep third-person voice (already correct) but ensure the 'when' trigger is a separate, explicit sentence rather than implied by the capability list.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — '智能采集热点话题', '10分制筛选优质选题', 'AI生成爆款内容(标题/封面/标签/图片/HTML排版)', '素材上传和草稿箱发布', '一键发布到微信公众号、小红书、B站' — giving comprehensive coverage of capabilities.

5 / 5

Completeness

Has a clear 'what' (hotspot collection, scoring, AI content generation, multi-platform publishing) but no explicit 'when' / 'Use when...' trigger clause, which per the guideline caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural user-facing terms ('热点话题', '爆款内容', '微信公众号', '小红书', 'B站') but lacks a 'Use when...' trigger clause and some common synonyms, so it sits above the 3 anchor but not fully comprehensive.

4 / 5

Distinctiveness Conflict Risk

The multi-platform hotspot-to-draft publishing niche is fairly distinct with concrete platform names, with only minor overlap risk against generic content-generation skills.

4 / 5

Total

16

/

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.

Validation16 / 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.