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.

80

Quality

100%

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%

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 well-structured, executable workflow with lean prose, concrete commands, explicit validation/feedback loops, and correctly signaled one-level-deep references that all exist. It assumes Claude's competence and avoids redundant explanation.

DimensionReasoningScore

Conciseness

The body is lean and directive — e.g. 'Use pdfplumber for text, table, image, and coordinate-aware inspection; use pypdf for page structure, metadata, page operations, and AcroForms; use ReportLab for new PDFs' — with no concept-explanation padding, matching the lean-and-efficient anchor; not level 2 which still carries unnecessary explanation.

3 / 3

Actionability

Provides fully executable bash commands with concrete flags and paths throughout (inspect --input/--out, scaffold/build, merge/split/rotate, forms-inspect/forms-fill, audit, render --dpi 144), matching the copy-paste-ready anchor; not level 2 which uses pseudocode or omits key details.

3 / 3

Workflow Clarity

Routes requests into four numbered paths, sequences risky steps ('inspect and render first, make the smallest page-level change, then audit and render again'), and includes an explicit audit/render feedback loop ('rerun audit and render until hard failures are gone'), matching the explicit-validation-checkpoint anchor; not level 2 where checkpoints are missing.

3 / 3

Progressive Disclosure

Body is a concise overview with well-signaled one-level-deep references (creation.md, structure-and-forms.md, qa-checklist.md — all verified to exist), each tied to a specific task type, matching the clear-overview anchor; not level 2 where references are poorly signaled or content is inline.

3 / 3

Total

12

/

12

Passed

Description

100%

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, trigger-rich, and complete, with explicit 'what' and 'when' guidance plus a clear out-of-scope boundary. It is a strong, concise description that avoids fluff.

DimensionReasoningScore

Specificity

Lists many concrete actions ('Read, create, edit, merge, split, rotate, fill, render, and verify' plus 'extracting text or tables, inspecting metadata and page geometry, generating a new PDF, rearranging pages, filling AcroForm fields'), matching the multiple-specific-actions anchor rather than the domain-plus-some-actions level below.

3 / 3

Completeness

Explicitly answers what ('Read, create, edit, merge, split, rotate, fill, render, and verify workspace PDF files') and when ('Use whenever the requested input or deliverable is a .pdf'), with an explicit 'Use whenever' trigger; not level 2 where 'when' is only implied.

3 / 3

Trigger Term Quality

Covers natural terms users say — 'PDF files', '.pdf', 'AcroForm fields', 'extracting text or tables', 'metadata', 'visual layout' — matching the good-coverage anchor; not the level below which only has a few relevant keywords.

3 / 3

Distinctiveness Conflict Risk

Clear niche (workspace .pdf files) plus an explicit exclusion ('Do not use for Google Drive or browser-only PDF workflows') reduces overlap, matching the distinct-trigger anchor rather than the could-still-overlap level.

3 / 3

Total

12

/

12

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.

Validation16 / 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.