pdf-parser
Pdf Parser - Auto-activating skill for Business Automation. Triggers on: pdf parser, pdf parser Part of the Business Automation skill category.
31
0%
Does it follow best practices?
Impact
86%
1.01xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/19-business-automation/pdf-parser/SKILL.mdQuality
Discovery
0%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 an extremely weak skill description that fails on all dimensions. It provides no concrete actions, no natural trigger terms, no 'when to use' guidance, and no distinguishing characteristics. It reads like auto-generated boilerplate rather than a useful skill description.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Extracts text, tables, and metadata from PDF files, converts PDF content to structured data for business workflows.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs to parse PDFs, extract data from PDF documents, read .pdf files, or convert PDF content to text or structured formats.'
Remove the duplicate trigger term 'pdf parser' and expand with natural variations users would actually say, such as 'read PDF', 'extract from PDF', 'PDF data extraction', '.pdf files'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only states 'Pdf Parser' and 'Business Automation' without describing what the skill actually does (e.g., extract text, parse tables, fill forms). | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'pdf parser' repeated twice. These are not natural terms users would say — users are more likely to say 'extract text from PDF', 'read PDF', or 'parse this document'. The triggers are extremely narrow and redundant. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it could overlap with any document processing or PDF-related skill. 'Business Automation' is a broad category that provides no meaningful differentiation from other skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is an empty shell—a template with no actual instructional content. It contains only meta-descriptions of what the skill supposedly does without providing any concrete guidance, code examples, or workflows for PDF parsing. It fails on every dimension because it teaches nothing and wastes tokens on self-referential descriptions.
Suggestions
Replace the entire body with actual PDF parsing instructions, including executable code examples using a specific library (e.g., pdfplumber or PyMuPDF) with copy-paste ready snippets.
Add a concrete workflow with steps: e.g., 1) Install library, 2) Extract text, 3) Handle tables, 4) Validate output—with specific commands at each step.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill rather than teaching the task—these waste tokens on information Claude doesn't need.
Include at least one complete, executable example showing input (a PDF scenario) and expected output (extracted text/data) to make the skill actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual instructions, code, or concrete guidance. Every token is wasted on describing the skill rather than teaching anything. | 1 / 3 |
Actionability | There is zero actionable content—no code, no commands, no specific steps, no examples of PDF parsing. The 'capabilities' section lists vague promises like 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints—just abstract claims about what the skill can do without any actual process. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no references to detailed materials, no links to examples or API references, and no meaningful structure beyond boilerplate headings. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
c8a915c
- 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.