pdf-processor

**WORKFLOW SKILL** - Process PDF files including text extraction, rotation, and merging. USE FOR: "extract PDF text", "rotate PDF", "merge PDFs", "split PDF pages", "convert PDF to text". DO NOT USE FOR: creating PDFs from scratch (use document-creator), editing PDF forms (use form-filler). INVOKES: pdf-tools MCP for extraction, file-system for I/O. FOR SINGLE OPERATIONS: Use pdf-tools MCP directly for simple extractions.

Quality

70%

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 ./cmd/waza/dev/testdata/high/SKILL.md

Quality

Content

47%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 token-efficient and neatly sectioned but lacks actionable, executable guidance: the workflow is generic, only extraction is concretely shown, and the rotation/merge/split operations promised in the description have no commands or code. Validation checkpoints are entirely absent.

Suggestions

Replace the abstract steps ('Use appropriate tools for the operation') with concrete commands or code for each supported operation, especially rotation, merging, and splitting.

Add a validation/verification checkpoint (e.g., confirm the output PDF opens and has the expected page count) before returning results, since merge and split are batch operations.

Either expand the body to cover all five advertised operations or move per-operation detail into reference files under references/ and link to them from the overview.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding or over-explanation of concepts Claude already knows, but the generic step 'Use appropriate tools for the operation' is vague rather than crisp, keeping it just below the fully efficient 5 anchor.	4 / 5
Actionability	Steps are high-level hints ('Parse the user's request', 'Use appropriate tools') with only one concrete command (pdftotext) and a thin MCP table; no executable code or specific commands for the rotation/merge/split operations the skill claims to support.	2 / 5
Workflow Clarity	The three-step sequence (parse, use tools, return results) is poorly defined with many gaps and no validation checkpoints, matching the rough-sequence anchor; the absence of validation is notable given batch-style merge/split operations.	2 / 5
Progressive Disclosure	Sections (Instructions, MCP Tools Used, Prerequisites) are well-organized with no nested references and the body is under 50 lines, but the skill claims complex workflows without breaking detail into reference files or expanding the overview.	4 / 5
	Total	12 / 20 Passed

Description

92%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 description that concisely states capabilities, provides explicit USE FOR/DO NOT USE FOR trigger guidance, and distinguishes itself from related skills. The only gap is the absence of file extensions and synonyms among the trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across extraction, rotation, merging, splitting, and PDF-to-text conversion, matching the comprehensive-coverage anchor; the third-person 'Process PDF files' phrasing avoids person-voice penalty.	5 / 5
Completeness	Explicitly answers both 'what' (Process PDF files including text extraction, rotation, and merging) and 'when' (USE FOR with concrete trigger phrases), matching the top anchor.	5 / 5
Trigger Term Quality	The USE FOR list provides natural user phrases ('extract PDF text', 'rotate PDF', 'merge PDFs'), but it lacks file extensions (.pdf) and synonyms, leaving it just below the comprehensive 5 anchor.	4 / 5
Distinctiveness Conflict Risk	Clear PDF-manipulation niche with a DO NOT USE FOR clause routing PDF creation and form editing to named sibling skills, minimizing conflict risk.	5 / 5
	Total	19 / 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: microsoft/waza
Path: cmd/waza/dev/testdata/high/SKILL.md
Commit: 611250c

Reviewed: 9 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.