CtrlK
BlogDocsLog inGet started
Tessl Logo

pandoc-pdf-error-recovery

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

66

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./benchmarks/gdpval/skills/pandoc-pdf-error-recovery/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The content is a lean, fully actionable, well-sequenced troubleshooting workflow: executable commands throughout, an explicit error-capture-and-fallback feedback loop, and clean section organization that needs no external references.

DimensionReasoningScore

Conciseness

The body is dominated by executable commands and brief, purposeful guidance; it avoids explaining basic concepts Claude already knows, and prose such as the engine-use-case notes and the `2>&1 | tee` explanation are concise and earn their place.

3 / 3

Actionability

Every step provides copy-paste-ready, fully executable commands (e.g. `pandoc input.md -o output.pdf --pdf-engine=xelatex 2>&1 | tee conversion.log`, `tlmgr install <package>`, `sudo apt-get install texlive-full`) with concrete install paths per OS.

3 / 3

Workflow Clarity

The seven numbered steps form a clear sequence with an explicit error-recovery feedback loop — capture stderr, analyze the log, then fall back through alternative engines — matching the score-3 anchor of clear sequencing with feedback loops.

3 / 3

Progressive Disclosure

The skill is a single self-contained troubleshooting recipe with no bundle files; it is organized into clear sections (Overview, Steps 1–7, Quick Reference, Tips) with no nested references, which is appropriate for a cohesive recipe that needs no external files.

3 / 3

Total

12

/

12

Passed

Description

57%

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 specific and clearly niche-scoped to pandoc PDF conversion errors, but it lacks an explicit 'Use when…' trigger clause and only offers a thin set of natural trigger-term variations, capping completeness and trigger quality at the mid level.

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 trigger terms to include natural variations such as 'pandoc to PDF', 'PDF export fails', and 'TeX/LaTeX engine error'.

List concrete actions to lift specificity, e.g. 'verify the installation, probe available PDF engines, and retry conversion with fallback engines.'

DimensionReasoningScore

Specificity

The phrase 'diagnose and recover from pandoc PDF conversion unknown errors' names the domain and two actions, but does not list multiple specific concrete actions like the score-3 anchor (extract, fill, merge); it stops at a general diagnose/recover pair.

2 / 3

Completeness

It answers 'what' (a systematic approach to diagnose and recover) but provides no explicit 'Use when…' trigger clause; the 'when' is only implied from 'unknown errors', which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

'pandoc', 'PDF conversion', and 'unknown errors' are natural terms a user would say, but coverage is narrow and lacks common variations such as 'PDF export', 'pandoc to PDF', or 'TeX/LaTeX engine errors'.

2 / 3

Distinctiveness Conflict Risk

The narrow scope of 'pandoc PDF conversion unknown errors' is a clear niche with distinct triggers that is unlikely to fire for unrelated document or PDF skills.

3 / 3

Total

9

/

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.