CtrlK
BlogDocsLog inGet started
Tessl Logo

pdf-download-extract-fallback

Multi-step PDF download and text extraction with progressive fallback strategies

52

Quality

57%

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-download-extract-fallback/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 body is highly actionable with executable code and a sensible fallback chain, but it suffers from significant duplication, a stray second frontmatter block, and a monolithic structure with no progressive disclosure. Cleaning up the duplication and splitting detail into reference files would markedly improve it.

Suggestions

Remove the duplicated second frontmatter block (lines ~253–256) and the repeated/truncated workflow narrative so there is a single coherent flow.

De-duplicate the install instructions and tool-availability checks into one section instead of repeating them across Step 3, the pre-check, and the workflow script.

Move the long failure-mode table and full bash script into a referenced file (e.g. references/fallbacks.md) so SKILL.md stays a lean overview with one-level-deep navigation.

DimensionReasoningScore

Conciseness

Individual sections are reasonably lean with executable snippets, but the body duplicates whole blocks (install steps, a second frontmatter, repeated workflow narrative) and explains things Claude already knows, fitting 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the lean level 3.

2 / 3

Actionability

Provides copy-paste-ready curl, pdftotext, PyMuPDF, and bash script commands with concrete flags and a complete workflow script, matching 'fully executable code/commands; specific examples; copy-paste ready'.

3 / 3

Workflow Clarity

A sequenced Steps 1–5 with a file-type validation checkpoint and a pdftotext→PyMuPDF→domain-knowledge fallback loop exists, but the duplicated, partially truncated second-half structure (stray frontmatter, parallel Mode A/B and Local File workflows) makes the true entry sequence ambiguous, fitting 'steps listed but... checkpoints missing or implicit' rather than a clean level 3.

2 / 3

Progressive Disclosure

No bundle files exist and everything is inline in one ~290-line monolithic file with duplicated sections, so it is 'some structure but could be better organized; content that should be separate is inline' rather than a well-split overview with one-level references.

2 / 3

Total

9

/

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 clearly conveys the skill's purpose and domain but stops short of providing explicit usage triggers or a comprehensive action list. It is competent yet generic enough to risk overlap with sibling PDF skills.

Suggestions

Append an explicit trigger clause, e.g. "Use when downloading PDFs from web sources or extracting text from PDF files that may be corrupted or access-restricted."

List a fuller set of concrete actions and natural trigger terms ("PDFs", ".pdf", "document extraction") to lift specificity and trigger quality.

Tighten the wording to third-person action verbs and remove the redundant second frontmatter block that duplicates this description in the body.

DimensionReasoningScore

Specificity

Quotes "PDF download and text extraction with progressive fallback strategies" — names the domain and two concrete actions (download, extract) plus a strategy, but does not enumerate multiple specific operations, matching the 'names domain and some actions' anchor rather than the multi-action level 3.

2 / 3

Completeness

It states what the skill does but provides no "Use when..." trigger guidance, so per the judging guidelines completeness is capped at 2 — 'has what, but when is missing or only implied'.

2 / 3

Trigger Term Quality

Contains natural terms like "PDF", "download", and "text extraction" a user might say, but misses common variations ("PDFs", ".pdf", "forms"), fitting 'some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

The "progressive fallback" framing gives it a recognizable niche, yet without explicit triggers it could still overlap with other PDF skills, matching 'somewhat specific but could still overlap'.

2 / 3

Total

8

/

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.