CtrlK
BlogDocsLog inGet started
Tessl Logo

pdf-extraction-fallback

Multi-stage fallback strategy for PDF/document extraction using sequential tool alternatives

53

Quality

58%

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 ./benchmarks/gdpval/skills/pdf-extraction-fallback/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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 and well-structured, with executable code for each fallback stage and a clear validation-gated workflow. The only weakness is minor verbosity in the introductory and best-practices prose.

Suggestions

Trim the opening paragraph and the 'Best Practices' list to the non-obvious items only, removing restatements of general knowledge.

Drop the redundant explanatory lead-ins (e.g. 'Try native PDF libraries first (fastest, preserves structure)') where the code already conveys intent.

DimensionReasoningScore

Conciseness

The body is mostly efficient and well-organized with executable code, but the intro paragraph and 'Best Practices' prose restate concepts and could be tightened without losing clarity.

2 / 3

Actionability

Every stage provides fully executable, copy-paste-ready code (PyPDF2, pdftotext subprocess, pdfplumber/pdfminer, pytesseract) plus specific shell commands.

3 / 3

Workflow Clarity

A clearly sequenced Stage 1-4 hierarchy with explicit success criteria (no exceptions, non-empty text), accumulated error logging, and a validation/feedback loop in the robust_pdf_extraction implementation.

3 / 3

Progressive Disclosure

A single-file, single-purpose skill under 50 lines of guidance with no need for external references, organized into clear sections; per the simple-skills note this scores 3.

3 / 3

Total

11

/

12

Passed

Description

32%

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 conveys the skill's purpose but omits explicit "when to use" trigger guidance and relies on a single abstract phrase rather than concrete enumerated actions. Adding a Use-when clause with natural trigger terms would meaningfully improve it.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when PDF or document extraction fails or returns empty/garbled text'.

Enumerate concrete actions (e.g. 'Extract text and tables, recover content from scanned PDFs via OCR') instead of the abstract 'sequential tool alternatives'.

Include common natural terms users say — 'PDFs', 'scanned PDFs', '.pdf', 'document extraction' — to improve trigger matching.

DimensionReasoningScore

Specificity

Names the domain and some actions ("fallback strategy", "extraction", "sequential tool alternatives") but does not enumerate multiple concrete actions like text or table extraction.

2 / 3

Completeness

It describes what the skill does but provides no "Use when..." clause or equivalent explicit trigger guidance, and a missing when-clause caps completeness at 2 with this case landing at 1.

1 / 3

Trigger Term Quality

Includes relevant keywords ("PDF", "document", "extraction") but misses common natural variations users would say, such as "PDFs", "forms", or ".pdf".

2 / 3

Distinctiveness Conflict Risk

"fallback strategy for PDF/document extraction" is somewhat specific to extraction failure but lacks distinct triggers and could overlap with general PDF skills.

2 / 3

Total

7

/

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.