CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

html-to-pdf

Convert HTML files or URLs to high-fidelity PDFs using Puppeteer; auto-detects or forces RTL for Hebrew/Arabic when RTL content is present.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Failed to scan

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Other/html-to-pdf/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The technical core is excellent — executable commands for every input mode, a complete worked example, a thorough CLI reference, and a verification loop with concrete escalation steps. The score is dragged down by a large tail of generic, skill-agnostic boilerplate that wastes context and even contradicts the document's own validation guidance.

Suggestions

Delete or drastically condense the generic sections from 'When Not to Use' through 'Completion Checklist' (~85 lines of template boilerplate); keep only skill-specific guidance such as the existing verification workflow and failure handling for Puppeteer/browser errors.

Resolve the contradiction between the 'Validation Shortcut' section (run scripts/validate_skill.py --help) and the 'Quick Validation' section ('No local script validation step is required for this skill') — remove whichever does not reflect the real workflow.

Consider moving the full 40-line single-page HTML example into a references/ file (e.g., references/single-page-example.html) and keeping just the command and key CSS rules inline.

DimensionReasoningScore

Conciseness

The core sections (When to Use, Example Usage, Implementation Details) are lean and earn their tokens, but roughly the last third of the body — 'When Not to Use', 'Required Inputs', 'Recommended Workflow', 'Output Contract', 'Validation and Safety Rules', 'Failure Handling', 'Quick Validation', 'Deterministic Output Rules', 'Completion Checklist' — is generic template boilerplate with lines like "Keep the output safe, reproducible, and within the documented scope at all times" that add no skill-specific value. This is several padded sections, matching the 'noticeably verbose' anchor rather than 'mostly efficient with some unnecessary explanation'.

2 / 5

Actionability

Fully executable, copy-paste-ready guidance throughout: exact commands ('node assets/html-to-pdf.js input.html output.pdf', 'npm install'), a complete runnable HTML example for the single-page A4 pattern, a full CLI parameter table with defaults, and concrete recovery values ('--scale' e.g. '0.9', '0.8', '--margin=10mm'). Common cases (local file, URL, stdin, RTL, custom executable) are all covered by example.

5 / 5

Workflow Clarity

The recommended verification workflow provides an explicit feedback loop: check 'No extra blank pages' / 'No clipped text', then iterate up to 5 attempts with specific fixes, escalating to HTML/CSS correction. However, the overall validation story has gaps: the top 'Validation Shortcut' (scripts/validate_skill.py --help) serves no clear purpose in the conversion flow, and the later 'Quick Validation' section states 'No local script validation step is required for this skill', directly contradicting it — so it sits below the fully coherent anchor 5.

4 / 5

Progressive Disclosure

The bundle structure is used appropriately: the implementation script lives in assets/html-to-pdf.js and the validation helper in scripts/validate_skill.py, both referenced by exact, verified-existing paths, with no nested references. Sections are well-organized with clear headers, but ~85 lines of boilerplate (the generic governance sections, plus the 40-line HTML example that could live in a references file) keep it at 'minor organization gaps' rather than an ideal overview split.

4 / 5

Total

15

/

20

Passed

Description

61%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, in third person, and communicates the core capability well, but it lacks an explicit 'Use when...' trigger clause and omits several natural synonyms and file extensions that would improve both completeness and discoverability.

Suggestions

Append an explicit trigger clause, e.g., 'Use when the user wants to convert HTML, a web page, or a URL to a PDF, or needs RTL-correct Hebrew/Arabic PDFs.'

Add natural variations and file extensions such as '.html', '.pdf', 'web page', 'save page as PDF', or 'print to PDF' to broaden trigger-term coverage.

Mention 1-2 more concrete capabilities (e.g., page formats, header/footer templates) to raise the specificity/comprehensiveness of the action list.

DimensionReasoningScore

Specificity

The description names the domain and concrete actions — "Convert HTML files or URLs to high-fidelity PDFs using Puppeteer" plus "auto-detects or forces RTL for Hebrew/Arabic" — but coverage is not comprehensive (no mention of page formats, header/footer templates, or single-page fitting). It names the domain with 2-3 concrete actions, matching the anchor for a clear-but-incomplete action list rather than the 'minor gaps' level above.

3 / 5

Completeness

The 'what' is clear and concrete (HTML/URL to high-fidelity PDF conversion with RTL support), but there is no 'Use when...' clause or equivalent explicit trigger guidance — "when RTL content is present" is a behavioral conditional, not a usage trigger. Per the judging guideline, a missing 'Use when' clause caps completeness at 3, which this anchor describes exactly.

3 / 5

Trigger Term Quality

Strong natural keywords users would say: "HTML files", "PDFs", "URLs", "convert", "Hebrew/Arabic", plus the specific technology "Puppeteer". A few common variations are missing ('web page to PDF', 'save/print as PDF', file extensions like .html/.pdf), so it sits between 'some relevant keywords' (3) and 'comprehensive coverage including synonyms and extensions' (5).

4 / 5

Distinctiveness Conflict Risk

The Puppeteer-based HTML-to-PDF pipeline with RTL/Hebrew/Arabic support is a fairly distinct niche with specific triggers, but 'convert to PDF' broadly overlaps with general PDF-creation/manipulation skills, so it does not reach the 'clear niche with minimal conflict risk' anchor.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Other/html-to-pdf/SKILL.md

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.