pdf-extraction-fallback-80956b

Multi-fallback PDF download and text extraction with early failure detection

Quality

68%

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-fallback-80956b/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 clear, validated multi-fallback workflow. Its main weaknesses are verbosity from duplicated code and explanatory notes, and a monolithic structure with no progressive disclosure to separate files.

Suggestions

Remove the duplicated 'Complete Workflow Script' or reference it as the canonical version to eliminate repeated logic.

Trim background notes (e.g. 'Notes for Regulatory Documents') that restate concepts Claude already knows.

Consider splitting the full script into a scripts/ file referenced one level deep to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body provides concrete code but pads it with explanatory notes Claude already knows ('Government and regulatory websites often...') and duplicates the per-fallback snippets inside a full 'Complete Workflow Script'. It is not a 3 because the duplicated logic and background notes could be tightened; not a 1 because the content is mostly actionable rather than conceptual filler.	2 / 3
Actionability	It provides fully executable bash and Python (curl, pdftotext, PyMuPDF, pdfplumber) plus install commands that are copy-paste ready. It is not a 2 because the examples are concrete and complete rather than pseudocode or missing key details.	3 / 3
Workflow Clarity	Steps are clearly sequenced (download+validate, sequential fallbacks, sanity validation) with explicit validation checkpoints (file-size check, error-pattern scan, content thresholds) and a failure-documentation table. It is not a 2 because validation and fallback loops are explicit rather than implicit.	3 / 3
Progressive Disclosure	No bundle files exist and the skill is a single ~250-line document with all content — including a full standalone script — inline rather than split into referenced files. It is not a 3 because nothing is offloaded to one-level-deep references; not a 1 because section organization provides some structure.	2 / 3
	Total	10 / 12 Passed

Description

60%

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 concise and names several concrete capabilities, but it lacks an explicit 'Use when...' trigger and has only partial coverage of natural keyword variations. It is reasonably specific to PDFs but could conflict with a general PDF extraction skill.

Suggestions

Add an explicit 'Use when...' clause naming trigger scenarios, e.g. 'Use when downloading PDFs from protected sites or when initial PDF downloads yield error pages.'

Broaden natural keyword coverage to include 'PDFs', 'extract text from PDF', and '.pdf' so users' phrasings match the trigger.

Sharpen the niche wording to distinguish this from a generic PDF extraction skill (emphasize the fallback/protected-source angle).

Dimension	Reasoning	Score
Specificity	The phrase 'Multi-fallback PDF download and text extraction with early failure detection' names multiple concrete actions — download, text extraction, and early failure detection — rather than vague abstractions. It is not a 2 because it lists several specific capabilities, not just a domain plus a single action.	3 / 3
Completeness	It clearly states what the skill does but contains no 'Use when...' clause or equivalent explicit trigger guidance for when to invoke it. Per the rubric, a missing explicit trigger caps completeness at 2; it is not a 1 because the 'what' is clearly stated.	2 / 3
Trigger Term Quality	It includes relevant keywords a user might say ('PDF download', 'text extraction'), but misses common natural variations such as 'PDFs', 'extract text', or '.pdf'. It is not a 3 because the keyword coverage is partial rather than comprehensive.	2 / 3
Distinctiveness Conflict Risk	The 'multi-fallback' and 'early failure detection' framing gives it a clearer niche than a generic PDF skill, but it could still overlap with a general PDF extraction skill. It is not a 3 because the description is terse and lacks distinct triggers that would prevent conflict.	2 / 3
	Total	9 / 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-fallback-80956b/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.