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 critically underdeveloped. It provides no concrete actions, no meaningful trigger terms beyond the skill name repeated, no 'Use when...' guidance, and no distinguishing details. It would be nearly impossible for Claude to reliably select this skill from a pool of alternatives.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates PDF documents from templates, creates invoices, exports reports to PDF format, converts HTML to PDF.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a PDF, generate a PDF report, export to PDF, make an invoice PDF, or convert content to .pdf format.'
Clarify the specific niche to reduce conflict risk, e.g., specify what types of PDFs (invoices, reports, contracts) and what inputs are expected (templates, data, HTML).
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only says 'Pdf Generator' and 'Business Automation' without describing any concrete actions. There are no specific capabilities listed such as creating, formatting, or populating PDFs. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' (no specific actions beyond the name) and 'when should Claude use it' (no explicit 'Use when...' clause or meaningful trigger guidance). | 1 / 3 |
Trigger Term Quality | The only trigger term is 'pdf generator' repeated twice. 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 extremely generic — 'Business Automation' could overlap with many skills, and 'pdf generator' alone doesn't clarify what kind of PDF generation (invoices, reports, forms, etc.) to distinguish it from other PDF-related 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 shell with no substantive content. It consists entirely of auto-generated boilerplate that describes what a PDF generator skill would do without providing any actual instructions, code examples, library recommendations, or workflows for generating PDFs. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples for PDF generation using a specific library (e.g., ReportLab, WeasyPrint, or fpdf2) with copy-paste ready snippets.
Define a clear workflow with steps: create content/template → generate PDF → validate output, including validation checkpoints.
Remove all meta-description sections (Purpose, When to Use, Example Triggers) and replace with actionable content like quick-start code, common patterns (tables, images, headers), and output format specifications.
If advanced topics exist (templates, styling, batch generation), reference them via clearly signaled links to separate files rather than leaving the skill content-free.
| 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 token is wasted on describing the skill rather than teaching anything. | 1 / 3 |
Actionability | There is zero actionable content—no code, no commands, no specific steps, no examples of PDF generation. Phrases like 'Provides step-by-step guidance' and 'Generates production-ready code' are claims about the skill, not actual guidance or code. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill merely states it can provide step-by-step guidance without actually providing any. | 1 / 3 |
Progressive Disclosure | There is no meaningful content to organize, no references to detailed files, and no navigation structure. The sections that exist (Purpose, When to Use, Capabilities, etc.) are boilerplate metadata rather than instructional content. | 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
dc559db
- 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.