pdf-gen-fallback-501bcc

Fallback pattern for PDF/document generation when execute_code_sandbox fails with opaque errors

Quality

68%

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/pdf-gen-fallback-501bcc/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 content is highly actionable with executable code throughout and a clear, verified workflow. Its main drawback is redundancy from repeating near-identical PDF generation blocks across multiple sections.

Suggestions

Consolidate the repeated reportlab PDF examples into a single canonical snippet to remove padding across Step 4, Step 5, and the Complete Example.

Tighten or remove the 'Why This Works' section, which restates concepts Claude already knows.

Add an Excel/xlsxwriter example to match the libraries listed in the Common Libraries table.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with well-organized sections, but the reportlab PDF generation code is repeated three times (Step 4, Step 5, and the Complete Example) and the 'Why This Works' section states fairly obvious points, so it could be tightened.	3 / 5
Actionability	Guidance is fully executable and copy-paste ready: concrete library checks, pip installs, complete PDF and DOCX generation snippets with try/except, and file verification commands covering the common cases.	5 / 5
Workflow Clarity	A clear six-step sequence is present with an explicit verification step (Step 6) and error-handling feedback in Step 5, but recovery is 'exit on error' rather than a validate-fix-retry loop, leaving a minor checkpoint gap.	4 / 5
Progressive Disclosure	The single-file skill is well structured with clear sections (When to Use, Step-by-Step, Complete Example, Common Libraries) and no nested references, though at ~140 lines some repeated examples could be consolidated.	4 / 5
	Total	16 / 20 Passed

Description

62%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 states both what the skill does and when to apply it, with a specific niche around sandbox failures. Its main weakness is relying on internal tool jargon ('execute_code_sandbox') as the trigger rather than natural user-facing language.

Suggestions

Add user-facing trigger phrasing (e.g., 'Use when PDF or DOCX generation fails or produces unhelpful errors') alongside the internal trigger.

Include common synonyms and file extensions (PDF, DOCX, .pdf, .docx) to improve natural keyword coverage.

Name a couple more concrete actions (e.g., generate, verify) to lift specificity beyond a single fallback pattern.

Dimension	Reasoning	Score
Specificity	Names the domain ('PDF/document generation') and a concrete fallback action, but coverage is limited to a single pattern rather than multiple specific actions, matching the 'names domain and 1-2 concrete actions' anchor.	3 / 5
Completeness	Both 'what' (fallback pattern for PDF/document generation) and 'when' (when execute_code_sandbox fails with opaque errors) are explicit; the 'when' is specific but tied to an internal failure state rather than user-facing trigger phrases, so it stops short of a 5.	4 / 5
Trigger Term Quality	Natural terms like 'PDF' and 'document generation' are present, but the trigger hinges on the internal jargon 'execute_code_sandbox fails with opaque errors' that a user would not naturally say, and synonyms/extensions (DOCX, .pdf) are missing.	3 / 5
Distinctiveness Conflict Risk	The sandbox-failure fallback niche is fairly distinct with a specific trigger condition, but it could still overlap with general PDF/document-generation skills, leaving minor conflict risk.	4 / 5
	Total	14 / 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/pdf-gen-fallback-501bcc/SKILL.md
Commit: 3827781

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