pdf

Create, read, merge, fill, and secure PDF files.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

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

An exemplary skill body: lean, fully executable, with a clearly sequenced workflow and explicit validation/feedback checkpoints. Deep form-spec material is appropriately pushed to references/forms.md rather than inlined.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's competence (no basic PDF/library explanations); every section and pitfall earns its place with non-obvious, actionable detail.	5 / 5
Actionability	"How to Run" and the Quick Reference table provide complete copy-paste CLI commands with all flags for every script, and the Procedure gives exact executable steps.	5 / 5
Workflow Clarity	A 9-step Procedure opens with inspect-first checks and closes with verify-last; the form-design loop (spec → lint → overlay → iterate until clean) is an explicit validation feedback loop.	5 / 5
Progressive Disclosure	SKILL.md is a well-sectioned overview that offloads form-spec detail to a real one-level reference (references/forms.md, cited in-body) and routes execution to bundled scripts.	5 / 5
	Total	20 / 20 Passed

Description

67%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 concise, specific, and distinct PDF-skill description that clearly states capabilities but omits any explicit "when to use" trigger guidance, capping completeness. Adding a "Use when…" clause with synonyms (PDFs, .pdf, forms) would raise trigger_term_quality and completeness.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user mentions PDFs, .pdf files, forms, or document extraction/merging."

Add natural synonyms and the file extension ("PDFs", ".pdf", "forms", "tables") to broaden trigger_term_quality.

Consider naming extraction explicitly ("extract text/tables") since "read" is generic and overlaps with OCR skills.

Dimension	Reasoning	Score
Specificity	Lists five concrete actions ("Create, read, merge, fill, and secure") on PDF files, matching the comprehensive multi-action anchor.	5 / 5
Completeness	The "what" is clear, but there is no "Use when…" clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric.	3 / 5
Trigger Term Quality	The only natural noun-phrase trigger is "PDF files"; action verbs (merge, fill, secure) add specificity but the rubric's keyword coverage is missing synonyms/extensions like PDFs, .pdf, forms, and extraction.	3 / 5
Distinctiveness Conflict Risk	The description is firmly PDF-niched with distinct triggers and minimal overlap risk with related document skills.	5 / 5
	Total	16 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: NousResearch/hermes-agent
Path: skills/productivity/pdf/SKILL.md
Commit: 6680afb

Reviewed: about 2 hours 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.