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.
82
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 'when' guidance. The main weakness is trigger term coverage - while functional, it could include more natural user variations like '.pdf' files or 'combine PDFs'. The description uses proper third-person voice throughout.
Suggestions
Add more natural trigger term variations users might say, such as '.pdf', 'PDFs', 'combine PDFs', 'split PDF', or 'PDF extraction'
| 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 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'). Has explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes 'PDF' multiple times and mentions 'form', 'text', 'tables', but misses common variations users might say like '.pdf', 'PDFs', 'document extraction', or 'combine PDFs'. The term 'programmatically' is more technical than natural user language. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly focused on PDF-specific operations with distinct triggers. The combination of 'PDF form', 'merging/splitting', and 'PDF documents' creates a clear niche 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 a wide range of operations. The main weaknesses are some verbosity that could be trimmed and missing validation/error-handling steps in multi-step workflows. The progressive disclosure and organization are well done with clear navigation to related files.
Suggestions
Add validation steps after critical operations (e.g., verify merged PDF page count, check output file exists and is readable)
Include basic error handling patterns for common failures like FileNotFoundError, encrypted PDFs, or corrupted files
Trim the Overview section - Claude doesn't need to be told what the guide covers when the structure is self-evident
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with executable code examples, but includes some unnecessary verbosity like the 'Overview' section explaining what the guide covers, and some examples could be more compact. The quick reference table is helpful but duplicates information already shown. | 2 / 3 |
Actionability | Excellent actionability with fully executable, copy-paste ready code examples for every operation. Both Python code and command-line tools are provided with specific, working commands and complete import statements. | 3 / 3 |
Workflow Clarity | Individual operations are clear, but multi-step workflows lack validation checkpoints. For example, the merge/split operations don't include verification steps to confirm success, and there's no error handling guidance for common failure modes like corrupted PDFs or permission issues. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections and appropriate references to external files (reference.md, forms.md). The quick start section provides immediate value, and advanced topics are properly signaled with one-level-deep references. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.