pdf-generator
Pdf Generator - Auto-activating skill for Business Automation. Triggers on: pdf generator, pdf generator Part of the Business Automation skill category.
34
0%
Does it follow best practices?
Impact
100%
1.04xAverage 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-generator/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 description is extremely weak across all dimensions. It provides no concrete actions, no meaningful trigger terms beyond a duplicated keyword, no 'when to use' guidance, and nothing to distinguish it from other skills. It reads as an auto-generated placeholder rather than a useful skill description.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates PDF documents from templates, converts HTML to PDF, creates invoices and reports in PDF format'.
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a PDF, generate a report, export to PDF, build an invoice, or produce a printable document'.
Remove the duplicated trigger term and expand with natural keyword variations users would actually say, such as 'create PDF', 'export PDF', 'PDF report', 'invoice PDF', 'generate document'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only says 'Pdf Generator' and 'Business Automation' without listing any concrete actions like creating, formatting, converting, or populating PDFs. No specific capabilities are described. | 1 / 3 |
Completeness | The 'what' is extremely vague (just 'Pdf Generator') and there is no explicit 'when' clause explaining when Claude should select this skill. The 'Triggers on' line is just a repeated keyword, not meaningful guidance. | 1 / 3 |
Trigger Term Quality | The only trigger term listed is 'pdf generator' (duplicated). It misses natural variations users would say like 'create PDF', 'generate PDF', 'make a PDF', 'export to PDF', '.pdf', or 'PDF report'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so generic that it could conflict with any PDF-related skill or any business automation skill. There is nothing to distinguish it from other PDF or document generation tools. | 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 shell—it contains only meta-descriptions and trigger phrases but provides absolutely no actionable content for PDF generation. There are no code examples, no library recommendations, no workflows, and no concrete guidance of any kind. It fails on every dimension of the rubric.
Suggestions
Replace the abstract capability descriptions with concrete, executable code examples for PDF generation (e.g., using reportlab, weasyprint, or fpdf2 with copy-paste-ready snippets).
Add a clear workflow with steps: define content → generate PDF → validate output, including validation checkpoints such as checking file size or opening the generated PDF.
Remove the 'When to Use', 'Example Triggers', and 'Capabilities' sections which are meta-information that wastes tokens, and replace them with actual technical guidance.
Include specific examples showing common PDF generation patterns (e.g., invoices, reports, tables) with input data and expected output descriptions.
| 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 section restates the same vague information. | 1 / 3 |
Actionability | There is zero actionable content—no code, no commands, no specific steps, no examples of PDF generation. The 'capabilities' section lists abstract promises ('provides step-by-step guidance') without delivering any. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill merely describes itself rather than instructing Claude on how to generate PDFs. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of self-referential descriptions with no references to external files, no structured sections with real content, and no navigation to deeper resources. | 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
4dee593
- 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.