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.
86
Quality
78%
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
85%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 articulates specific PDF manipulation capabilities and includes explicit trigger guidance. The main weakness is the trigger term coverage could be expanded to include more natural user language variations like '.pdf' files or 'combine PDFs'.
Suggestions
Add more natural trigger term variations users might say, such as '.pdf', 'PDFs', 'combine PDFs', 'extract from PDF', or 'PDF reader'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'extracting text and tables', 'creating new PDFs', 'merging/splitting documents', and 'handling forms'. Uses third person voice correctly. | 3 / 3 |
Completeness | Clearly answers both what ('extracting text and tables, creating new PDFs, merging/splitting documents, handling forms') and when ('When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents'). | 3 / 3 |
Trigger Term Quality | Includes 'PDF' multiple times and mentions 'form', 'text', 'tables', but missing common user variations like '.pdf', 'PDFs', 'document extraction', or file-specific terms users might naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly focused on PDF-specific operations with distinct triggers like 'PDF form', 'merging/splitting', and 'PDF documents'. Unlikely to conflict with general document or text processing skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%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 code examples covering common operations. The main weaknesses are some verbosity in showing similar patterns repeatedly and missing explicit validation steps for batch/destructive operations. The progressive disclosure and organization are well-executed with clear pointers to specialized documentation.
Suggestions
Add explicit validation checkpoints to merge/split workflows (e.g., 'Verify page count before and after merge: `len(reader.pages)`')
Consolidate similar code patterns - the merge/split/rotate examples could share a common pattern explanation rather than repeating full boilerplate
Remove the bilingual section header '交互式处理 (Interactive Processing)' - use consistent language throughout
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with executable code examples, but includes some redundancy (multiple similar operations shown in full) and the bilingual section header is unnecessary. Some sections could be consolidated. | 2 / 3 |
Actionability | Excellent actionability with fully executable, copy-paste ready code examples for every operation. Both Python and command-line approaches are provided with complete, working code snippets. | 3 / 3 |
Workflow Clarity | While individual operations are clear, there are no explicit validation checkpoints for destructive operations like merging/splitting. The interactive processing note mentions confirmation but doesn't integrate validation steps into the workflows themselves. | 2 / 3 |
Progressive Disclosure | Well-structured with clear overview, organized sections by tool/task, and appropriate references to external files (reference.md, forms.md) for advanced features. Navigation is straightforward with a helpful quick reference table. | 3 / 3 |
Total | 10 / 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.
6213d1a
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.