pandoc-pdf-error-resolution

Systematic debugging workflow for pandoc PDF conversion errors

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./benchmarks/gdpval/skills/pandoc-pdf-error-resolution/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 content is highly actionable with a clear, validated workflow, but it carries some unnecessary explanation of basics Claude already knows and does not split its sizable script/reference material into bundle files for progressive disclosure.

Suggestions

Trim explanations of known concepts (e.g. the pandoc-delegates-to-engines note and the per-engine characteristic blurbs) to tighten conciseness.

Move the complete debug script into a scripts/ file (e.g. scripts/pandoc-pdf-debug.sh) and reference it from the body, improving progressive disclosure for this 140-line skill.

Consider extracting the command quick-reference table into a references/ file so the SKILL.md body stays a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly actionable commands, but it explains concepts Claude already knows (e.g. 'pandoc itself doesn't generate PDFs directly—it delegates to external PDF engines', 'This confirms pandoc is available and shows the version number', and the engine-characteristic blurbs). It is efficient but padded with unnecessary explanation that could be trimmed.	2 / 3
Actionability	It provides fully executable commands (`pandoc --version`, `which pdflatex xelatex ...`, `pandoc input.md -o output.pdf --pdf-engine=xelatex`, `tlmgr install`, `apt-get install`) plus a complete, copy-paste bash script. The guidance is concrete and ready to run, matching the 'fully executable; copy-paste ready' anchor.	3 / 3
Workflow Clarity	The 6-step procedure is clearly sequenced with an explicit error-capture checkpoint ('Always capture the complete error output before falling back') and a validate-then-fallback loop demonstrated in the example script (`if [ $? -eq 0 ]`). This is not a destructive/batch operation, so the workflow-clarity cap does not apply.	3 / 3
Progressive Disclosure	Sections are well organized, but the ~140-line file keeps the full debug script and quick-reference inline with no external references or file splitting. Because it exceeds the 50-line simple-skill threshold and content that could be separate remains inline, it fits the 'some structure but content that should be separate is inline' anchor rather than a 3.	2 / 3
	Total	10 / 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 distinctive and targets a clear niche, but it is a single noun phrase that omits concrete actions and an explicit 'Use when...' trigger, capping completeness and trigger quality at the mid level.

Suggestions

Add an explicit trigger clause, e.g. 'Use when pandoc fails with an "unknown error" during PDF conversion while succeeding for other formats.'

List one or two concrete actions to raise specificity, e.g. '...checks available PDF engines and retries with an explicit --pdf-engine flag.'

Include common user phrasings such as 'pandoc to PDF' or 'PDF generation failed' to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The phrase 'Systematic debugging workflow for pandoc PDF conversion errors' names the domain and a general action ('debugging workflow') but does not list concrete actions like verifying pandoc, checking engines, or retrying with an explicit flag. It is not vague enough for a 1, yet lacks the multiple specific actions required for a 3.	2 / 3
Completeness	It answers what (a debugging workflow for pandoc PDF conversion errors) but when is only implied from the domain, with no explicit 'Use when...' trigger clause. Per the judging guidelines, a missing explicit trigger caps completeness at 2.	2 / 3
Trigger Term Quality	It includes natural terms a user might say ('pandoc', 'PDF', 'conversion errors'), but misses common variations such as 'PDF generation', 'pandoc to PDF', or 'PDF export'. Coverage is relevant but incomplete, matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The combination 'pandoc PDF conversion errors' is a clear, narrow niche with distinct trigger terms, making it unlikely to fire for an unrelated skill. It matches the 'clear niche with distinct triggers; unlikely to conflict' anchor.	3 / 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/pandoc-pdf-error-resolution/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.