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.
Install with Tessl CLI
npx tessl i github:ComposioHQ/awesome-claude-skills --skill pdfOverall
score
95%
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/skillEvaluation — 98%
↑ 2.48xAgent success when using this skill
Validation 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 capabilities and includes explicit trigger conditions. The main weakness is in trigger term coverage, where it could benefit from more natural user language variations and common synonyms for PDF operations.
Suggestions
Add more natural trigger term variations like '.pdf files', 'PDFs', 'combine PDFs', 'split PDF', 'extract from PDF' to improve discoverability
Replace 'programmatically' with more user-friendly language like 'automatically' or 'batch process' since users rarely use technical jargon when requesting help
| 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'). | 3 / 3 |
Trigger Term Quality | Includes 'PDF' multiple times and mentions 'form', 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 the lack of validation/verification steps in workflows and some redundancy in content presentation. The progressive disclosure is well-handled with clear pointers to specialized documentation.
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, especially for file operations and password-protected PDFs
Remove the quick reference table or significantly condense it, as it largely duplicates the section headers and examples already provided
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with executable code examples, but includes some unnecessary verbosity like the full 'Advanced Table Extraction' section and repetitive patterns. The quick reference table at the end duplicates information already shown in examples. | 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 complete, working syntax. | 3 / 3 |
Workflow Clarity | Individual operations are clear, but there are no validation checkpoints or error handling guidance. For operations like merging, splitting, or password protection, there's no verification step to confirm success or handle failures. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections, a quick start, and appropriate references to external files (reference.md, forms.md) for advanced topics. Navigation is straightforward with a helpful quick reference table and 'Next Steps' section. | 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.
- 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.