pdf-extraction-fallbacks-7d54a9

Multi-fallback PDF extraction with sequential approaches and early failure detection

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./benchmarks/gdpval/skills/pdf-extraction-fallbacks-7d54a9/SKILL.md

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable code and a well-sequenced, validated workflow, but it sacrifices conciseness by duplicating extraction logic across inline snippets and a full implementation, and it keeps all detail inline rather than splitting into reference files.

Suggestions

De-duplicate the extraction methods: keep either the inline per-fallback snippets or the consolidated Python implementation, not both, to reduce token cost.

Move the 'Complete Python Implementation' and 'Integration Example' into a referenced script/reference file, keeping SKILL.md as a lean overview pointing to the full code.

Trim the verbose inline comments and the redundant 'Best Practices'/'Common Failure Modes' tables where they restate thresholds already shown in the workflow.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and avoids explaining what a PDF is, but it repeats the same extraction logic three times (inline fallback snippets plus a full Python implementation) and includes verbose comments and a near-duplicate integration example, so it could be tightened.	2 / 3
Actionability	It provides fully executable bash and Python snippets with concrete commands (curl, pdftotext, fitz, pdfplumber), specific thresholds, and a copy-paste-ready complete implementation — matching the 'Fully executable code/commands' anchor.	3 / 3
Workflow Clarity	Steps are explicitly sequenced (download → validate → sequential fallbacks → sanity check) with concrete validation checkpoints (size < 1KB, HTML detection, char/word thresholds) and a feedback loop that rejects and tries the next method, satisfying the 'Clear sequence with explicit validation steps' anchor.	3 / 3
Progressive Disclosure	Content is organized into clear sections, but everything lives inline in SKILL.md with no bundle references — the complete implementation and integration example that could be in separate files are kept in the main body, fitting 'content that should be separate is inline.'	2 / 3
	Total	10 / 12 Passed

Description

50%

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 identifies the domain and a couple of features but lacks concrete action verbs and any 'Use when...' trigger guidance. It is above the vague baseline yet below the fully concrete, trigger-complete examples.

Suggestions

Add concrete actions: e.g. 'Download PDFs, validate downloads, and extract text via multiple fallback methods.'

Append a 'Use when...' clause with natural user trigger terms like 'PDF files, .pdf links, extract text from PDF, document download failures.'

Use third person and replace abstract phrasing like 'sequential approaches' with specific named tools (pdftotext, PyMuPDF, pdfplumber) to sharpen specificity.

Dimension	Reasoning	Score
Specificity	The description names a domain (PDF extraction) and references 'sequential approaches' and 'early failure detection,' but it does not list multiple concrete actions like 'extract text,' 'download documents,' or 'validate output' — it stays at the level of 'Names domain and some actions, but not comprehensive.'	2 / 3
Completeness	It states what the skill does ('Multi-fallback PDF extraction...'), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which the guidelines say should cap completeness at 2.	2 / 3
Trigger Term Quality	'PDF extraction' is a natural term a user would say, but there are no common variations or explicit user-facing trigger phrasing ('PDF files,' 'extract text from PDF,' 'download PDF'); it falls to 'Some relevant keywords but missing common variations.'	2 / 3
Distinctiveness Conflict Risk	PDF extraction is a fairly distinct niche, but the phrasing is generic enough ('multi-fallback,' 'sequential approaches') that it could overlap with broader document-handling skills rather than being a clearly distinct trigger set.	2 / 3
	Total	8 / 12 Passed

Validation

100%

Warnings & errors only

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
Path: benchmarks/gdpval/skills/pdf-extraction-fallbacks-7d54a9/SKILL.md
Commit: c5a9c4b

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.