CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wechat-channels-publish

通过 camoufox-cli 持久化 session wechat-channel 发布视频到微信视频号,支持视频上传、封面上传、视频描述与短标题填写、即时发布。

Quality

79%

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 ./crews/main/skills/expert-wx-channel/tools/wechat-channels-publish/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a dense, highly executable operational runbook: every step has exact commands and selectors, validation checkpoints and retry loops are built in throughout, and pitfalls document real failure signatures. The weaknesses are structural — the same constraints are repeated across sections, inflating token cost, and the whole thing is one monolithic file instead of an overview with split-out references.

Suggestions

Deduplicate rules stated three times (cookie/UA closure, fail-first queue, ~300字 guidance): state each once in 必做约束/Session 共享约束 and reference it from other sections.

Split the login/login-confirm QR protocol and the Pitfalls catalog into references/ files (e.g. LOGIN.md, PITFALLS.md), keeping SKILL.md a lean overview with clear one-level-deep pointers.

Move the dated daemon note (「2026-08-22 起已默认关闭 idle 自退」) into a deprecated/old-patterns note so time-sensitive history does not pad the active workflow.

DimensionReasoningScore

Conciseness

Information density is high and nothing explains concepts Claude already knows, but several rules are restated verbatim three times across sections — 「不导出 cookie/UA」 (前置条件 twice, then Session 共享约束), the fail-first queue (intro, 必做约束, Session 共享约束), and 「约 300 字为建议值」 (输入, Step 6, 入库衔接约束) — plus a dated note (「2026-08-22 起已默认关闭 idle 自退」) sitting inline in a pitfall rather than a deprecated section. The duplication goes beyond the 'minor instances' of anchor 4, so 3 is the best fit.

3 / 5

Actionability

Every step ships copy-paste-ready commands: exact invocations like `camoufox-cli --session wechat-channel --persistent --json open "https://channels.weixin.qq.com/platform/post/create"`, complete eval JS snippets including the mousedown/mouseup/click dispatch walk, scoped selectors such as `input[type=file][accept*="image"]`, the `wechat-channels-publish fill --body @/绝对路径/body.txt` wrapper, and literal error strings to match (「session wechat-channel 正忙」). Covers common cases including fallbacks — matches the fully-executable anchor.

5 / 5

Workflow Clarity

The 8-step flow is clearly sequenced with explicit validation checkpoints and feedback loops: transcode polling via `snapshot -s` state classes with a 3-minute cap and failure signatures, short-title verification by eval-reading `.value` with a re-fill retry loop (「为空 → 重新 fill 再校验」), a disabled-button check before publish, and post-publish confirmation via URL/redirect, backed by an error-handling table with recovery actions. This matches the explicit-validation-with-error-recovery anchor.

5 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), so all ~290 lines live in one SKILL.md. Section headers are good, but self-contained blocks — the login/login-confirm QR protocol, the full Pitfalls catalog, and 入库衔接约束 — are inlined where they clearly belong in separate reference files. Fits 'some structure but content that should be separate is inline'; not 4 because there are no one-level-deep reference files at all for a document of this size.

3 / 5

Total

16

/

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 concrete and comprehensive about what the skill does, listing the complete publish pipeline with specific actions, and occupies a distinct niche. Its main weakness is the complete absence of 'when to use' trigger guidance, which caps completeness, and thin synonym coverage for natural trigger phrases.

Suggestions

Add an explicit trigger clause, e.g. 「Use when the user asks to publish or upload a video to 微信视频号 (WeChat Channels)」, to answer 'when' and lift completeness.

Include natural trigger synonyms such as 「视频号」, 「发视频号」, and "WeChat Channels" so keyword coverage includes the variations users actually say.

State the scope boundary (publishing only — no engagement tracking, no link retrieval) in the description to further reduce overlap with sibling 视频号 skills.

DimensionReasoningScore

Specificity

「支持视频上传、封面上传、视频描述与短标题填写、即时发布」 enumerates the full pipeline as concrete actions and names the mechanism (「通过 camoufox-cli 持久化 session wechat-channel 发布视频到微信视频号」), covering every capability of the tool. It matches the comprehensive-coverage anchor; score 4 would apply only if a capability were left out.

5 / 5

Completeness

The 'what' is clear and concrete (publish videos to WeChat Channels with upload, cover, description and short title), but there is no 'Use when...' clause or equivalent explicit trigger guidance anywhere in the description, which per the judging guidelines caps completeness at 3. Not 2, because the 'what' half is fully present and specific.

3 / 5

Trigger Term Quality

Natural phrases a user would say are present — 「发布视频」, 「微信视频号」, 「封面」, 「短标题」, 「上传」 — giving good keyword coverage, but there are no synonyms or alternate forms (e.g. 「视频号发布」, English "WeChat Channels"), so it falls short of the comprehensive anchor 5 without being merely 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

The platform + action pair (「发布视频到微信视频号」) carves a clear niche that would not fire for unrelated skills, but sibling skills sharing the 视频号 platform terminology (e.g. `wx-channel-engagement`) create minor overlap risk. Fits 'mostly distinct; minor overlap risk with closely related skills'; not 5 because the platform keyword alone is shared.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

TeamWiseFlow/xiaobei

Path

crews/main/skills/expert-wx-channel/tools/wechat-channels-publish/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.