reportlab-styles

Use reportlab's pre-defined styles from getSampleStyleSheet() correctly

Quality

64%

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/reportlab-styles/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 body is a well-structured, actionable reference with executable examples and a clear checklist, appropriately assuming Claude's reportlab knowledge. Minor tightening of the redundant 'Common Mistake' block and checklist would push it toward the top of the scale.

Dimension	Reasoning	Score
Conciseness	The body is efficient: a one-sentence overview, a compact style table, and focused code blocks assume Claude's competence without explaining reportlab basics. Not a 5 because the 'Common Mistake' block and the checklist restate information that could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready, executable Python for both using existing styles and creating custom styles, covering the common cases. Not a 5 because there is no end-to-end document build example and the 'wrong' example is illustrative rather than a runnable pattern.	4 / 5
Workflow Clarity	The closing Quick Reference Checklist gives a clear ordered sequence (import -> call -> access -> avoid conflicts -> unique names) appropriate for this simple, non-destructive skill. Not a 5 because the sequence is a checklist rather than an explicitly validated workflow, though no validation is needed here.	4 / 5
Progressive Disclosure	Content is well-organized into clearly labeled sections (Overview, Available Styles, Correct Usage, Common Mistake, Best Practices, Checklist) with no nested references and no bundle files needed. Not a 5 because the style table is reference-like material inlined in SKILL.md and the body exceeds 50 lines.	4 / 5
	Total	16 / 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 is concrete and narrowly scoped to reportlab's pre-defined styles, but it omits any 'Use when...' trigger guidance and lists only a single action. Adding a trigger clause and one or two more specific actions would raise completeness and specificity.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when generating PDFs with reportlab and applying paragraph styles.'

List one or two more concrete actions (e.g., 'access Title/Heading/Normal styles, create custom styles based on them') to improve specificity.

Include natural synonyms users might say (e.g., 'reportlab styles', 'paragraph styles', 'PDF styling') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('reportlab's pre-defined styles', 'getSampleStyleSheet()') and one concrete action ('Use ... correctly'), but offers only a single action rather than several specific capabilities. It is above a 2 because a concrete API is named, but below a 4 because coverage is not comprehensive.	3 / 5
Completeness	Provides a clear 'what' (use reportlab's pre-defined styles correctly) but no 'when'/Use-when clause, which per the guidelines caps completeness at 3. It is above a 2 because the 'what' is concrete, but below a 4 because trigger guidance is entirely missing.	3 / 5
Trigger Term Quality	Contains relevant keywords ('reportlab', 'pre-defined styles', 'getSampleStyleSheet()') but leans technical; it misses natural synonyms a user might say. Not a 2 because the terms are domain-relevant, not generic; not a 4 because common variations are absent.	3 / 5
Distinctiveness Conflict Risk	The niche is specific (reportlab's getSampleStyleSheet styles), giving minimal conflict risk with unrelated skills. Not a 5 because it lacks explicit trigger phrases that distinguish it at invocation time; not a 3 because it is clearly more distinct than a broad 'document files' description.	4 / 5
	Total	13 / 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/reportlab-styles/SKILL.md
Commit: 3827781

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