CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

expert-wx-mp

微信公众号运营专家。承接从定位起号、选题写作、排版发布到数据复盘的完整运营工作。用户只需要说目标和给素材,具体流程和平台规则由专家自己把握。零散的发布、取数、排版等操作也可以直接做。

Quality

78%

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

Fix and improve this skill with Tessl

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

Quality

Content

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

A lean, well-structured orchestration skill: clear workflow routing, concrete tool commands and storage conventions, and an explicit safety checkpoint (user confirmation before DNA write-back). The only weaknesses are minor — a repeated instruction about scattered operations and the absence of command invocation examples.

DimensionReasoningScore

Conciseness

The body is dense and efficient — routing tables, short bullets, and specific paths with no explanations of concepts Claude already knows. Minor trimming is possible because the 'use the tools directly for scattered operations' instruction is repeated in three places (the section intro, '零散操作…直接用下面的工具', and again under '## 工具清单'), placing it just below anchor 5.

4 / 5

Actionability

The body provides concrete, executable routing: named shell commands ('wechat-style-profiler', 'generate-wenyan-theme', 'wx-mp-publisher', 'wx-mp-engagement'), concrete paths and defaults ('wx_mp/dna/', default 'dna-0', 'wx_mp/wenyan-theme/'), and a scenario→workflow table. It stops short of anchor 5 because no invocation examples or arguments are shown for the commands.

4 / 5

Workflow Clarity

The scenario table clearly sequences routing with explicit trigger conditions, and a validation checkpoint exists for the risky write-back path ('建议经用户逐条确认后走 Style DNA Workflow 回写 DNA') plus a mandatory next-step rule for reviews. It is not 5 because individual workflows lack explicit step sequences with validation loops, and not 3 because checkpoints like user confirmation and the review-to-DNA feedback loop are present.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are all absent), and the 49-line body needs none: it is a well-organized index with clear section headers that routes to external logical resources by name while explicitly warning not to treat them as workspace paths. Per the rubric's simple-skill note, well-organized sections with no need for external references merit 5.

5 / 5

Total

17

/

20

Passed

Description

70%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, specific description that names the niche and a concrete pipeline of operations with natural Chinese trigger vocabulary. Its main weakness is the absence of an explicit 'Use when…' trigger clause, which leaves the invocation conditions only weakly implied.

Suggestions

Add an explicit trigger clause, e.g. '当用户要发公众号、写公众号文章、做排版、复盘公众号数据时使用' — a sentence stating when this skill should be invoked would raise completeness from 3.

Trim the vague filler sentence ('具体流程和平台规则由专家自己把握…') or replace it with one or two additional concrete capabilities (e.g. 对标账号分析、排版主题生成) to improve specificity and keyword coverage.

Include common user phrasings/synonyms such as 写推文/写文章 or 小绿书 so the description matches more of the natural terms users say.

DimensionReasoningScore

Specificity

The description lists several concrete operations across the operations pipeline ('定位起号、选题写作、排版发布到数据复盘' plus '零散的发布、取数、排版等操作'), though one sentence is vague filler ('具体流程和平台规则由专家自己把握') and coverage of capabilities like benchmark analysis or theme generation is missing. It fits anchor 4 (several specific actions, minor gaps), not 5 (not comprehensive) and not 3 (well more than 1-2 actions).

4 / 5

Completeness

The 'what' is clear (full operations ownership from positioning to data review, plus scattered single operations), but the 'when' is only weakly implied — there is no 'Use when…' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 4 because the usage conditions are not explicitly stated.

3 / 5

Trigger Term Quality

Natural domain keywords a user would actually say are present: 公众号, 运营, 发布, 排版, 选题, 复盘, 起号, 定位. Good keyword coverage, but common variations like 写推文/写文章 or content types like 小绿书 are absent, so it falls between anchors 3 and 4, noticeably above the midpoint.

4 / 5

Distinctiveness Conflict Risk

The description occupies a clear niche (微信公众号运营) with distinct domain-specific triggers (起号, 排版, 选题, 复盘), giving minimal conflict risk with other skills. This clearly matches anchor 5.

5 / 5

Total

16

/

20

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.

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

Path

crews/main/skills/expert-wx-mp/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.