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 ./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 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 PDF processing examples but suffers from significant verbosity—most of the content covers standard library usage that Claude already knows. The workflow lacks validation checkpoints for destructive operations like merging and splitting. The progressive disclosure structure references external files appropriately but keeps too much routine content inline.
Suggestions
Drastically reduce the body to a quick-reference overview with only non-obvious patterns (e.g., OCR pipeline, advanced table extraction), moving standard pypdf/pdfplumber/reportlab usage to reference.md.
Add explicit validation steps after merge/split operations (e.g., verify page count, check file size, open and spot-check output) to create proper feedback loops for destructive operations.
Remove explanations of basic operations Claude already knows (rotate, extract metadata, password protection) or condense them to single-line entries in the quick reference table.
Move the command-line tools section and common tasks to reference.md, keeping only the quick reference table and links in the main skill file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is very verbose with extensive code examples for operations Claude already knows how to perform (basic pypdf, pdfplumber, reportlab usage). The rotate pages, extract metadata, password protection, and watermark sections are all standard library usage that Claude can generate without instruction. The file is well over 200 lines with much redundant content. | 1 / 3 |
Actionability | All code examples are fully executable, copy-paste ready, and use real library APIs with correct syntax. Commands include specific flags and arguments. The quick reference table provides a useful lookup. | 3 / 3 |
Workflow Clarity | There is a brief mention of using mcp-feedback-enhanced for confirming irreversible merge/split operations, but no explicit validation steps or feedback loops are defined for any of the multi-step processes (merge, split, watermark). For destructive batch operations like merging and splitting, there are no verification checkpoints (e.g., confirming page counts after merge). | 2 / 3 |
Progressive Disclosure | References to forms.md and reference.md are present and clearly signaled, which is good. However, the main file contains a large amount of inline content (basic operations, common tasks, CLI tools) that could be split into separate reference files, making the overview too long and reducing its effectiveness as a quick-start guide. | 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-data
- Commit
b1a95aa
- 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.