databricks-unstructured-pdf-generation
Generate PDF documents from HTML and upload to Unity Catalog volumes. Use for creating test PDFs, demo documents, reports, or evaluation datasets.
74
67%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./databricks-skills/databricks-unstructured-pdf-generation/SKILL.mdQuality
Discovery
85%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 is a solid description that clearly communicates both what the skill does and when to use it, with a distinctive niche combining PDF generation from HTML with Unity Catalog uploads. The main weakness is that trigger term coverage could be broader—adding terms like 'convert HTML to PDF', 'Databricks', or '.pdf' would improve discoverability.
Suggestions
Add more natural trigger term variations such as 'convert HTML to PDF', '.pdf files', 'Databricks volumes' to improve keyword coverage for user queries.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Generate PDF documents from HTML' and 'upload to Unity Catalog volumes', plus enumerates use cases like 'test PDFs, demo documents, reports, evaluation datasets'. | 3 / 3 |
Completeness | Clearly answers both what ('Generate PDF documents from HTML and upload to Unity Catalog volumes') and when ('Use for creating test PDFs, demo documents, reports, or evaluation datasets') with an explicit 'Use for' trigger clause. | 3 / 3 |
Trigger Term Quality | Includes some natural keywords like 'PDF', 'HTML', 'reports', 'Unity Catalog volumes', but misses common variations users might say such as 'convert HTML to PDF', '.pdf', 'document generation', or 'Databricks volumes'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of HTML-to-PDF generation with Unity Catalog volume upload is a very specific niche that is unlikely to conflict with other skills. The mention of Unity Catalog makes it clearly distinct. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is highly actionable with concrete, executable examples and a clear tool signature, but it is significantly bloated with repetitive patterns and HTML/CSS guidance that Claude doesn't need. The workflow section lacks error-handling validation steps for batch operations, and the entire content would benefit from splitting templates and patterns into separate reference files.
Suggestions
Remove or drastically condense the three 'Common Patterns' — they all demonstrate the same tool call with different HTML. One example plus a brief note about varying content is sufficient.
Remove the 'HTML Best Practices' section (complete HTML5 structure, CSS features supported/avoided) — Claude already knows HTML/CSS. Keep only the PlutoPrint-specific limitation about no external resources.
Add explicit error-handling guidance in the workflow: check the 'success' field in the response, handle failures, and include a retry step for batch operations.
Move the professional document template and any additional patterns to a separate TEMPLATES.md file, referenced from the main skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~200+ lines. The three 'Common Patterns' (technical docs, business reports, HR policies) are essentially the same tool call with slightly different HTML/CSS — they add little instructional value. The parallel execution example repeats 5 nearly identical calls. The HTML best practices section explains basic HTML5 structure and CSS features Claude already knows. | 1 / 3 |
Actionability | The tool signature, return schema, and all examples are concrete and copy-paste ready. Every pattern shows a complete, executable tool call with full HTML content, and the parameters are clearly documented. | 3 / 3 |
Workflow Clarity | The 'Workflow for Multiple Documents' section lists steps but lacks explicit validation checkpoints — there's no guidance on checking the 'success' field in the return value, handling errors from failed uploads, or retry logic. For batch operations uploading to external storage, this missing error-handling feedback loop caps the score at 2. | 2 / 3 |
Progressive Disclosure | The content is a monolithic file with no references to external documents. The professional document template, three common patterns, and HTML best practices could easily be split into separate reference files. The structure uses headers well but everything is inline, making it a long single document. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- databricks-solutions/ai-dev-kit
- Commit
b4071a0
- 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.