document-merger
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill document-mergerDocument Merger - Auto-activating skill for Business Automation. Triggers on: document merger, document merger Part of the Business Automation skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially just restating the skill name without providing actionable information. It lacks concrete capabilities, natural trigger terms, and explicit usage guidance. The redundant trigger terms and boilerplate category information add no value for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Combines multiple documents into a single file, supports PDF, Word, and text files, preserves formatting and page order'
Include a 'Use when...' clause with natural trigger terms like 'combine documents', 'merge files', 'join PDFs', 'concatenate pages', 'put together multiple files'
Specify supported file formats (.pdf, .docx, .txt) to distinguish from other document skills and help Claude select appropriately
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Document Merger' without describing any concrete actions. It doesn't explain what merging entails (e.g., combining PDFs, merging Word documents, handling different file formats). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no explicit 'when to use' guidance. The 'Triggers on' line is redundant and doesn't constitute proper usage guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'document merger' repeated twice. This misses natural variations users would say like 'combine documents', 'merge files', 'join PDFs', 'concatenate', or specific file types. | 1 / 3 |
Distinctiveness Conflict Risk | While 'document merger' is somewhat specific to merging functionality, the lack of file type specificity (PDF, Word, etc.) could cause overlap with other document-handling skills. The term 'document' is quite broad. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder with no substantive content. It describes capabilities it doesn't demonstrate and promises guidance it doesn't provide. The entire content could be replaced with actual document merging instructions (file formats supported, libraries to use, code examples) to become useful.
Suggestions
Add executable code examples showing how to merge common document types (PDFs, Word docs, spreadsheets) using specific libraries
Define a clear workflow: 1) identify input formats, 2) validate inputs, 3) merge using appropriate method, 4) validate output
Remove all meta-description content ('This skill provides...', 'Capabilities include...') and replace with actual instructions
Include specific examples of input/output for at least one document merge scenario (e.g., merging two PDFs with pdfplumber or PyPDF)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic filler that provides no actionable information. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague platitudes 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 marketing-style text with no structure for actual learning. No references to detailed documentation, no links to examples, and no organization beyond generic section headers. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 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.