CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wx-mp-hunter

微信公众号内容抓取。如下三个场景必用本技能:(1) 用户提供 mp.weixin.qq.com 文章链接 -> 直接用本技能 fetch 全文(不要用浏览器 或 web_fetch);(2) 用户提供公众号名称、要求按时间窗口或最近 N 条获取发布列表 -> 用本技能 posts-list;(3) 用户提供 mp.weixin.qq.com/mp/homepage 专题页/主题页链接 或 mp.weixin.qq.com/mp/appmsgalbum 合集链接,要求采集该页面全部文章 -> 用本技能 homepage 采集目录链接

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

70%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 operationally excellent: complete CLI syntax, option tables, output schemas, and batch workflows with genuine validation checkpoints and failure-handling loops. Its weaknesses are redundancy (usage examples and follow-constraint restated multiple times) and a missing bridge to the bundled script that implements everything, which also leaves the invocation path implicit.

Suggestions

Add a line connecting the CLI to the bundle, e.g. 'run via python3 scripts/wx_mp_hunter.py <command>' (or document the install/PATH setup), so the copy-paste commands are actually executable from the skill bundle.

Remove the '典型用法示例' section or reduce it to a single compact table — it duplicates the workflow diagram and per-command sections already shown above.

State the posts-list follow-account constraint once and reference it from the JSON examples' hint field instead of repeating the full explanation in three places; consider moving detailed environment-detection paths into a short reference file.

DimensionReasoningScore

Conciseness

The '典型用法示例' section (scenarios A/B/B2/C) largely restates the '两条独立工作流' diagram and the per-command sections, and the posts-list follow-account constraint is repeated three times (workflow note, 已关注账号约束 section, and both JSON hint examples). This is noticeable tightening opportunity rather than minor trims, so anchor 3 fits better than 4, though it never explains concepts Claude already knows.

3 / 5

Actionability

Commands are concrete and copy-paste ready with full flag syntax ('wx-mp-hunter fetch <url> --html --download-images --output-dir ./article-out'), option tables, and annotated output JSON with field-by-field descriptions. It falls short of anchor 5 because the body never references the bundled scripts/wx_mp_hunter.py, leaving unstated how the 'wx-mp-hunter' command maps to or invokes the script, and camoufox-cli steps are described procedurally rather than with executable commands.

4 / 5

Workflow Clarity

The homepage and batch-fetch workflows have explicit validation and feedback loops: small-sample verification before batch ('先选 1 篇文章 fetch 验证链路成功;成功后才能批量'), scroll-until-height-stable checks, URL dedup with count reporting, 1-2s pacing, stop after 3 consecutive failures, captcha escalation to the user, and an error-cause-action table. This matches the anchor 5 pattern of clear sequence with explicit validation and error recovery.

5 / 5

Progressive Disclosure

The body has clear per-command sections, but the bundle's only implementation file (scripts/wx_mp_hunter.py) is never referenced or linked from the body, and ~300 lines of inline CLI reference (options tables, two full posts-list output examples, detection path details) sit in SKILL.md with no one-level-deep split. Structure exists but organization and signaling gaps keep it at anchor 3 rather than 4.

3 / 5

Total

15

/

20

Passed

Description

87%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.

A strong description: it defines a clear WeChat-specific niche with three explicitly enumerated trigger scenarios, concrete command mappings, and explicit negative guidance (don't use browser or web_fetch). Minor room to broaden trigger phrasings beyond URL-carrying requests and to mention more capabilities of the fetch output.

DimensionReasoningScore

Specificity

The description names the domain (微信公众号内容抓取) and maps each of three trigger scenarios to a concrete action ('fetch 全文', 'posts-list', 'homepage 采集目录链接'). It stops short of anchor 5 because capabilities like markdown/image/cover download and output format are not mentioned, and it exceeds anchor 3 since more than 1-2 specific actions are listed.

4 / 5

Completeness

It explicitly answers 'what' (WeChat Official Account content scraping) and 'when' with an explicit trigger clause ('如下三个场景必用本技能') enumerating three concrete trigger conditions. Anchor 4 does not fit because the 'when' is already highly explicit and specific with URL patterns, matching anchor 5's requirement for concrete trigger phrases.

5 / 5

Trigger Term Quality

Triggers cover natural user inputs well: mp.weixin.qq.com URLs, 公众号名称, 时间窗口, 最近 N 条, and synonyms 专题页/主题页 and 合集. A few natural phrasings are missing (e.g., a user asking to scrape a '微信文章' without providing a link), so it falls just below comprehensive anchor 5 but clearly above anchor 3's partial coverage.

4 / 5

Distinctiveness Conflict Risk

mp.weixin.qq.com URL patterns, /mp/homepage, /mp/appmsgalbum, and 公众号-specific vocabulary define a clear niche that no generic fetching or scraping skill would claim. It also explicitly redirects away from browser/web_fetch, minimizing wrong-skill triggering.

5 / 5

Total

18

/

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.

Validation — 13 / 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

Warning

Total

13

/

16

Passed

Repository

TeamWiseFlow/xiaobei

Path

crews/main/skills/wx-mp-hunter/SKILL.md

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.