CtrlK
BlogDocsLog inGet started
Tessl Logo

wecom-doc

当用户提到企业微信文档、智能表格、创建文档、编辑文档、写文档时启用。优先复用 wecom channel 自动写入的文档 MCP 配置,并通过 mcporter 调用文档能力。

75

Quality

95%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

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

A lean, highly actionable skill body: concrete commands with specific arguments, a clearly sequenced check-configure-call workflow with validation and error-recovery feedback loops, and clean single-file organization. It respects Claude's intelligence and gives copy-paste-ready guidance throughout.

DimensionReasoningScore

Conciseness

The body is action-dense and assumes Claude's competence, with no padding explaining what WeCom or mcporter is; nearly every line is a command, an arg value, or a short directive that earns its place.

3 / 3

Actionability

Provides fully executable commands (npm install -g mcporter, mcporter list wecom-doc --output json, mcporter config add … --type --url, mcporter daemon start) with specific args (doc_type: 3 / 10); placeholders like <url> are justified by the instruction to read values dynamically rather than hardcode them.

3 / 3

Workflow Clarity

The check-configure-call sequence is clearly numbered, with explicit validation checkpoints ("添加完成后再次执行 mcporter list … 进行验证", "配置完成后重新执行") and an error-handling section that maps return codes (850001, help_message, daemon not running) to recovery actions.

3 / 3

Progressive Disclosure

A self-contained single-purpose workflow (~120 lines) with no bundle files and well-organized section headings; nothing here is a large reference block that should be externalized, so a single well-structured file navigates cleanly.

3 / 3

Total

12

/

12

Passed

Description

90%Weight 40%Scale 1-3

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 focused, well-triggered description that clearly defines when to use the skill and carves out a distinct niche. The main weakness is specificity: it summarizes capabilities as '调用文档能力' rather than listing the concrete create/edit actions it supports.

Suggestions

List concrete capabilities explicitly (e.g., '创建企业微信文档与智能表格、编辑机器人创建的文档') instead of the generic '调用文档能力'.

Keep the existing trigger phrase, but pair the 'what' with one or two specific verbs so the capability set is unambiguous at a glance.

DimensionReasoningScore

Specificity

Names the domain (企业微信文档/智能表格) and a concrete action ("通过 mcporter 调用文档能力" / reusing the wecom MCP config), but condenses capabilities into the single phrase "调用文档能力" rather than enumerating multiple specific actions.

2 / 3

Completeness

Explicitly answers 'when' via the trigger clause ("当用户提到…时启用") and states 'what' (reuse wecom channel's auto-written doc MCP config and call doc capabilities through mcporter); the explicit 'Use when'-equivalent trigger is present so completeness is not capped at 2.

3 / 3

Trigger Term Quality

Lists natural user phrasings — 企业微信文档、智能表格、创建文档、编辑文档、写文档 — that a user would genuinely say when needing this skill, with good coverage and no jargon.

3 / 3

Distinctiveness Conflict Risk

Scoped to a clear niche (企业微信文档/智能表格 via mcporter) with distinct triggers unlikely to fire for unrelated skills.

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
BytePioneer-AI/openclaw-china
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.