document-python-direct-exec

Use direct Python execution for reliable spreadsheet and document/PDF generation operations

Quality

53%

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/spreadsheet-direct-python-merged-343937/SKILL.md

Quality

Content

57%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 content is highly actionable with executable examples and good internal structure, but it is verbose for a single file and lacks output-validation checkpoints in its generation workflow. Splitting detailed examples and references into bundle files would improve both conciseness and progressive disclosure.

Suggestions

Add an explicit output-validation checkpoint to the generation workflow (e.g. verify the file exists and opens, or assert expected sheet/page count) before declaring success.

Move the longer worked examples and the troubleshooting/library tables into files under references/ and link to them from SKILL.md to reduce inline length and improve progressive disclosure.

Consolidate the three PDF examples (reportlab canvas, platypus, fpdf) into one or two, or factor the repetitive parts into a shared snippet, to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with tight code blocks, but at ~345 lines with six full code examples (three PDF generators), two tables, and extensive troubleshooting/best-practices lists, it could be tightened and includes some redundancy across the PDF examples.	3 / 5
Actionability	Provides six concrete, copy-paste-ready Python examples plus an error-handling pattern covering the common spreadsheet and PDF cases, with only minor template placeholders (e.g. "# Your code here", a bare "pass" loop) keeping it from a perfect score.	4 / 5
Workflow Clarity	A clear 2-step "write file then execute" pattern and a try/except error-handling section are present, but document/spreadsheet generation can overwrite existing files and there is no explicit output-validation or verify step, so the destructive/batch cap holds at 3.	3 / 5
Progressive Disclosure	Section headers are clear and well-ordered, but the skill exceeds 50 lines as a single monolithic file with detailed examples, library tables, and troubleshooting all inlined and no references/ or other bundle files, so content that could be split stays inline.	3 / 5
	Total	13 / 20 Passed

Description

50%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 states a clear purpose and approach but lacks an explicit trigger clause and broader trigger vocabulary, capping both completeness and trigger quality at the midpoint. It is adequate but could be sharpened with a "Use when..." phrase and file-extension terms.

Suggestions

Add an explicit trigger clause, e.g. "Use when generating or transforming Excel spreadsheets, PDFs, or Word documents via Python scripts."

Include natural file extensions and synonyms (Excel, .xlsx, .pdf, forms, reports) to improve trigger term coverage.

Replace the generic word "operations" with concrete actions (read, write, format, transform) to raise specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ("spreadsheet and document/PDF generation") and one concrete action ("generation") via "direct Python execution", but the word "operations" is generic and the body's broader read/transform/format actions are not reflected, so coverage is not comprehensive.	3 / 5
Completeness	Has a clear "what" (direct Python execution for spreadsheet/document/PDF generation) but no explicit "Use when..." trigger clause; per the rubric a missing explicit trigger caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural terms "spreadsheet", "document", and "PDF", but misses common variations and extensions users say ("Excel", ".xlsx", ".pdf", "forms", "reports", "invoices"), leaving relevant synonyms absent.	3 / 5
Distinctiveness Conflict Risk	The "direct Python execution" qualifier adds some distinctiveness, but the domain spans spreadsheets, documents, and PDFs broadly enough to overlap with other document/spreadsheet skills.	3 / 5
	Total	12 / 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/spreadsheet-direct-python-merged-343937/SKILL.md
Commit: 3827781

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