CtrlK
BlogDocsLog inGet started
Tessl Logo

robust-pdf-extraction

Multi-method PDF extraction with sequential fallback and OCR for scanned documents

55

Quality

61%

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

Quality

Content

65%

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 complete executable code and a clear numbered workflow, but it is somewhat redundant, lacks a batch-level feedback loop, and keeps everything inline rather than splitting detailed methods into reference files.

Suggestions

Move per-method extraction implementations into a reference file (e.g. scripts/ or references/methods.md) and keep SKILL.md as a lean overview with one-level-deep pointers.

Add an explicit batch-processing feedback loop (validate extracted text per file, log failures, retry/OCR) since batch use is advertised.

Reduce redundancy by showing each method once and composing them, rather than defining standalone functions and re-listing them in robust_pdf_extract.

DimensionReasoningScore

Conciseness

The body is mostly efficient executable code with little concept explanation, but it defines each extraction method as a standalone function and then re-composes them in robust_pdf_extract, creating redundancy that could be tightened; this fits the level-2 anchor rather than the lean level-3 example.

2 / 3

Actionability

Every method is provided as complete, copy-paste-ready executable Python or shell code with imports and a fully assembled robust_pdf_extract function, matching the level-3 anchor for executable, specific examples.

3 / 3

Workflow Clarity

Steps are clearly numbered 1-6 with a per-method is_meaningful_text validation checkpoint and try/except recovery, but the skill lists batch processing as a use case without a batch-level validate/fix/retry feedback loop, so per the scoring notes workflow clarity is capped at 2.

2 / 3

Progressive Disclosure

Sections are well organized, but with no references/, scripts/, or assets/ bundle files present, all ~180 lines of multi-method code live inline in SKILL.md where per-method code could be split into one-level-deep reference files, matching the level-2 anchor of content that should be separate being inline.

2 / 3

Total

9

/

12

Passed

Description

57%

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 and occupies a clear niche, but it omits explicit 'when to use' trigger guidance and lacks full coverage of natural user phrasings, capping completeness and trigger-term quality at 2.

Suggestions

Add an explicit trigger clause, e.g. 'Use when extracting text from PDFs of unknown type, scanned documents, or when initial extraction returns empty results.'

Broaden natural keyword coverage to include terms like 'PDFs', 'extract text', 'document', and '.pdf'.

List a couple more concrete capabilities (e.g. text vs. scanned/image PDFs) to push specificity toward level 3.

DimensionReasoningScore

Specificity

The phrase 'Multi-method PDF extraction with sequential fallback and OCR for scanned documents' names the domain and two concrete actions (extraction, OCR) but does not enumerate multiple specific capabilities (e.g. text vs. tables, form handling), so it stops short of the level-3 anchor.

2 / 3

Completeness

It clearly states what the skill does but provides no 'Use when...' clause or equivalent trigger guidance, so per the judging guidelines completeness is capped at 2.

2 / 3

Trigger Term Quality

It includes relevant natural terms like 'PDF extraction', 'scanned documents', and 'OCR', but omits common variations a user would say such as 'PDFs', 'document', 'extract text', or '.pdf', matching the level-2 anchor of partial coverage.

2 / 3

Distinctiveness Conflict Risk

'Multi-method PDF extraction with sequential fallback and OCR for scanned documents' carves a clear, specific niche that is unlikely to trigger for unrelated skills, satisfying the level-3 anchor.

3 / 3

Total

9

/

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