document-python-direct

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

Quality

59%

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

Quality

Content

68%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 complete executable examples and good structure, but it is somewhat verbose from repeated boilerplate and lacks validation checkpoints for its destructive batch file-generation workflow.

Suggestions

Add an explicit validation checkpoint after generation (e.g., verify the output file opens, check row counts, or re-open the workbook/PDF to confirm integrity) to lift workflow clarity above the destructive/batch cap of 3.

De-duplicate the 'Write to file first, then execute:' lead-in and consolidate the overlapping 'When to Use This Skill' and 'Why Direct Execution?' sections to reduce token cost.

Consider moving the full per-library examples and the troubleshooting catalog into reference files (e.g., examples.md, troubleshooting.md) referenced one level deep from SKILL.md.

Dimension	Reasoning	Score
Conciseness	The body mostly assumes Claude knows the libraries and avoids concept padding, but the repeated 'Write to file first, then execute' lead-in across six examples and the overlapping 'When to Use'/'Why Direct Execution' sections are unnecessary bulk that could be tightened.	3 / 5
Actionability	Six complete, copy-paste-ready Python code blocks (pandas, openpyxl formatting, reportlab, fpdf2, combined workflow, try/except) plus concrete bash patterns cover the common document and spreadsheet generation cases.	5 / 5
Workflow Clarity	A clear write-to-file-then-execute sequence is present with an error-handling pattern, but the skill performs batch/destructive file generation (overwriting output.xlsx, report.pdf) with no validation checkpoint or verify step, capping workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	Content is well-organized with clear section headers and no nested references, and no bundle files exist; the long inline examples and troubleshooting bulk could arguably be split into reference files, but navigation is already good.	4 / 5
	Total	15 / 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 conveys a clear method and domain but lacks explicit "when to use" trigger guidance and relies on generic "operations" language. Trigger terms are relevant but miss common synonyms and file extensions.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers, e.g., 'Use when generating PDF reports, Excel spreadsheets, or formatted documents, or when the user mentions PDFs, .xlsx files, or report generation.'

Replace the generic word 'operations' with several specific actions (e.g., 'read and transform Excel data, apply formatting, generate PDF reports and checklists').

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

Dimension	Reasoning	Score
Specificity	It names the domain ("spreadsheet and document/PDF generation") and a concrete method ("direct Python execution"), but the actual operations are described generically as "operations" rather than listing several specific actions, so coverage is not comprehensive.	3 / 5
Completeness	The "what" is reasonably clear (direct Python execution for spreadsheet/document/PDF generation), but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Natural terms like "spreadsheet", "document", and "PDF" appear, but common variations and extensions users would say (Excel, .xlsx, PDFs, reports, forms) are missing.	3 / 5
Distinctiveness Conflict Risk	The "direct Python execution" framing adds some distinctiveness, but "spreadsheet and document/PDF generation" broadly overlaps with related document, spreadsheet, and PDF 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-f07ee1/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.