CtrlK
BlogDocsLog inGet started
Tessl Logo

pdf-extraction-fallback

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

58

Quality

66%

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

82%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 skill body is highly actionable with executable code at every stage and a clear fallback workflow supported by validation criteria and a failure-mode table. It is well-structured and concise, with only minor room to tighten prose and add an explicit output-quality checkpoint.

DimensionReasoningScore

Conciseness

The body is mostly lean code and a useful failure-mode table with minimal concept explanation, though the intro paragraph and 'Core Principle' section restate context that could be trimmed.

4 / 5

Actionability

Provides fully executable, copy-paste-ready code for each stage plus a complete robust_pdf_extraction orchestrator covering the common cases, with specific commands and library calls.

5 / 5

Workflow Clarity

The Stage 1-4 fallback hierarchy is a clearly sequenced retry workflow with error collection and a Success Criteria validation block, but the content-quality check is described rather than implemented in the main flow.

4 / 5

Progressive Disclosure

Content is well-organized into clearly labeled sections (Fallback Hierarchy, Implementation Pattern, Success Criteria, Common Failure Modes) with no nested references; at ~155 lines it exceeds the simple-skill threshold that would allow a 5.

4 / 5

Total

17

/

20

Passed

Description

50%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 conveys the skill's purpose and approach but omits explicit 'when to use' trigger guidance and lacks comprehensive natural keyword coverage. It is adequate but not standout.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers (e.g., 'Use when PDF text extraction fails or returns empty/garbled output').

Expand keyword coverage to include natural synonyms and extensions such as 'PDFs', '.pdf', 'scanned documents', and 'OCR'.

List 2-3 concrete actions (e.g., extract text, recover tables, OCR scanned pages) to raise specificity.

DimensionReasoningScore

Specificity

Names the domain ('PDF/document extraction') and a concrete approach ('multi-stage fallback strategy', 'sequential tool alternatives'), but does not enumerate multiple specific actions like text extraction, form filling, or table parsing.

3 / 5

Completeness

Provides a clear 'what' (multi-stage fallback strategy for extraction) but lacks any 'Use when...' clause or explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

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

3 / 5

Distinctiveness Conflict Risk

The fallback-strategy framing is somewhat distinctive, but 'PDF/document extraction' is broad and would overlap with general PDF-processing skills, so conflict risk remains moderate.

3 / 5

Total

12

/

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.