pdf

Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.

1.17x

Quality

—

Does it follow best practices?

Impact

100%

1.17x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

65%

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

The content is highly actionable with solid executable examples, but is hurt by redundancy, an unexplained Chinese section, an empty Quick Start, and dangling references to missing bundle files (reference.md, forms.md).

Suggestions

Create the referenced reference.md and forms.md (or remove the pointers) so the progressive-disclosure navigation resolves to real files.

Trim redundant tool variants for merge/split/rotate, keeping one primary approach and a brief mention of alternatives rather than full duplicate examples.

Fill in or remove the empty Quick Start section, and replace the standalone Chinese block with a concise English validation/confirmation checkpoint for destructive batch operations.

Dimension	Reasoning	Score
Conciseness	The body is code-driven and mostly assumes competence, but includes several near-redundant approaches (merge/split/rotate shown in pypdf, qpdf, and pdftk) plus a stray Chinese-language section that adds noise without earning its tokens.	2 / 3
Actionability	Provides fully executable, copy-paste-ready code and concrete CLI commands throughout with specific examples for each task.	3 / 3
Workflow Clarity	No sequenced multi-step workflow with validation checkpoints; the destructive merge/split operations only get a confirmation note with no validate-fix-retry feedback loop, and the Quick Start section is empty.	2 / 3
Progressive Disclosure	References are well-signaled one level deep (reference.md, forms.md) but point to files that do not exist in the bundle — there are no references/scripts/assets directories — so the navigation is broken rather than usable.	2 / 3
	Total	9 / 12 Passed

Description

85%

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 and complete, clearly stating both capabilities and an explicit use-trigger, with low conflict risk. It would improve by adding common user-facing keyword variants (PDFs, .pdf) to strengthen trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms" — matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers both what (the enumerated actions) and when ("When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale").	3 / 3
Trigger Term Quality	Contains relevant natural terms ("PDF form", "PDF documents", "forms") but omits common variations users say such as "PDFs", ".pdf", and "document extraction".	2 / 3
Distinctiveness Conflict Risk	Clear PDF-specific niche with distinct triggers unlikely to overlap with other skills.	3 / 3
	Total	11 / 12 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: majiayu000/claude-skill-registry
Commit: 8271354

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