CtrlK
BlogDocsLog inGet started
Tessl Logo

reportlab-styles

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

61

Quality

71%

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/reportlab-styles/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 body is a tight, well-structured reference with fully executable code examples and an unambiguous single-action workflow. Its only weakness is mild redundancy across the mistake, best-practices, and checklist sections.

DimensionReasoningScore

Conciseness

The body is mostly efficient and does not explain concepts Claude already knows, but the 'Common Mistake to Avoid', 'Best Practices', and final checklist overlap noticeably and could be tightened, fitting 'mostly efficient but includes some unnecessary explanation or could be tightened'.

2 / 3

Actionability

It provides fully executable, copy-paste-ready Python for correct usage, the wrong pattern, and creating custom styles, matching 'fully executable code/commands; specific examples; copy-paste ready'.

3 / 3

Workflow Clarity

This is a simple single-purpose reference skill with an unambiguous single action (get the stylesheet, access by name, do not redefine existing names) and an explicit checklist; per the simple-skills note, that warrants a 3 with no destructive workflow requiring validation.

3 / 3

Progressive Disclosure

Content is well-organized into clear sections (overview, styles table, correct usage, common mistake, best practices, checklist) with no need for external references, and the inline styles table is appropriately compact rather than a monolithic wall of text.

3 / 3

Total

11

/

12

Passed

Description

57%

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 specific and clearly distinguishable but reads as a single action with no explicit 'when to use' trigger guidance. It is solid but stops short of the highest bar because it lacks a use-trigger and broader natural keywords.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when generating PDFs with reportlab and styling paragraphs, or when you hit a KeyError on a pre-defined style name.'

Broaden the action beyond one verb to list concrete actions (get the stylesheet, access styles by name, base custom styles on existing ones) to raise specificity.

Add natural trigger terms a user would actually say ('reportlab styles', 'paragraph styles', 'PDF styling') alongside the technical 'getSampleStyleSheet()' reference.

DimensionReasoningScore

Specificity

It names the domain (reportlab pre-defined styles) and a single concrete action ('Use ... correctly'), but does not list multiple specific actions, matching the 'names domain and some actions, but not comprehensive' anchor.

2 / 3

Completeness

It states what the skill does (use reportlab's pre-defined styles correctly) but has no 'Use when...' trigger clause; per the guidelines a missing explicit trigger caps completeness at 2 ('has what, but when is missing or only implied').

2 / 3

Trigger Term Quality

It includes the relevant technical keywords ('reportlab', 'pre-defined styles', 'getSampleStyleSheet()') but leans on API jargon and lacks common natural variations a user might say, fitting 'some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

The niche is very specific (reportlab's getSampleStyleSheet pre-defined styles) and unlikely to overlap with other skills, matching 'clear niche with distinct triggers; unlikely to conflict'.

3 / 3

Total

9

/

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.