CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pdf-processor

Perform basic local PDF operations (merge, split, extract pages/text/tables, create) when users request offline PDF processing without external services.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Other/pdf-processor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 core operational content is excellent — complete executable command examples for all six operations with well-documented flags and failure behavior. However, the skill is heavily padded with generic process boilerplate that adds no PDF-specific value, its validation guidance is abstract and partly incoherent, and it references bundle files that are missing from the skill directory.

Suggestions

Delete the generic boilerplate sections (Recommended Workflow, Output Contract, Validation and Safety Rules, Failure Handling, Required Inputs, Input Validation) or replace them with PDF-specific content; they consume roughly half the body without teaching anything the command examples don't already show.

Add a concrete, executable validation step after batch operations like split (e.g., a one-line check that the output directory contains one PDF per input page), and fix the Quick Validation section — `pdf_tool.py --help` prints argparse help, not a result-file summary.

Ship the referenced bundle files (scripts/pdf_tool.py, scripts/requirements.txt, references/examples.md) or remove the dangling references so navigation matches the actual bundle structure.

DimensionReasoningScore

Conciseness

Roughly half the body is generic template boilerplate — "Recommended Workflow" ("Select the documented execution path and prefer the simplest supported command"), "Output Contract", "Validation and Safety Rules", "Failure Handling", and "Required Inputs" contain no PDF-specific information, matching anchor 2's "several unnecessary explanations or padded sections". The genuinely useful sections (When to Use, Example Usage, Implementation Details) are efficient.

2 / 5

Actionability

Six complete, copy-paste-ready bash commands with all flags (e.g., `--operation extract-pages --pages "1-3,5"`) cover every documented operation, plus the pip install and `--help` commands — fully executable guidance covering the common cases.

5 / 5

Workflow Clarity

Per-operation commands are unambiguous, but batch operations like `split` ("Writes one PDF per page") lack concrete validation: "Success criteria" are stated abstractly with no executable check, and the "Quick Validation" section claims `--help` outputs "Result file: pdf_processor_result.md", which is incoherent with the tool. Per the batch-operation guideline, workflow clarity is capped at 3.

3 / 5

Progressive Disclosure

Section structure is clear, but the body references bundle files that do not exist — `scripts/pdf_tool.py`, `scripts/requirements.txt`, and a hedged "More examples may be available in references/examples.md" — while the bundle contains no scripts/, references/, or assets/ directories. Structure exists, but navigation to referenced materials is broken and the inline boilerplate dilutes the overview.

3 / 5

Total

13

/

20

Passed

Description

80%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: it names the domain, enumerates all supported operations concretely, and includes an explicit scope constraint (local/offline, no external services). Its main weaknesses are missing natural trigger synonyms and file extensions, and a when-clause phrased as a request condition rather than natural user language.

DimensionReasoningScore

Specificity

The parenthetical "(merge, split, extract pages/text/tables, create)" enumerates every operation the skill documents, so coverage is comprehensive with no gaps — anchor 4's "minor gaps in coverage" does not apply.

5 / 5

Completeness

The "what" is concrete ("Perform basic local PDF operations (merge, split, extract pages/text/tables, create)") and a when-clause exists ("when users request offline PDF processing without external services"), but the trigger is a condition on the request rather than concrete user phrasing like "when the user mentions PDFs", so it does not reach anchor 5.

4 / 5

Trigger Term Quality

Natural terms like "PDF", "merge", "split", and "extract" are present and would be said by users, but the description lacks common synonyms and file extensions ("PDF files", "PDFs", ".pdf") required for anchor 5.

4 / 5

Distinctiveness Conflict Risk

The "local" and "without external services" qualifiers carve out a distinct offline niche, but any other general-purpose PDF skill in the environment would still be triggered by the same PDF-related requests, leaving minor overlap risk with closely related skills.

4 / 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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 10 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Other/pdf-processor/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.