pdf-parser
Pdf Parser - Auto-activating skill for Business Automation. Triggers on: pdf parser, pdf parser Part of the Business Automation skill category.
34
Quality
3%
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
7%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 description is severely underdeveloped, consisting mostly of boilerplate metadata rather than useful content. It fails to describe any concrete capabilities, lacks natural trigger terms users would actually say, and provides no guidance on when Claude should select this skill. The duplicate trigger term and generic category label suggest this may be auto-generated placeholder text.
Suggestions
Add specific actions the skill performs, e.g., 'Extracts text, tables, and images from PDF files. Fills PDF forms, merges multiple PDFs, and converts PDF content to other formats.'
Add a 'Use when...' clause with natural trigger terms: 'Use when the user mentions PDF files, .pdf documents, extracting content from PDFs, filling forms, or merging documents.'
Remove the duplicate trigger term and boilerplate category text - replace with substantive capability descriptions that help Claude distinguish this skill from others.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only 'Pdf Parser' which names the tool but doesn't describe what it does (e.g., extract text, merge, fill forms). 'Auto-activating skill for Business Automation' is abstract filler. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no actions described) and 'when should Claude use it' (no 'Use when...' clause or equivalent guidance). The 'Triggers on' line is not a proper usage guide. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'pdf parser, pdf parser' (duplicated). Users rarely say 'pdf parser' - they would say 'extract from PDF', 'read this PDF', 'convert PDF', etc. Missing natural variations like 'PDF files', '.pdf', 'document extraction'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'PDF' provides some specificity to distinguish from other document types, but 'Business Automation' is very broad and could overlap with many skills. Without specific actions, it's unclear what distinguishes this from other PDF-related skills. | 2 / 3 |
Total | 5 / 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 template with no actual PDF parsing content. It consists entirely of generic placeholder text that could apply to any skill topic. There is no executable code, no specific guidance, and no real information about how to parse PDFs.
Suggestions
Add executable Python code showing how to extract text from PDFs using a specific library like pdfplumber or PyMuPDF
Include concrete examples for common PDF parsing tasks: text extraction, table extraction, and handling multi-page documents
Define a clear workflow with validation steps, especially for handling malformed or encrypted PDFs
Remove all generic boilerplate text and replace with specific, actionable PDF parsing instructions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with zero actionable information. | 1 / 3 |
Actionability | Contains no concrete code, commands, or specific instructions for PDF parsing. The entire content describes what the skill supposedly does without showing how to actually parse a PDF. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, and no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed documentation, no examples file, no API reference. The 'Related Skills' section mentions a category but provides no actual links or navigation. | 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
0c08951
- 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.