merge4docx

将多个 Word 文档合并为一个文件。当用户提到 Word 合并、合并 docx、合并多个 Word 时使用。

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/word/merge4docx/SKILL.md

Quality

Content

65%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, actionable, single-purpose skill with clean section organization. Its weaknesses are a duplicated code example and the absence of any validation/verification for what is a batch merge operation.

Suggestions

Remove or differentiate the "使用示例" section — it currently duplicates "调用方式"; instead show the two distinct input modes (a file list vs an entire folder) to improve both conciseness and actionability.

Add a validation/verification step after the merge (e.g., confirm the output .docx opens/is valid and that the input file count matches) so the batch operation is not left unverified, which would lift workflow_clarity above 3.

Drop the redundant blockquote that repeats the description to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient (no concept over-explanation), but the "使用示例" section duplicates the "调用方式" code and the blockquote repeats the description, adding unnecessary tokens; this fits anchor 3 ('mostly efficient but some unnecessary content') rather than the trimmer anchor 4.	3 / 5
Actionability	Provides copy-paste-ready Python with a full import and a complete parameter table, fitting anchor 4's 'mostly executable guidance with minor gaps'; it stops short of 5 because the two near-identical examples do not illustrate the distinct input modes (file list vs folder) named in the description.	4 / 5
Workflow Clarity	The single merge call is unambiguous, but merging multiple files is a batch operation and the body has no validation/verification step (no check that the output is a valid docx or that all inputs were processed), which caps the score at 3 per the rubric's batch-operation rule.	3 / 5
Progressive Disclosure	The body is under 50 lines, has no bundle files and no need for external references, and is organized into clearly labeled sections, satisfying the simple-skills exception for a 5 at anchor 5.	5 / 5
	Total	15 / 20 Passed

Description

78%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 well-structured Chinese description that explicitly covers both capability and usage triggers in the recommended pattern. Its main weakness is single-action specificity and slightly incomplete keyword coverage (no explicit .docx extension).

Suggestions

Add the explicit '.docx' file extension and a synonym (e.g., 'Word文档合并') to the trigger clause to push trigger_term_quality toward 5.

Mention the input flexibility concretely in the description (e.g., 'from a file list or an entire folder') to lift specificity beyond a single action.

Dimension	Reasoning	Score
Specificity	Names the domain (Word/docx) and one concrete action ("合并为一个文件" / merge into one file), matching anchor 3's 'domain and 1-2 concrete actions, not comprehensive'; it does not list several distinct actions needed for a 4.	3 / 5
Completeness	Clearly states what it does ("将多个 Word 文档合并为一个文件") and gives an explicit "当用户提到…时使用" (Use when...) clause with concrete triggers, matching the anchor-5 example pattern exactly; not below 4 because both what and when are explicit and specific.	5 / 5
Trigger Term Quality	Includes several natural user phrases ("Word 合并", "合并 docx", "合并多个 Word") giving good keyword coverage, but omits the explicit ".docx" file extension and some synonyms expected at anchor 5.	4 / 5
Distinctiveness Conflict Risk	The merge niche is clear with distinct merge-specific triggers and minimal conflict risk, but the broad "Word document" domain carries minor overlap with other Word skills, fitting anchor 4 rather than the fully-distinct anchor 5.	4 / 5
	Total	16 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: CoderWanFeng/python-office
Path: skills/word/merge4docx/SKILL.md
Commit: dd6fe56

Reviewed: 1 day 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.