wxwork-moments

Publish content (text + images/video/link) to WeChat Work (企业微信) customer moments via wiseflow-relay. Credentials (corp_id + corp_secret) read from daemon.env and passed per-request; relay is stateless.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

92%

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

The body is concise, highly actionable, and has a clear workflow with a validation checkpoint and error-recovery table. Its main weakness is progressive disclosure: the skill repeatedly directs the agent to a REFERENCE.md that is not shipped in the bundle.

Suggestions

Ship the referenced REFERENCE.md in references/ (or inline the credential-acquisition steps into the body) — it is referenced five times but does not exist in the bundle.

Reference scripts/post_moments.py by path so the agent can locate the underlying script that the `wxwork-moments` wrapper invokes.

Reduce the mild redundancy between the "凭据缺失时 Agent 行为" steps and the Error Handling rows, which both describe the REFERENCE.md → IT engineer → restart flow.

Dimension	Reasoning	Score
Conciseness	The body is lean and table-driven (attachment limits, error handling) with no over-explanation of concepts Claude already knows; each section earns its place, and the credential/error coverage is complementary rather than padded.	3 / 3
Actionability	Copy-paste-ready commands are given for every mode — `wxwork-moments "正文内容"`, image, video, and `--link URL TITLE cover.jpg` — plus a concrete ✓/✗ output contract, so the guidance is fully executable.	3 / 3
Workflow Clarity	The single delegated action is unambiguous, with an explicit validation checkpoint (last line ✓ = success / ✗ = failure) and an error→cause→handling table that provides a feedback loop for recovery.	3 / 3
Progressive Disclosure	The body is well-sectioned and clearly signals a one-level-deep reference ("先读同目录 REFERENCE.md"), but REFERENCE.md is referenced five times yet is absent from the bundle (no references/ directory exists), so the navigation is broken.	2 / 3
	Total	11 / 12 Passed

Description

72%

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 distinctive and uses natural bilingual trigger terms, but it lacks an explicit "Use when..." trigger clause and front-loads implementation detail (credential handling, relay statelessness) that dilutes the capability statement. It reads as a precise integration spec rather than a trigger-rich skill description.

Suggestions

Add an explicit "Use when..." clause, e.g. "Use when the user wants to post or publish to WeChat Work customer moments (企业微信朋友圈)."

Lead with the concrete capability verbs — e.g. "Publish text, image, video, and link posts to WeChat Work customer moments" — before any implementation detail, to lift the specificity listing toward the top anchor.

Trim or defer the credential/relay-statelessness detail, which does not contribute to triggering or capability clarity.

Dimension	Reasoning	Score
Specificity	It names the domain and a concrete action — "Publish content (text + images/video/link) to WeChat Work customer moments" — but the capability is a single publish action with content-type variants rather than the multiple distinct concrete actions the top anchor requires, and much of the prose ("Credentials ... read from daemon.env ... relay is stateless") is implementation detail rather than capability.	2 / 3
Completeness	The "what" is clearly stated, but there is no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Natural bilingual trigger terms are well covered — "WeChat Work (企业微信) customer moments" plus "朋友圈" in the name and "publish content" — terms a user would actually say when requesting this skill.	3 / 3
Distinctiveness Conflict Risk	The niche is sharply specific — "WeChat Work (企业微信) customer moments via wiseflow-relay" — with distinct triggers that are very unlikely to overlap with or misfire for other skills.	3 / 3
	Total	10 / 12 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Path: crews/main/skills/wxwork-moments/SKILL.md
Commit: bcef823

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.