pdf-checklist-generator

Generate structured PDF checklists and reports with tables, sections, and scoring criteria using Python libraries

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-checklist-generator/SKILL.md

Quality

Content

77%

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 with copy-paste-ready executable templates and a clear sequenced workflow including verification, but it suffers from redundant near-duplicate code examples and keeps everything monolithically inline rather than offloading detail to reference files.

Suggestions

Consolidate the three near-duplicate reportlab examples (Template A, Template C, Example Complete Workflow) into one canonical template plus short diffs to reduce redundancy.

Move the larger template variants, common patterns, and troubleshooting table into reference files (e.g., TEMPLATES.md, PATTERNS.md) and link to them one level deep.

Add an explicit fix-and-retry loop to Step 4 so verification failures have a clear recovery path.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and avoids explaining concepts Claude already knows, but it repeats near-identical reportlab PDF-building code across Template A, Template C, and the Example Complete Workflow, which is padding that could be tightened.	2 / 3
Actionability	Three complete, executable Python templates with real reportlab/fpdf2 imports, Table/TableStyle usage, doc.build(), and a concrete ARTIFACT_PATH convention are copy-paste ready, matching the fully executable anchor.	3 / 3
Workflow Clarity	A clear four-step sequence (Plan, Write, Include ARTIFACT_PATH, Verify) includes an explicit verification checkpoint in Step 4, satisfying the clear-sequence-with-validation anchor; it is a lighter 3 since there is no validate-fix-retry feedback loop.	3 / 3
Progressive Disclosure	The ~270-line skill is well-organized into sections but keeps large, separable content (three full templates, common patterns, troubleshooting) entirely inline with no one-level-deep reference files, matching the 'content that should be separate is inline' anchor.	2 / 3
	Total	10 / 12 Passed

Description

60%

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 concrete about what the skill produces but lacks any explicit "when to use it" trigger guidance, capping completeness and trigger coverage. It is reasonably specific and distinct but would benefit from a Use-when clause.

Suggestions

Add an explicit 'Use when...' trigger clause naming natural user phrasing (e.g., 'Use when generating PDF checklists, scorecards, reports, or tabular deliverables').

Broaden trigger terms to include common variations like 'scorecard', 'form', and 'document generation'.

Consider whether 'reports' is too broad and tighten it to the checklist/scorecard niche to reduce overlap with general document skills.

Dimension	Reasoning	Score
Specificity	"Generate structured PDF checklists and reports with tables, sections, and scoring criteria" names multiple concrete deliverables and features, matching the anchor that lists several specific concrete actions.	3 / 3
Completeness	The description clearly states what the skill does but omits any "Use when..." clause or equivalent trigger guidance, so per the judging guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	Natural keywords like "PDF checklists" and "reports" appear, but coverage is incomplete and lacks common variations such as scorecard, form, or document, fitting the "some relevant keywords but missing common variations" anchor.	2 / 3
Distinctiveness Conflict Risk	The PDF checklist/report/scorecard niche is somewhat specific, but the broad term "reports" and absence of explicit triggers mean it could still overlap with other document-generation skills.	2 / 3
	Total	9 / 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/pdf-checklist-generator/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.