CtrlK
BlogDocsLog inGet started
Tessl Logo

wx-mp-engagement

微信公众号 engagement 数据抓取。通过 camoufox-cli 跑创作者中心拿已发布文章的阅读数 / 点赞数 / 评论数 / 分享数 / 收藏数,写入 published-track的 pub_wx_mp 表。

65

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./crews/main/skills/wx-mp-engagement/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

The body is highly actionable with a clearly sequenced, validated workflow for a fragile scraping task, but it pays for it in conciseness (repeated token/session/coupling explanations) and keeps everything inline rather than splitting deeper detail into signaled reference files. De-duplicating the repeated facts and moving the innerText-parsing detail into a reference would lift the weakest dimensions.

Suggestions

State the token source, session-sharing/concurrency rules, and published-track integration rationale each in exactly one place, then cross-reference rather than re-explaining.

Move the innerText parsing structure and detailed integration notes into a reference file (e.g. references/parsing.md) and signal it explicitly from the body, rather than inlining it in SKILL.md.

Explicitly point to scripts/fetch_engagement.py for the executable implementation so the SKILL.md reads as an overview rather than a monolith.

DimensionReasoningScore

Conciseness

The body is dense and operational with no conceptual padding, but several points are repeated across sections — the token source is explained in 关键发现 #2, fetch 流程 step 4, and Notes; session-sharing/concurrency appears in 前置条件 #1, 关键发现 #3, and 约束; and the 4-step internal flow is restated in '与 published-track 集成'. It could be tightened by stating each fact once.

2 / 3

Actionability

Provides concrete, copy-paste-ready CLI commands with flags and exit codes, exact URLs with the required token parameter, a 9-step fetch flow with real camoufox-cli invocations, a full output JSON example, and a complete executable script (scripts/fetch_engagement.py).

3 / 3

Workflow Clarity

The fetch flow is clearly sequenced with an explicit validation checkpoint (wx-mp-hunter check exit 0/2 branching), consistent exit-code semantics, and recovery loops in Pitfalls (DOM change → probe, token expiry → re-login, rate limit → manual fallback) for this fragile browser-scraping + DB write operation.

3 / 3

Progressive Disclosure

Sections are clearly organized and a bundle script exists, but the SKILL.md is a ~196-line monolith that inlines detail (innerText parsing structure, integration rationale, all pitfalls) rather than splitting it into well-signaled one-level-deep reference files; the script is not explicitly referenced for the parsing logic.

2 / 3

Total

10

/

12

Passed

Description

82%

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 well-targeted with natural trigger terms and a clear, distinct niche, but it omits an explicit 'Use when...' clause so the use-when guidance is only implied. Adding a trigger clause would raise the completeness score.

Suggestions

Append an explicit 'Use when ...' trigger clause, e.g. 'Use when the user asks for WeChat official-account engagement metrics (reads/likes/comments/shares/favorites) for accounts they administer.'

Keep the concrete metric list and target table, but consider adding the platform context ('for the user's own backend-managed accounts') up front to make the when-trigger self-contained.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — running the creator center via camoufox-cli, fetching five named metrics (阅读数/点赞数/评论数/分享数/收藏数), and writing to a specific table (pub_wx_mp). It is comprehensive and names the exact target, not just a domain.

3 / 3

Completeness

Clearly states what the skill does but lacks an explicit 'Use when...' trigger clause, so the 'when' is only implied; per the rubric guideline a missing explicit trigger caps completeness at 2.

2 / 3

Trigger Term Quality

Uses natural terms a user would say ('微信公众号 engagement 数据抓取', '阅读数/点赞数/评论数/分享数/收藏数', 'published-track'); keyword coverage matches common user phrasing for this task.

3 / 3

Distinctiveness Conflict Risk

Targets a narrow, specific niche (WeChat creator-center engagement metrics for one's own accounts written to pub_wx_mp) with distinct triggers, making conflict with other skills unlikely.

3 / 3

Total

11

/

12

Passed

Validation

87%

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

Validation14 / 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

Total

14

/

16

Passed

Repository
TeamWiseFlow/xiaobei
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.