pandoc-pdf-error-recovery

Systematic approach to diagnose and recover from pandoc PDF conversion unknown errors

Quality

70%

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/pandoc-pdf-error-recovery/SKILL.md

Quality

Content

75%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 body is highly actionable with copy-paste commands and a clear sequenced workflow with error-recovery feedback loops. Its main weakness is mild over-explanation of concepts Claude already knows.

Suggestions

Trim explanations of basics Claude already knows, e.g. the '2>&1 | tee pattern captures both stdout and stderr' note and the one-line engine type descriptions.

Add an explicit validation gate such as 'Only proceed to the next engine once you have inspected conversion.log for the actual error message' to sharpen the checkpoints.

Consider moving the engine comparison table and dependency-install commands into a separate reference file so the main procedure stays lean.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but includes explanations Claude already knows (e.g. 'The 2>&1 \| tee pattern captures both stdout and stderr to a log file' and engine descriptions like 'pdflatex: Standard LaTeX, fast but limited Unicode support'), which could be trimmed — anchor 3 rather than 4.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands (pandoc --version, which pdflatex xelatex..., pandoc input.md -o output.pdf --pdf-engine=xelatex 2>&1 \| tee, sudo apt-get install texlive-full) covering the common cases across multiple engines and fallbacks, matching anchor 5.	5 / 5
Workflow Clarity	A clear 7-step sequence with feedback loops (analyze captured log in Step 4, fall back to alternative engines in Step 5, install deps in Step 6), but checkpoints are implicit rather than crisply gated ('Only proceed when valid'), so anchor 4 over 5.	4 / 5
Progressive Disclosure	Well-organized into clearly labeled sections (Overview, Step-by-Step Procedure, Quick Reference, Tips) and self-contained with no external references, but at ~119 lines it exceeds the under-50-lines threshold that would let well-organized sections alone reach anchor 5.	4 / 5
	Total	16 / 20 Passed

Description

65%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 names a specific, distinctive niche and two concrete actions but lacks an explicit 'Use when...' trigger clause, which caps completeness. Trigger-term coverage is good though not exhaustive.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when pandoc fails to convert a document to PDF with an unknown or vague error message.'

Expand the action list beyond 'diagnose and recover' to name the concrete recovery techniques (e.g., switch PDF engine, install missing LaTeX packages) for higher specificity.

Include the .pdf extension and common synonyms (e.g., 'PDF generation', 'pandoc --pdf-engine') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('pandoc PDF conversion unknown errors') and two concrete actions ('diagnose and recover'), but is not comprehensive — anchor 3 fits 1-2 concrete actions, and it falls short of anchor 4's 'several specific actions'.	3 / 5
Completeness	The 'what' is clear (diagnose and recover from pandoc PDF conversion errors), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at anchor 3.	3 / 5
Trigger Term Quality	Includes natural terms a user would say ('pandoc', 'PDF conversion', 'unknown errors') giving good keyword coverage, but misses synonyms and file extensions (.pdf) that would push it to anchor 5.	4 / 5
Distinctiveness Conflict Risk	Targets a clear, narrow niche (pandoc PDF conversion error recovery) with distinct triggers and minimal overlap risk with other skills, matching the anchor 5 example of a clear niche.	5 / 5
	Total	15 / 20 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/pandoc-pdf-error-recovery/SKILL.md
Commit: 3827781

Reviewed: 24 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.