pdf-generator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill pdf-generatorPdf Generator - Auto-activating skill for Business Automation. Triggers on: pdf generator, pdf generator 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 mainly of a skill name and category label without any substantive content. It fails to describe what the skill actually does, provides minimal trigger terms, and offers no guidance on when Claude should use it. This would be nearly useless for skill selection among multiple options.
Suggestions
Add specific capabilities describing what the skill does, e.g., 'Generates PDF documents from text, HTML, or markdown content. Creates invoices, reports, and formatted documents.'
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks to create a PDF, generate a document, make an invoice, or export content to PDF format.'
Expand trigger terms to include natural variations: 'create PDF', 'make PDF', 'export to PDF', 'PDF document', 'generate report', '.pdf file'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only 'Pdf Generator' which is a name, not a capability description. There's no indication of what the skill actually does (create PDFs, convert to PDF, fill PDF forms, etc.). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the vague name, and has no 'Use when...' clause or equivalent guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'pdf generator' repeated twice, which is extremely limited. Missing natural variations users would say like 'create PDF', 'generate PDF', 'make a PDF', 'export to PDF', '.pdf', etc. | 1 / 3 |
Distinctiveness Conflict Risk | While 'PDF Generator' is somewhat specific to PDF creation, the lack of detail about what kind of PDF generation (from what sources? for what purposes?) could cause overlap with other document or PDF-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is entirely meta-content with no actual substance. It describes what the skill supposedly does without providing any concrete guidance on PDF generation - no libraries, no code, no workflows, no examples. The content is a template placeholder that would provide zero value to Claude when actually generating PDFs.
Suggestions
Add concrete, executable code examples for PDF generation using a specific library (e.g., reportlab, weasyprint, or fpdf)
Define a clear workflow with steps: create document structure, add content, style formatting, export/save, and validate output
Remove all meta-description content ('This skill activates when...', 'Capabilities include...') and replace with actual PDF generation instructions
Include specific examples showing input data and expected PDF output structure
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. It explains what triggers the skill and describes capabilities in abstract terms without any concrete information Claude doesn't already know. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance is provided. The entire content describes rather than instructs - there are no actual steps for generating PDFs, no library recommendations, no code examples. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for PDF generation. There are no validation checkpoints or process sequences. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no useful structure. There are no references to detailed materials, no links to examples or API documentation, and no organization of actual PDF generation content. | 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.