pdf-parser
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill pdf-parserPdf Parser - Auto-activating skill for Business Automation. Triggers on: pdf parser, pdf parser Part of the Business Automation skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, consisting only of a skill name, redundant trigger terms, and a generic category label. It provides no information about what the skill actually does or when Claude should select it, making it nearly useless for skill selection among multiple options.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Extracts text, tables, and images from PDF documents, parses structured data, converts PDF to other formats').
Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user mentions PDF files, .pdf documents, extracting content from PDFs, or parsing PDF data').
Remove the redundant trigger term and expand to include variations like 'PDF', 'pdf file', 'read PDF', 'extract from PDF', 'parse document'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only says 'Pdf Parser' and 'Business Automation' without describing any concrete actions. There are no verbs or specific capabilities listed like 'extract text', 'parse tables', or 'convert documents'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'pdf parser' repeated twice. This misses natural user language like 'PDF', 'extract from PDF', 'read PDF', '.pdf files', or 'document extraction'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'pdf parser' is somewhat specific to PDF handling, the vague 'Business Automation' category and lack of specific capabilities could cause overlap with other document processing or automation skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is a template placeholder with no actual PDF parsing content. It contains only meta-descriptions of what a skill should do without any executable code, specific libraries, concrete examples, or actionable guidance. The content would be entirely useless for actually parsing PDFs.
Suggestions
Add executable Python code showing how to extract text from PDFs using a specific library like pdfplumber or PyMuPDF
Include concrete examples with input/output showing text extraction, table extraction, or form field reading
Remove all meta-descriptions ('This skill provides...', 'Capabilities include...') and replace with actual implementation guidance
Add specific workflow steps for common PDF parsing tasks like handling multi-page documents, extracting tables, or dealing with scanned PDFs
| 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 meaningful structure or references to detailed materials. The sections are organizational theater with no actual content to disclose progressively. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 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.