Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.
95
82%
Does it follow best practices?
Impact
97%
2.48xAverage score across 10 eval scenarios
Risky
Do not use without reviewing
Quality
Discovery
100%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 is a strong skill description that clearly enumerates specific PDF manipulation capabilities and provides an explicit 'when' clause for triggering. It uses third-person voice appropriately and includes natural trigger terms users would use. The description is concise yet comprehensive, covering both the breadth of capabilities and the conditions under which the skill should be selected.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'extracting text and tables', 'creating new PDFs', 'merging/splitting documents', and 'handling forms'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (extracting text/tables, creating PDFs, merging/splitting, handling forms) and 'when' ('When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale'). The 'when' clause is explicit. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'PDF', 'text', 'tables', 'merging', 'splitting', 'forms', 'PDF form', 'generate', 'analyze PDF documents'. Good coverage of common variations and use cases. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to PDF manipulation with distinct triggers like 'PDF form', 'merging/splitting documents', 'PDF documents'. Unlikely to conflict with other skills due to the specific PDF focus and enumerated capabilities. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable PDF processing guide with excellent executable code examples covering a wide range of tasks. Its main weaknesses are the lack of validation/verification steps in multi-step workflows and the amount of inline content that could benefit from being split into referenced files. The content is practical and well-organized but could be more concise by trimming redundant examples and trusting Claude's ability to generalize from fewer demonstrations.
Suggestions
Add validation checkpoints to multi-step workflows (e.g., verify merged PDF page count matches expected total, check output file exists and is non-zero bytes after write operations).
Move detailed library-specific examples (reportlab, CLI tools) into reference.md and keep only the most essential quick-start examples inline to improve conciseness and progressive disclosure.
Add error handling guidance for common failure modes (e.g., encrypted PDFs without passwords, corrupted files, missing tesseract installation).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with executable code examples, but includes some redundancy (e.g., multiple similar merge/split examples across pypdf and CLI tools, the quick reference table partially duplicates what's already shown). Some sections like 'Extract Metadata' and 'Rotate Pages' are straightforward operations Claude could derive without full examples. | 2 / 3 |
Actionability | Every section provides fully executable, copy-paste ready code with proper imports and complete examples. Both Python and CLI approaches are covered with concrete commands and real code, not pseudocode. | 3 / 3 |
Workflow Clarity | The skill presents individual operations clearly but lacks validation checkpoints or feedback loops. For operations like merging, watermarking, or encrypting PDFs, there are no verification steps (e.g., confirming output file integrity, checking page counts after merge). The OCR workflow doesn't mention checking tesseract installation or handling failures. | 2 / 3 |
Progressive Disclosure | References to forms.md and reference.md are well-signaled and appear to be one level deep, which is good. However, the main SKILL.md itself is quite long with extensive inline code that could be split into separate files (e.g., CLI tools reference, reportlab examples). The balance between overview and detail leans too heavily toward inline content. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
ce01116
Table of Contents
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.