CtrlK
BlogDocsLog inGet started
Tessl Logo

pdf-verification-check-112b09

Verify generated PDF files using PyPDF2 to check page counts and integrity

54

Quality

60%

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 ./benchmarks/gdpval/skills/pdf-verification-check-112b09/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

66%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 provides executable, validation-focused guidance with a clear feedback loop, but it is held back by noticeable duplication of the same verification code across three sections. Structure is good for a single-purpose skill with no bundle files.

Suggestions

Consolidate the three near-identical verification code blocks into one canonical example; reference it from the other sections instead of repeating it.

Replace the placeholder generate_pdf/regenerate_pdf calls in the Example Workflow with real or clearly-marked illustrative steps.

Trim redundant prose such as restating the install step and the 'Critical' completion warning where the feedback loop already conveys it.

DimensionReasoningScore

Conciseness

The verification logic is presented three times in near-identical form (a full verify_pdf function with a usage loop, an inline python -c block, and an Example Workflow that calls verify_pdf again), which is noticeably padded duplication.

2 / 5

Actionability

The verification code is concrete and copy-paste executable, but the Example Workflow relies on placeholder calls (generate_pdf, regenerate_pdf) that are not executable, leaving a minor gap.

4 / 5

Workflow Clarity

Steps are clearly sequenced (install, verify, run via run_shell, verify-before-completion) with an explicit numbered feedback loop (examine error, regenerate, re-run, repeat until pass), matching the anchor for clear sequence with explicit validation and error-recovery loops.

5 / 5

Progressive Disclosure

A single, well-organized file with clear section headers (When to Use, Verification Steps, Common Issues, Example Workflow); no external references are needed for this scope, but the inline duplication leaves minor organization gaps.

4 / 5

Total

15

/

20

Passed

Description

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

The description clearly states what the skill does but omits any explicit trigger guidance for when to use it, capping completeness. Trigger terms are present but lack natural synonyms and rely partly on a library name.

Suggestions

Add an explicit 'Use when...' clause listing concrete triggers (e.g., after generating PDFs, when a task requires a specific page count).

Replace or supplement the library name 'PyPDF2' with natural user phrases like 'verify PDFs', 'check PDF page count', and include the '.pdf' extension.

Broaden the action list slightly (e.g., 'detect empty or corrupted PDFs') to lift specificity toward 4-5.

DimensionReasoningScore

Specificity

Names the domain (PDF files), the tool (PyPDF2), and two concrete actions ('check page counts and integrity'), matching the anchor for 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

The 'what' is clear ('Verify generated PDF files... to check page counts and integrity') but there is no 'Use when...' clause, so per the guidelines completeness is capped at 3.

3 / 5

Trigger Term Quality

Relevant terms like 'PDF files' and 'page counts' appear, but 'PyPDF2' is technical jargon rather than a user phrase, and common variations ('PDFs', '.pdf', 'verify PDF') are missing.

3 / 5

Distinctiveness Conflict Risk

The narrow verification niche (page counts + integrity via PyPDF2) is mostly distinct, with only minor overlap risk against general PDF-creation skills.

4 / 5

Total

13

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
HKUDS/OpenSpace
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.