document-merger
Document Merger - Auto-activating skill for Business Automation. Triggers on: document merger, document merger Part of the Business Automation skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill document-merger35
Quality
3%
Does it follow best practices?
Impact
92%
1.01xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/19-business-automation/document-merger/SKILL.mdDiscovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a placeholder that provides almost no useful information for skill selection. It repeats the skill name as trigger terms, lacks any concrete action descriptions, and provides no guidance on when Claude should select this skill. The 'Business Automation' category mention adds minimal value.
Suggestions
Add specific actions the skill performs, e.g., 'Combines multiple documents into a single file, supports PDF, Word, and text file merging, handles page ordering and formatting preservation.'
Include a 'Use when...' clause with natural trigger terms like 'combine documents', 'merge files', 'join PDFs', 'consolidate reports', 'append documents'.
Specify supported file types and merge scenarios to distinguish from other document-handling skills (e.g., 'Use when combining contracts, reports, or multi-part documents into unified files').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only says 'Document Merger' without describing any concrete actions. It doesn't explain what merging entails (e.g., combining PDFs, merging Word docs, handling conflicts) - just repeats the skill name. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when to use' guidance. The 'Triggers on' section is not a proper use-case explanation. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'document merger' repeated twice, which is redundant and unlikely to match natural user language. Users would more likely say 'combine documents', 'merge files', 'join PDFs', etc. | 1 / 3 |
Distinctiveness Conflict Risk | While 'document merger' is somewhat specific compared to generic 'helps with documents', the lack of detail about what types of documents or merge operations could cause overlap with PDF skills, Word processing skills, or general file handling skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is entirely meta-content describing what a document merger skill would do, without any actual implementation guidance. It contains no executable code, no specific document formats, no merging strategies, and no concrete instructions. The content is essentially a placeholder that provides zero value to Claude.
Suggestions
Add concrete code examples for merging common document types (e.g., PDFs with pypdf, Word documents with python-docx, or text files)
Define a clear workflow with specific steps: identify input files, validate formats, merge using specific method, validate output
Remove all meta-description ('This skill provides...', 'Capabilities include...') and replace with actual instructions
Include at least one complete, executable example showing input files and expected merged output
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actionable information. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that waste tokens without teaching Claude anything specific about document merging. | 1 / 3 |
Actionability | No concrete code, commands, or specific instructions are provided. The skill describes what it claims to do ('generates production-ready code') but provides zero actual examples, methods, or executable guidance for merging documents. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill mentions 'step-by-step guidance' but provides none. There are no steps, no validation checkpoints, and no actual process for merging documents. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no structure pointing to actual implementation details. There are no references to detailed materials, examples, or supporting documentation. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- 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.