CtrlK
BlogDocsLog inGet started
Tessl Logo

direct-reportlab-pdf-generation

Generate complex multi-page PDFs by running reportlab Python code directly via run_shell when shell_agent fails on document creation

59

Quality

67%

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/direct-reportlab-pdf-generation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 skill body is actionable and clearly sequenced with a verification step, and it is well-structured for a no-bundle skill. It is somewhat verbose in its explanatory sections and the execution examples contain placeholders that prevent a perfect actionability score.

Suggestions

Trim the 'Advantages Over shell_agent' section and the prose about text wrapping; assume Claude knows these library behaviors.

Replace the Step 3 placeholder blocks with one fully wired, copy-paste-ready script so execution is end-to-end runnable.

Add a brief validate-and-retry loop (e.g., re-run on PDF build errors, confirm page count) to strengthen the workflow checkpoint.

DimensionReasoningScore

Conciseness

The body is mostly efficient with a complete script and focused steps, but the 'Advantages Over shell_agent' section and remarks like 'ReportLab automatically handles text wrapping' add explanation Claude does not need and could be trimmed.

3 / 5

Actionability

It provides a complete, executable reportlab script plus concrete run_shell execution patterns, but the Step 3 execution blocks use placeholders ('# Your complete reportlab script here') rather than a fully wired runnable example.

4 / 5

Workflow Clarity

The five numbered steps are clearly sequenced and Step 5 provides an explicit output verification checkpoint ('ls -la', 'pdfinfo'), with only minor gaps such as no error-recovery feedback loop.

4 / 5

Progressive Disclosure

Sections are well-organized (When to Use, Core Technique, Steps, Common Patterns, Troubleshooting) and there are no bundle files to navigate, though the full inline script is long enough that it could optionally live in a reference file.

4 / 5

Total

15

/

20

Passed

Description

67%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 is a clear, third-person statement with both a 'what' and a conditional 'when', and it is reasonably distinct from sibling skills. It is somewhat jargon-heavy and would benefit from more natural trigger terms.

Suggestions

Add natural trigger phrases users would actually say (e.g., 'PDF', '.pdf', 'generate PDF', 'create a multi-page document') alongside the technical 'run_shell'/'shell_agent' terms.

Broaden the 'when' clause beyond a single failure condition to cover more situations where direct reportlab control is preferable.

Tighten 'complex multi-page PDFs' with a few concrete capability verbs (e.g., 'style, paginate, and lay out') to lift specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

The description names the domain ('complex multi-page PDFs') and a concrete action mechanism ('running reportlab Python code directly via run_shell'), which lists several specific actions but leaves out finer capabilities like styling or pagination control.

4 / 5

Completeness

It explicitly answers both 'what' (generate multi-page PDFs via reportlab/run_shell) and 'when' (when shell_agent fails on document creation), though the trigger is a single failure condition rather than broader, more explicit triggers.

4 / 5

Trigger Term Quality

It includes relevant keywords ('PDFs', 'reportlab', 'run_shell', 'shell_agent') but is heavy on technical jargon and missing natural synonyms or file extensions like 'PDF', '.pdf', or 'document generation' that users would actually say.

3 / 5

Distinctiveness Conflict Risk

The fallback-on-failure framing ('when shell_agent fails') carves a distinct niche unlikely to trigger for general PDF skills, with only minor overlap risk against other document-generation skills.

4 / 5

Total

15

/

20

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.