CtrlK
BlogDocsLog inGet started
Tessl Logo

pdf

Read, create, edit, merge, split, rotate, fill, render, and verify workspace PDF files. Use whenever the requested input or deliverable is a .pdf, including extracting text or tables, inspecting metadata and page geometry, generating a new PDF, rearranging pages, filling AcroForm fields, or checking visual layout. Do not use for Google Drive or browser-only PDF workflows.

77

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

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.

The body is a model skill document: lean, fully executable via the bundled CLI, with an explicit route-selection step, validation feedback loops (audit, render, per-page inspection, self-test), and clean progressive disclosure to three real reference files. No dimension shows a meaningful defect.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows (no PDF format primer, no library tutorials); every line is a constraint, a routed decision, or a command. Lean and efficient throughout, matching the every-token-earns-its-place anchor.

5 / 5

Actionability

Every operation — inspect, scaffold, build, merge, split, rotate, forms-inspect, forms-fill, audit, render, self-test, check/fix — has a complete copy-paste-ready bash invocation with flags and output paths, plus a concrete builder contract (accepts --out, offline, explicit fonts, deterministic numbering).

5 / 5

Workflow Clarity

Four explicit routes, a clear prepare-runtime → inspect → act → audit → render → full-size page inspection → iterate sequence with an explicit feedback loop ("rerun audit and render until hard failures are gone") and a self-test. Batch/destructive operations all have validation, so the workflow-clarity cap does not apply.

5 / 5

Progressive Disclosure

A ~140-line overview with three condition-gated, clearly signaled one-level-deep references ("Read [creation.md] before creating or visually redesigning a PDF"), all of which exist in references/; scripts and the starter asset are properly kept out of the overview.

5 / 5

Total

20

/

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.

An exemplary description: a dense list of concrete capabilities, an explicit and detailed when-clause, and a negative boundary. The only weakness is a couple of missing natural synonyms (plain "PDFs", plain "forms") in an otherwise strong trigger set.

Suggestions

Add the everyday word "forms" (e.g., "filling PDF forms") alongside the technical "AcroForm fields" so users who say "form" trigger the skill naturally.

Include the plural "PDFs" as a trigger synonym alongside "PDF files" and ".pdf".

DimensionReasoningScore

Specificity

"Read, create, edit, merge, split, rotate, fill, render, and verify" plus "extracting text or tables, inspecting metadata and page geometry... filling AcroForm fields" lists many concrete actions with no meaningful coverage gaps, matching the comprehensive anchor rather than the minor-gaps anchor at 4.

5 / 5

Completeness

The opening sentence answers "what" concretely, "Use whenever the requested input or deliverable is a .pdf, including..." is an explicit when-clause with concrete trigger phrases, and the trailing "Do not use for..." adds a negative boundary — clearly both what and when.

5 / 5

Trigger Term Quality

"PDF files", ".pdf", "extracting text or tables", "merge", "split", "rotate" give strong keyword coverage, but plain natural synonyms like "PDFs" and the everyday word "forms" (only the jargon variant "AcroForm fields" appears) are missing, placing it just below the comprehensive-synonym anchor at 5.

4 / 5

Distinctiveness Conflict Risk

The skill owns a clear .pdf niche with distinct trigger terms, and the explicit exclusion "Do not use for Google Drive or browser-only PDF workflows" removes the main overlap risk, so conflict with other skills is minimal.

5 / 5

Total

19

/

20

Passed

Validation

100%

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
OpenBMB/PilotDeck
Reviewed

Table of Contents

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.