pdff

Convert documents to PDF format

Quality

48%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./tests/fixtures/typosquat/SKILL.md

Quality

Content

51%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 body is well structured and appropriately brief, but it contains no executable guidance: no conversion commands, libraries, or per-format methods, leaving the agent to invent the entire implementation. The workflow is sequenced yet generic, with no validation of outputs.

Suggestions

Replace "Use the appropriate conversion method" with concrete per-format commands, e.g. `pandoc input.md -o output.pdf`, `libreoffice --headless --convert-to pdf input.docx`, or a Python snippet for .txt/.html.

Specify the output filename convention and add a validation step, e.g. verify the produced PDF is non-empty/openable before reporting success.

Tie each Supported Formats entry to its conversion method so the format list doubles as a dispatch table.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept explanations or padding — it does not explain what a PDF is or how libraries work. It falls short of 5 only because of minor redundancy: the intro line "This skill converts various document formats to PDF" repeats the title, and step 1 ("Accept the input file path from the user") adds little.	4 / 5
Actionability	There is no concrete command, library, or code anywhere — step 3 says "Use the appropriate conversion method for the detected format," which defines nothing (no pandoc, wkhtmltopdf, LibreOffice, or pdfkit). This matches 'Minimal concrete guidance; high-level hints but missing the specific steps to execute'; it is above 1 because a high-level step sequence does exist.	2 / 5
Workflow Clarity	A rough four-step sequence exists (accept path, detect format, convert, save) but the steps are poorly defined — detection method unspecified, conversion method unspecified, output naming unspecified — and there are no validation checkpoints (e.g., verifying the PDF opened correctly). This fits anchor 2 ('Rough sequence present but many gaps; steps poorly defined; validation absent') better than 3, whose steps are concrete with only checkpoints missing.	2 / 5
Progressive Disclosure	The skill is under 50 lines, single-purpose, and needs no external references; sections ('Instructions', 'Supported Formats') are well organized and the body is a clear overview. Per the rubric's simple-skill exception, this can score 5 with just well-organized sections.	5 / 5
	Total	13 / 20 Passed

Description

45%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 concise and states a clear purpose, but it is a bare minimum: one generic action, no trigger guidance, and no natural user phrasing or file extensions. Adding an explicit 'Use when...' clause and naming supported formats would move it from mediocre to good.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to convert or export documents (docx, txt, html, md) to PDF.'

Include natural user phrasing and file extensions — 'convert to PDF', 'export as PDF', '.docx', '.pdf' — to improve trigger matching.

Briefly enumerate the concrete capabilities, e.g. 'Converts .txt, .md, .html, and .docx files to PDF' to sharpen both specificity and distinctiveness.

Dimension	Reasoning	Score
Specificity	"Convert documents to PDF format" names the domain (documents, PDF) and a single generic action, matching the anchor 'Names the domain but actions are minimal or generic' ("Processes PDF files"). It is not a 3 because it lists no format-specific actions or additional capabilities like the "Processes PDF files and extracts content" example.	2 / 5
Completeness	The description clearly answers 'what' (convert documents to PDF) but has no 'when' — no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3. It is above 2 because the 'what' is clear rather than vague.	3 / 5
Trigger Term Quality	Relevant keywords are present ("documents", "PDF", "convert") but common variations users would naturally say are missing — no "convert to PDF", "export", file extensions like .docx or .pdf, or synonyms. This fits 'Some relevant keywords but missing common variations or synonyms' rather than 4's 'Good keyword coverage'.	3 / 5
Distinctiveness Conflict Risk	The to-PDF direction is somewhat specific, but the phrasing could overlap with document-processing or PDF-manipulation skills and there are no distinct trigger phrases to disambiguate. This fits 'Somewhat specific but could still overlap with similar skills' better than 4, which expects mostly distinct differentiation.	3 / 5
	Total	11 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: NMitchem/SkillScan
Path: tests/fixtures/typosquat/SKILL.md
Commit: 08afcd4

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.