document-merger
Document Merger - Auto-activating skill for Business Automation. Triggers on: document merger, document merger Part of the Business Automation skill category.
32
0%
Does it follow best practices?
Impact
92%
1.01xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/19-business-automation/document-merger/SKILL.mdQuality
Discovery
0%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 extremely weak across all dimensions. It essentially restates the skill name without providing any concrete actions, meaningful trigger terms, or guidance on when to use it. The duplicate trigger term and boilerplate category mention add no value.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Combines multiple documents (PDF, Word, text) into a single output file, handles page ordering, and resolves formatting conflicts.'
Add a 'Use when...' clause with natural trigger terms: 'Use when the user asks to merge, combine, join, or concatenate documents, files, or PDFs into one.'
Include supported file types and formats (e.g., .pdf, .docx, .txt) to improve distinctiveness and help Claude differentiate this from other document-processing skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Document Merger' but provides no concrete actions—it doesn't explain what merging entails (e.g., combining PDFs, merging Word documents, concatenating files). The phrase 'Auto-activating skill for Business Automation' is vague filler. | 1 / 3 |
Completeness | The 'what' is extremely weak (just the name 'Document Merger' with no elaboration on capabilities), and the 'when' is essentially absent—'Triggers on: document merger' is a redundant restatement of the skill name, not meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger term listed is 'document merger' repeated twice. It misses natural variations users would say like 'merge documents', 'combine files', 'join PDFs', 'concatenate', specific file types, etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it could overlap with any file-handling, document processing, or PDF skill. There are no distinct triggers or specific file types/formats that would help Claude differentiate this from other document-related skills. | 1 / 3 |
Total | 4 / 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 an empty shell—a template placeholder with no actual instructional content. It describes what a document merger skill would do in abstract terms but provides zero actionable guidance, no code examples, no concrete steps, and no references to supporting materials. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples for merging documents (e.g., using python-docx for Word documents, PyPDF2/pypdf for PDFs) with specific input/output patterns.
Define a clear multi-step workflow: identify input files → validate formats → merge with specific tool/library → validate output → save, with explicit validation checkpoints.
Remove all meta-description sections ('Purpose', 'When to Use', 'Capabilities', 'Example Triggers') that describe the skill rather than teach the task—these waste tokens on information Claude doesn't need.
Add references to advanced topics (e.g., handling different file formats, conflict resolution in merges, batch operations) in separate linked files if needed.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual instructions, code, or actionable content. Every token is wasted on describing the skill rather than teaching how to merge documents. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific steps, no examples of actual document merging. The 'Example Triggers' section just lists phrases to activate the skill, not how to perform the task. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill merely claims it 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, no links to examples or advanced guides, and no meaningful structure beyond boilerplate headings. | 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 | |
- Commit
3e83543
- 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.