CtrlK
BlogDocsLog inGet started
Tessl Logo

pdf-checklist-generation

Generate structured PDF checklists and reports using Python libraries in sandbox

54

Quality

60%

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-checklist-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 body is well-structured, executable, and includes a verification checkpoint, making it actionable and clear; the main weakness is mild verbosity in best-practices/pitfalls sections that restate knowledge Claude already has.

Suggestions

Trim "Best Practices" and "Common Pitfalls" to non-obvious items, removing guidance Claude already knows (e.g., install before import, use UTF-8).

Add a brief validate->fix->retry feedback loop in the workflow for when PDF generation or file verification fails.

Optionally move the library comparison table and advanced examples into a references file to tighten the main body further.

DimensionReasoningScore

Conciseness

Mostly efficient with a complete inline code example and clear sections, but the "Best Practices" and "Common Pitfalls" lists include guidance Claude already knows (install before import, verify file existence, use UTF-8) that could be trimmed.

3 / 5

Actionability

Provides copy-paste-ready reportlab code plus install, sandbox execution, and verification steps; minor gaps are that the fpdf and matplotlib alternatives listed in the table are not demonstrated.

4 / 5

Workflow Clarity

A clear 4-step sequence with an explicit verification checkpoint (Step 4: verify the PDF was created) for a batch/output operation; only a minor gap is the lack of a formal validate->fix->retry feedback loop.

4 / 5

Progressive Disclosure

A single, well-organized SKILL.md (~115 lines) with clear sections and no external references; per the simple-skill guideline this is strong, with only minor opportunity to split the library comparison or advanced examples into reference files.

4 / 5

Total

15

/

20

Passed

Description

53%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 names a concrete domain and a couple of actions but lacks an explicit "Use when..." trigger and broader keyword coverage, leaving it adequate rather than strong.

Suggestions

Add an explicit trigger clause, e.g., "Use when generating downloadable PDF checklists, scorecards, or reports in a sandbox environment."

Broaden trigger terms to include synonyms users would naturally say, such as ".pdf", "scorecards", "fillable forms", and "downloadable reports".

Expand the concrete action list for more comprehensive coverage (e.g., tables, sections, scoring criteria) rather than just "checklists and reports".

DimensionReasoningScore

Specificity

States "Generate structured PDF checklists and reports using Python libraries in sandbox", naming the domain plus 1-2 concrete actions, but coverage is not comprehensive (no forms, merging, conversion, etc.).

3 / 5

Completeness

Provides a clear "what" (generate PDF checklists/reports) but no explicit "Use when..." trigger clause, which per rubric guidance caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural terms like "PDF", "checklists", and "reports", but misses common variations and synonyms users would say (e.g., .pdf, scorecards, forms, fillable documents).

3 / 5

Distinctiveness Conflict Risk

The niche (structured PDF checklists/reports via Python in sandbox) is mostly distinct with concrete triggers, with only minor overlap risk against general PDF skills.

4 / 5

Total

13

/

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.