CtrlK
BlogDocsLog inGet started
Tessl Logo

pdf-verification-check

Verify generated PDFs for integrity and page count using PyPDF2 before task completion.

56

Quality

71%

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/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 content is highly actionable with a complete executable verification script and a clear, well-structured workflow, but conciseness slips due to a redundant integration example and restated rationale, and the remediation loop lacks an explicit re-verification checkpoint.

Suggestions

Remove or merge the "Integration Example" section, since its "# ... insert logic here ..." heredoc duplicates the full script without adding executable value.

Make the remediation feedback loop explicit by adding a step to re-run verification after regenerating, closing the workflow_clarity gap.

Tighten the "Rules" section to avoid restating the rationale already conveyed by the verification steps.

DimensionReasoningScore

Conciseness

The body is mostly efficient, but the "Integration Example" heredoc with "# ... insert logic here ..." adds little over the full script, and the "Rules" section restates rationale already implied by the verification steps.

3 / 5

Actionability

The provided Python script using PdfReader is complete and copy-paste ready, with a concrete files_to_check example and a pip install command, covering the common verification cases.

5 / 5

Workflow Clarity

The four verification steps form a clear sequence with a remediation feedback loop (step 4), but it does not explicitly call for re-running verification after regeneration, leaving a minor validation gap.

4 / 5

Progressive Disclosure

The skill is well organized into clear sections (When to Use, Verification Steps, Script, Rules, Dependencies) with no external references needed; the only gap is mild redundancy between the Script and Integration Example sections.

4 / 5

Total

16

/

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 and targets a distinct niche, but lacks an explicit "Use when..." trigger clause and natural keyword synonyms, which together cap completeness and trigger-term quality at 3.

Suggestions

Add an explicit "Use when..." trigger clause, e.g. "Use when a task generates PDF files that must meet specific page counts or integrity requirements."

Include natural synonyms users would say, such as "PDF files", "documents", or the ".pdf" extension, alongside the existing "PDFs" and "page count".

Consider whether mentioning the implementation library (PyPDF2) in the description adds user-relevant trigger value or is better deferred to the body.

DimensionReasoningScore

Specificity

"Verify generated PDFs for integrity and page count using PyPDF2" names the domain plus two concrete actions (integrity check, page-count check), but coverage is not comprehensive beyond those two checks.

3 / 5

Completeness

The "what" is clear (verify integrity and page count), but there is no "Use when..." trigger clause; "before task completion" only weakly implies when, so per the rubric guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

"PDFs" and "page count" are relevant natural terms, but common variations/synonyms like "PDF files", "documents", or ".pdf" are missing, and "PyPDF2" is library jargon rather than a phrase users say.

3 / 5

Distinctiveness Conflict Risk

The niche—post-generation PDF verification for integrity and page count—is fairly distinct from generation/extraction skills, with only minor overlap risk against other general PDF 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.

Validation — 16 / 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.