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.
84
75%
Does it follow best practices?
Impact
100%
1.17xAverage score across 3 eval scenarios
Passed
No known issues
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', '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 document-type skills due to the specific PDF focus and enumerated capabilities. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%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 for PDF processing but is far too verbose for a SKILL.md—most of the content is standard library usage that Claude already knows and could generate on demand. The content would benefit greatly from being condensed to a quick-reference overview with key decisions (which tool for which task) and delegating detailed examples to reference files. Workflow clarity suffers from missing validation steps for destructive operations.
Suggestions
Drastically reduce the body to a decision table (which tool for which task) and 1-2 key examples that show non-obvious patterns, moving detailed code examples to reference.md
Add explicit validation/verification steps for merge and split workflows (e.g., verify page count after merge, check output file size, open and validate result)
Remove explanations of basic library usage (pypdf read, pdfplumber extract_text, reportlab canvas) that Claude can generate without instruction—focus on gotchas, edge cases, and tool selection criteria
Move the bulk of code examples into reference.md and keep SKILL.md as a concise overview with the quick reference table and links to detailed guides
| 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 reads like a tutorial/reference manual rather than a skill that adds novel knowledge. Much of this is standard library usage that Claude can generate on demand. | 1 / 3 |
Actionability | All code examples are fully executable, copy-paste ready, and cover concrete operations with specific libraries and commands. The examples include imports, complete function calls, and file I/O. | 3 / 3 |
Workflow Clarity | While individual operations are clear, there are no validation checkpoints or feedback loops for destructive operations like merging/splitting. The interactive processing section mentions confirming operations but doesn't integrate validation steps into the actual workflows. For batch merge/split operations, missing validation caps this at 2. | 2 / 3 |
Progressive Disclosure | References to forms.md and reference.md are present and clearly signaled, which is good. However, the main file contains ~200 lines of detailed code examples that could be split into separate reference files, making the SKILL.md itself a monolithic wall of code rather than a concise overview pointing to detailed materials. | 2 / 3 |
Total | 8 / 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
dea85ce
- 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.