pdf

Use when tasks involve reading, creating, or reviewing PDF files where rendering and layout matter; prefer visual checks by rendering pages (Poppler) and use Python tools such as `reportlab`, `pdfplumber`, and `pypdf` for generation and extraction.

1.03x

Quality

76%

Does it follow best practices?

Impact

55%

1.03x

Average score across 6 eval scenarios

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./bundled/skills/pdf/SKILL.md

Quality

Content

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

A concise, well-structured skill body with executable commands and a solid render-verify workflow. The biggest gap is that the bundle scripts and asset are not surfaced from the body, leaving form-field and validation-image capabilities undiscoverable.

Suggestions

Add a short section (e.g. 'Form filling & validation') that links to the relevant scripts/*.py files (fill_fillable_fields.py, check_bounding_boxes.py, create_validation_image.py) so the bundle is discoverable.

Include a minimal copy-paste Python example for reportlab generation or pdfplumber extraction to push actionability toward anchor 5.

Remove or merge the empty 'Environment' section to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	Largely efficient and assumes Claude's competence, with minor trimmable padding such as the near-empty 'Environment' section ('No required environment variables.') and restatements like 'Keep filenames stable and descriptive'.	4 / 5
Actionability	Provides fully executable shell commands (pdftoppm, uv/pip install, brew/apt-get) and named tools, but lacks a copy-paste Python snippet for the core reportlab/pdfplumber generation and extraction tasks, leaving a moderate gap below anchor 5.	4 / 5
Workflow Clarity	A clear four-step sequence with an explicit re-render-and-verify validation checkpoint (step 4) and a 'Final checks' gate, satisfying the batch/visual-validation feedback requirement; the on-failure fix-and-retry sub-loop is implied rather than spelled out, keeping it just below anchor 5.	4 / 5
Progressive Disclosure	Well-organized with clear section headers and no nested references, but the body never points to the substantial bundle that exists (eight scripts/*.py files for form filling, bounding boxes, field extraction, and a validation image, plus assets/pdf.png), a missed navigation opportunity that holds it below anchor 5.	4 / 5
	Total	16 / 20 Passed

Description

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

A strong, third-person description with an explicit 'Use when' trigger and concrete, tool-backed capabilities. The main gap is missing natural synonyms ('PDFs', 'forms', '.pdf') that would round out trigger coverage.

Suggestions

Add common synonyms and the file extension to the trigger, e.g. 'Use when working with PDF files, PDFs, forms, or .pdf documents'.

Surface form filling and table extraction as distinct capabilities since the bundle scripts support them, broadening the 'what' coverage toward anchor 5.

Consider pairing the tool preference with one more concrete action verb (e.g. 'fill forms') to reduce overlap between 'reading' and 'reviewing'.

Dimension	Reasoning	Score
Specificity	Names the PDF domain plus several concrete actions (read, create, review, render pages, generate, extract) backed by named tools (Poppler, reportlab, pdfplumber, pypdf), landing between the 'several specific actions' and 'comprehensive coverage' anchors.	4 / 5
Completeness	Explicitly answers 'when' via the 'Use when tasks involve reading, creating, or reviewing PDF files where rendering and layout matter' clause and gives a concrete 'what' via rendering and named generation/extraction tools, just short of the fully concrete trigger-phrase breadth of anchor 5.	4 / 5
Trigger Term Quality	Includes the natural phrase 'PDF files' alongside task verbs users would say, but omits common synonyms like 'PDFs', 'forms', 'document extraction', and the '.pdf' extension that the anchor-5 example shows.	4 / 5
Distinctiveness Conflict Risk	A clear PDF niche sharpened by the rendering/layout angle and named Poppler/Python tooling, giving distinct triggers with minimal overlap against other skills.	5 / 5
	Total	17 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: foryourhealth111-pixel/Vibe-Skills
Path: bundled/skills/pdf/SKILL.md
Commit: d5ae560

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.