wxwork-drive

Manage spaces, folders and files in WeChat Work WeDrive (企业微信微盘) via wiseflow-relay — create space, create folder, upload image/video, list, info, rename, move, delete, and share files via file-level share link. Standard flow 建空间 → 传文件 → file-share 发分享链接给同事. Credentials (corp_id + corp_secret) read from daemon.env and passed per-request; relay is stateless. Space/folder IDs cached locally in spaces.json.

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/wxwork-drive/SKILL.md

Quality

Content

77%

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

Highly actionable, well-sequenced content with a clear main workflow and error-recovery table, held back by repeated inline explanation and references that don't resolve to real bundle files. Consolidating the share explanation and materializing the referenced files would tighten it considerably.

Suggestions

State the file-share-vs-space-share / 640028 rationale once in a single callout and reference it elsewhere instead of repeating the full explanation in four places.

Create the referenced bundle files (REFERENCE.md, spaces.example.json, docs/WXWORK-DRIVE-API.md) so the signaled one-level-deep references actually resolve, or remove the dangling references and inline only what is needed.

Move the per-subcommand flag/error detail that is not needed for the main flow into the API reference doc to reduce inline bulk.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command-table-driven content with little concept re-explanation, but the file-share vs space-share / 640028 explanation is repeated four or more times (header callout, command-table note, '为什么主链路' block, 特殊用途 table, return-values), which is padding that could be consolidated.	2 / 3
Actionability	Provides fully executable commands (e.g. 'wxwork-drive space-create main wiseflow素材 --default'), concrete flags, a copy-paste end-to-end flow, and a precise return-field specification — copy-paste ready.	3 / 3
Workflow Clarity	The main chain (建空间 → 建文件夹 → 上传 → file-share) is clearly sequenced with numbered steps, an explicit 'extract fileid from previous JSON' rule, and an error-handling table that supplies the recovery feedback loop for batch/destructive operations.	3 / 3
Progressive Disclosure	References like REFERENCE.md, spaces.example.json and docs/WXWORK-DRIVE-API.md are signaled but are not real bundle files (only scripts/drive.py exists), and substantial API/error detail is inlined rather than split into the referenced files; structure is present but references are not one-level-deep real files.	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.

A specific and distinctive description that clearly states what the skill does, weakened only by the absence of an explicit 'Use when...' trigger clause. Adding an explicit usage-trigger sentence would lift completeness to full marks.

Suggestions

Append an explicit trigger clause, e.g. 'Use when managing WeChat Work WeDrive (企业微信微盘) files and spaces, or when the user wants to upload and share files to colleagues via 微盘.'

Drop the implementation detail ('Credentials read from daemon.env... relay is stateless... cached in spaces.json') from the description — it dilutes the trigger signal and belongs in the body.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('create space, create folder, upload image/video, list, info, rename, move, delete, and share files via file-level share link'), matching the anchor for enumerating specific concrete actions.	3 / 3
Completeness	Clearly answers 'what' with detailed actions, but provides only an implied 'when' (no explicit 'Use when...' or equivalent trigger guidance), which per the rubric caps completeness at 2.	2 / 3
Trigger Term Quality	Includes natural terms a user needing this would say — 'WeChat Work WeDrive', '企业微信微盘', 'spaces, folders and files', 'share link' — giving good coverage of likely trigger phrasings.	3 / 3
Distinctiveness Conflict Risk	Targets a very specific niche (企业微信微盘 via wiseflow-relay with file-level share), making it unlikely to trigger for the wrong skill.	3 / 3
	Total	11 / 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: skills/wxwork-drive/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.