pdf

Extract text, create PDFs, and handle forms. Useful for press releases, branded one-pagers, and printable design deliverables.

Quality

55%

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 ./skills/pdf/SKILL.md

Quality

Content

43%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.

This is a thin catalogue/discovery stub rather than a functional skill body: it describes the upstream bundle and links to it instead of providing executable PDF guidance, a sequenced workflow, or actual bundled references. It is concise but largely unactionable.

Suggestions

Inline or bundle concrete, executable guidance (e.g., a pdfplumber text-extraction snippet and a form-filling example) rather than only linking to the upstream repo.

Add a sequenced workflow with validation checkpoints for PDF creation/form handling so the agent can execute without reading external docs.

Provide the referenced references/ or scripts/ files (or remove the implication that a local bundle exists) so progressive disclosure is backed by real artifacts.

Dimension	Reasoning	Score
Conciseness	The body is short and avoids explaining PDF concepts, but it restates the description verbatim in the "What it does" section, which is mild redundancy.	4 / 5
Actionability	The only concrete instruction is `open https://github.com/...`; there is no executable code, library, command, or specific extraction/form workflow, leaving the agent without actionable steps.	2 / 5
Workflow Clarity	It points to an external README to "inspect for exact paths" but provides no sequenced steps and no validation for destructive/batch PDF operations, so the workflow is roughly hinted at with major gaps.	2 / 5
Progressive Disclosure	Sections are present and the body is appropriately short, but the promised bundle (references/scripts/assets) does not exist and all real content is offloaded to an upstream URL rather than clearly signaled one-level-deep references.	3 / 5
	Total	11 / 20 Passed

Description

66%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 concrete and domain-specific with natural trigger phrases, but it relies on an implicit "Useful for" rather than an explicit "Use when" clause and lacks a few synonyms/file extensions. Strong but not fully complete.

Suggestions

Add an explicit "Use when..." clause (e.g., "Use when the user mentions PDFs, forms, press releases, or one-pagers.") to lift completeness.

Include synonyms and the file extension ("PDFs", ".pdf") in the description text for better trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists three concrete actions ("Extract text", "create PDFs", "handle forms") plus domain outcomes, leaving minor coverage gaps such as merge/convert/table extraction.	4 / 5
Completeness	The "what" is clear, but the "when" is only weakly implied via "Useful for..." rather than an explicit "Use when..." clause, which per guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural terms ("create pdf", "pdf form", "branded pdf", "one pager") plus the extension itself, but omits common synonyms like "PDFs" in the description and lacks ".pdf".	4 / 5
Distinctiveness Conflict Risk	The PDF/form niche is mostly distinct with branded one-pager and printable deliverable triggers reducing overlap, though generic "documents" skills could still overlap on basic PDF handling.	4 / 5
	Total	15 / 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: nexu-io/open-design
Path: skills/pdf/SKILL.md
Commit: d4138ea

Reviewed: 3 days 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.