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 reads like auto-generated boilerplate rather than a useful guide for skill selection. It lacks any concrete actions, meaningful trigger terms, explicit usage guidance, and distinctive characteristics. It would be nearly impossible for Claude to reliably select this skill over others based on this description alone.
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 asks to read, parse, or extract data from PDF files, or mentions .pdf files, document parsing, or PDF text extraction.'
Remove the duplicate trigger term 'pdf parser' and expand with natural variations users would actually say, such as 'read PDF', 'extract from PDF', 'PDF text', 'parse document', '.pdf'.
| 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 too vague to be distinctive. 'Business Automation' is extremely broad and could overlap with many other skills. There are no specific triggers or capabilities that would help distinguish this from other document or automation 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 is an empty placeholder with no actual content about PDF parsing. It contains only generic boilerplate descriptions of what a skill would do, without any concrete instructions, code examples, library recommendations, or workflows. It provides zero value beyond what the skill's title alone conveys.
Suggestions
Add concrete, executable code examples for PDF text extraction using a specific library (e.g., pdfplumber or PyMuPDF), including installation commands and working code snippets.
Define a clear workflow for common PDF parsing tasks: extracting text, extracting tables, handling multi-page documents, with validation steps for output quality.
Remove all generic boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actionable content—specific patterns, error handling, and edge cases for PDF parsing.
Add concrete examples showing input (PDF characteristics) and expected output (extracted data format) so Claude knows exactly what to produce.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, provides no specific information about PDF parsing, and wastes tokens on generic phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' without any actual substance. | 1 / 3 |
Actionability | There is zero concrete, executable guidance. No code examples, no specific commands, no library recommendations, no actual instructions for parsing PDFs. The entire content describes what the skill supposedly does without ever doing it. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequences, no validation checkpoints—just vague claims about providing 'step-by-step guidance' without any actual steps. | 1 / 3 |
Progressive Disclosure | No references to external files, no structured navigation, and no bundle files exist. The content is a monolithic block of generic placeholder text with no meaningful organization or layered information architecture. | 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
3a2d27d
- 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.