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.
80
68%
Does it follow best practices?
Impact
100%
1.17xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/data/06-office-pdf/SKILL.mdQuality
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', 'form', 'fill in a 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
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides comprehensive, executable code examples covering a wide range of PDF operations, which is its primary strength. However, it is excessively verbose for a skill file—most of these code patterns are well within Claude's existing knowledge and don't need to be spelled out. The lack of validation workflows for destructive operations (merge/split) and the monolithic structure significantly weaken its effectiveness as a skill guide.
Suggestions
Drastically reduce the content to only project-specific conventions, preferred libraries, and non-obvious patterns—Claude already knows how to use pypdf, pdfplumber, and reportlab from training data.
Add explicit validation workflows for merge/split operations (e.g., verify page counts before and after, check file sizes, confirm with user before overwriting).
Move the bulk of code examples (reportlab creation, CLI tools, OCR, watermarking) into reference.md and keep SKILL.md as a concise overview with the quick reference table and pointers to detailed files.
Include error handling patterns and recovery steps for common failure modes (corrupted PDFs, password-protected files, missing dependencies) rather than happy-path-only examples.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is very verbose, including many code examples that Claude already knows how to write (basic pypdf usage, reportlab canvas creation, pdftotext commands). It explains common operations at length rather than providing only what Claude wouldn't already know. The file reads like a tutorial rather than a concise skill reference. | 1 / 3 |
Actionability | All code examples are fully executable and copy-paste ready. Specific libraries, commands, and complete code snippets are provided for every task, with no pseudocode or vague instructions. | 3 / 3 |
Workflow Clarity | There are no validation checkpoints or feedback loops for destructive operations like merging/splitting PDFs. The interactive processing section mentions confirming operations but doesn't integrate this into actual workflows. Steps are presented as isolated code snippets rather than sequenced workflows with error handling. | 1 / 3 |
Progressive Disclosure | References to forms.md and reference.md are present and clearly signaled, but the main file contains far too much inline content that could be split into separate files (e.g., command-line tools, reportlab creation, OCR). The quick reference table is helpful but the body is monolithic. | 2 / 3 |
Total | 7 / 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.
- Repository
- majiayu000/claude-skill-registry
- Commit
632759f
- 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.