document-gen-resilient-multiformat

Resilient multi-format document generation with environment checks, auto-sanitization, and fallback engines

Quality

56%

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/document-gen-fallback-enhanced-enhanced-618c9b/SKILL.md

Quality

Content

62%

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 and workflow-clear with strong validation and recovery guidance, but it is far too verbose due to repeated sections and lacks any file-based progressive disclosure despite its length. The main weakness is token efficiency.

Suggestions

Eliminate redundancy: keep one pre-flight check and one workflow narrative; remove the Complete Example and overlapping Troubleshooting/Commands/Error tables, or merge them.

Move the sanitize_for_pdf.sh script into a scripts/ file and the Python fallback options and pandoc command reference into a references/ file, keeping SKILL.md a concise overview with one-level-deep links.

Trim conceptual asides Claude already knows (e.g. 'fpdf2 has limited Unicode support') to leaner notes.

Dimension	Reasoning	Score
Conciseness	The ~460-line body is padded with heavy redundancy: the pre-flight check appears three times (Pre-Flight Environment Check, Step 0, and the Complete Example), the workflow is restated in the Complete Example, and the 'Common pandoc Commands', 'Troubleshooting Quick Reference', and 'Error Handling' tables overlap substantially.	1 / 3
Actionability	Provides concrete, copy-paste-ready guidance throughout: executable pandoc commands, complete fpdf2/reportlab Python snippets, and a fully specified sanitize_for_pdf.sh script, with only one stub (Option C) noted as simplified.	3 / 3
Workflow Clarity	A clear Step 0–4 sequence is reinforced by a PDF-engine decision tree, an explicit Step 4 verification checkpoint (test -s output.pdf), and an error table plus recovery workflow with an engine-fallback feedback loop.	3 / 3
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ absent), so everything is inline in a single ~460-line monolithic file; the sanitization script, Python fallbacks, and reference tables are well-sectioned by headers but not split into separate files.	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 conveys the skill's purpose and distinguishing features but reads as a noun-phrase list with no explicit use-when trigger guidance and no concrete format keywords. It is adequate but not exemplary, scoring 2 across all dimensions.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers, e.g. 'Use when generating .docx/.pdf/.html from one source, or when pandoc/LaTeX PDF generation fails on Unicode.'

Reword features as concrete actions and include format keywords users say naturally ('.pdf', '.docx', '.html', 'create a PDF', 'convert markdown').

Tighten the niche by leading with the formats and the fallback angle to reduce overlap with generic document skills.

Dimension	Reasoning	Score
Specificity	Names the domain and several features ('multi-format document generation', 'environment checks', 'auto-sanitization', 'fallback engines') but as noun phrases rather than concrete verb-phrase actions, and omits the actual target formats.	2 / 3
Completeness	Clearly states what the skill does but provides no 'Use when...' trigger clause; per the rubric, a missing explicit trigger caps completeness at 2.	2 / 3
Trigger Term Quality	Includes 'document generation' but lacks the natural format keywords users actually say ('.pdf', '.docx', 'create a PDF'), so common variations are missing.	2 / 3
Distinctiveness Conflict Risk	The 'resilient ... fallback engines' framing is somewhat distinctive but the description still overlaps with other document-generation skills and lacks format-specific triggers that would separate it cleanly.	2 / 3
	Total	8 / 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/document-gen-fallback-enhanced-enhanced-618c9b/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.