CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pdf

Manipulate PDF files — extract text, count pages, render thumbnails, merge or split documents. Use for PDF-specific operations that don't fit `markdown-converter` (general read) or `pandic-office` (write from markdown).

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./backend/commonly-bundled-skills/pdf/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A concise, largely executable operations cookbook with clear sectioning and useful cross-references to sibling skills. Its main weaknesses are the broken shell-expansion inside the quoted Python heredocs and the absence of validation steps for the batch operations (split, merge, render-all).

Suggestions

Fix the quoted-heredoc expansion bug: inside <<'PY' the $(basename "$PWD") construct is literal, so pypdf writes to a nonexistent directory. Use plain filenames ('input.pdf', 'merged.pdf') or pass the path via sys.argv/environment variable instead.

Add validation after batch operations, e.g. verify a split produced the expected file count (ls page_*.pdf | wc -l vs pdfinfo's Pages) or confirm pdfinfo succeeds on the merged output before reporting success.

Replace the ten repetitions of /workspace/$(basename "$PWD")/ with a one-line note about the workspace path convention, which would trim token cost and remove the confusing construct from the bash examples too.

DimensionReasoningScore

Conciseness

The body is a lean recipe book with no explanations of concepts Claude already knows and a genuinely useful tool inventory, but the opaque `/workspace/$(basename "$PWD")/` prefix is repeated in every command where a single path note would do — minor trimmable noise.

4 / 5

Actionability

Bash commands (pdftotext, pdfinfo, pdftoppm) are concrete and executable, but the Python heredocs use a quoted delimiter (<<'PY') so `$(basename "$PWD")` inside them is never expanded by the shell, producing literal broken output paths; the merge example also mixes relative input paths with that absolute construct. Mostly executable with one systematic defect.

4 / 5

Workflow Clarity

Each single-task recipe is unambiguous, but split, merge, and render-all are batch operations and the skill includes no validation or verification steps (e.g., checking the split output's page count), which caps workflow clarity at 3 per the rubric.

3 / 5

Progressive Disclosure

The ~80-line body is cleanly sectioned per operation with clear cross-skill pointers and nothing inlined that belongs in a separate file; it exceeds the 50-line simple-skill threshold and offers no quick-start/advanced split or reference structure, so it sits at good-but-not-ideal organization.

4 / 5

Total

15

/

20

Passed

Description

78%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 names concrete capabilities, provides explicit trigger guidance, and actively distinguishes itself from neighboring skills. The only gaps are a missing capability (metadata editing) and the absence of file-extension/synonym trigger terms.

DimensionReasoningScore

Specificity

The description lists five concrete actions ("extract text, count pages, render thumbnails, merge or split documents") but omits metadata editing, which the skill body covers — a minor coverage gap that fits the 'several specific actions; minor gaps' anchor rather than comprehensive coverage.

4 / 5

Completeness

Both a clear 'what' (five named operations) and an explicit "Use for PDF-specific operations that don't fit..." trigger clause are present; the 'when' is framed as boundary disambiguation against other skills rather than concrete user trigger phrases, keeping it below the top anchor.

4 / 5

Trigger Term Quality

Good natural keyword coverage ("PDF files", "extract text", "merge or split", "thumbnails"), but it lacks the '.pdf' file extension and plural 'PDFs' synonyms that the top anchor requires.

4 / 5

Distinctiveness Conflict Risk

It claims a clear PDF-specific niche and explicitly disambiguates against the two adjacent skills ("doesn't fit `markdown-converter` (general read) or `pandic-office` (write from markdown)"), giving minimal conflict risk.

5 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

Team-Commonly/commonly

Path

backend/commonly-bundled-skills/pdf/SKILL.md

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.