pdf-engine-fallback

Retry PDF generation with alternative engines when pandoc fails

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./benchmarks/gdpval/skills/pdf-engine-fallback/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 a clear, validated retry workflow, but it is padded by duplication between the prose steps and the full script, and at this size it should externalize bulkier material.

Suggestions

Eliminate the duplication between 'Steps' and the 'Complete Fallback Script' — keep one as the primary method and reference the other instead of restating the same engine-by-engine logic twice.

Move the full fallback script to scripts/pdf-fallback.sh and the engine-selection guide / troubleshooting to a reference file, keeping SKILL.md a concise overview that links out, which fits progressive disclosure for a skill this size.

Dimension	Reasoning	Score
Conciseness	It avoids explaining concepts Claude already knows, but the 'Steps' section duplicates the 'Complete Fallback Script' logic and the engine table repeats step content, so it could be tightened rather than earning level 3.	2 / 3
Actionability	Provides fully executable pandoc/which/apt-get commands and a complete, copy-paste-ready pdf-fallback.sh, matching the level-3 anchor.	3 / 3
Workflow Clarity	A clear 4-step sequence with an explicit error-recovery feedback loop in the script (success exits early, failures fall through to the next engine, final FAILURE exit); PDF generation is not a destructive/batch op so the level-2 cap does not apply.	3 / 3
Progressive Disclosure	Single self-contained file with clear headers and no broken references, but at ~147 lines (above the 50-line simple-skill allowance) it keeps a full executable script plus guide and troubleshooting inline rather than externalizing them.	2 / 3
	Total	10 / 12 Passed

Description

75%

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 concrete and trigger-explicit, cleanly answering what and when for a distinct niche, but it names only one action and has narrow keyword coverage.

Suggestions

List multiple concrete actions (check available engines, retry with xelatex for Unicode, install missing engines) to lift specificity from a single action toward the level-3 'multiple specific actions' anchor.

Broaden trigger terms to natural phrasings users actually say, e.g. 'when pandoc PDF generation fails with engine errors, missing fonts, or Unicode/CJK characters', and name the engines consulted (xelatex, pdflatex, wkhtmltopdf).

Dimension	Reasoning	Score
Specificity	Names the domain and a single concrete action ('Retry PDF generation with alternative engines'), but does not list multiple concrete actions as the level-3 anchor requires.	2 / 3
Completeness	Answers both what ('Retry PDF generation with alternative engines') and when with an explicit trigger ('when pandoc fails'), an equivalent 'Use when' clause that avoids the level-2 cap.	3 / 3
Trigger Term Quality	Contains relevant natural terms ('PDF generation', 'pandoc fails') but misses common variations users would say (PDF conversion, latex/xelatex engine errors, Unicode/CJK), matching the level-2 anchor.	2 / 3
Distinctiveness Conflict Risk	Targets a clear niche (pandoc PDF-engine fallback) with a distinct trigger unlikely to fire for unrelated skills; uses third-person voice with no I/you penalty.	3 / 3
	Total	10 / 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-engine-fallback/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.