CtrlK
BlogDocsLog inGet started
Tessl Logo

pdf-gen-fallback-501bcc

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

67

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

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
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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 and clearly sequenced with explicit validation and error-handling feedback loops. Its main weakness is redundancy across the example sections and a 'Why This Works' section that explains concepts Claude already knows.

Suggestions

Consolidate the three near-duplicate PDF generation code blocks (Step 4, Step 5, and the Complete Example) into a single canonical example with error handling.

Trim or remove the 'Why This Works' section, which states obvious rationale Claude already understands.

Keep only the most representative library snippets in the body and rely on the Common Libraries table for the rest to reduce token cost.

DimensionReasoningScore

Conciseness

The body is mostly lean executable code, but the 'Why This Works' bullets explain rationale Claude already knows and the Step 4, Step 5, and Complete Example sections repeat near-duplicate PDF generation snippets that could be tightened.

2 / 3

Actionability

All guidance is fully executable: concrete `python -c` scripts, `pip install` commands, library checks, and verification commands that are copy-paste ready.

3 / 3

Workflow Clarity

A clear 6-step numbered sequence includes explicit verification checkpoints (Step 6 and the Complete Example's verify step) and try/except feedback loops for error recovery.

3 / 3

Progressive Disclosure

The skill is a single self-contained file with no bundle files and well-organized sections (When to Use, Steps, Complete Example, Common Libraries), avoiding nested references and wall-of-text organization.

3 / 3

Total

11

/

12

Passed

Description

75%

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 answers both what the skill does and when to use it with an explicit trigger, and is reasonably specific to a distinct niche. Its main weaknesses are internal jargon ('execute_code_sandbox') in the trigger and a lack of enumerated concrete actions.

Suggestions

Add a natural-language 'Use when...' phrasing with user-facing terms (e.g., 'Use when PDF or document generation fails with unclear sandbox errors') to improve trigger term quality.

Replace or pair the internal tool name 'execute_code_sandbox' with plain language a user would actually say.

Enumerate a few concrete actions (e.g., generate PDF/DOCX/XLSX) to lift specificity to the top anchor.

DimensionReasoningScore

Specificity

The description names the domain ('PDF/document generation') and the concrete scenario ('Fallback pattern... when execute_code_sandbox fails with opaque errors'), but does not enumerate multiple specific concrete actions like the score-3 anchor requires.

2 / 3

Completeness

Both 'what' (fallback pattern for PDF/document generation) and 'when' (when execute_code_sandbox fails with opaque errors) are answered with an explicit equivalent trigger clause, satisfying the score-3 anchor.

3 / 3

Trigger Term Quality

'PDF' and 'document generation' are natural user terms, but 'execute_code_sandbox fails with opaque errors' is internal tool jargon a user would not say, and common variations are missing.

2 / 3

Distinctiveness Conflict Risk

The trigger is narrowly keyed to a specific sandbox-failure fallback condition, carving a clear niche unlikely to fire for unrelated PDF skills.

3 / 3

Total

10

/

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.