document-direct-python

Use direct Python execution for reliable document creation including spreadsheets, PDFs, and structured reports

Quality

63%

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/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 body is highly actionable with complete executable examples and good section organization, but loses points for an off-topic padded section and the absence of validation/feedback checkpoints in its file-writing workflow.

Suggestions

Remove or relocate the 'Handling Web Research Failures' section and the hardcoded task ID reference, which are off-skill padding.

Add an explicit validation checkpoint (e.g. verify the output file opens / re-read it to confirm) and a fix-retry loop after write-and-execute steps.

Tighten the 'Why Direct Execution?' rationale to a few bullets rather than restating shell_agent failure modes at length.

Dimension	Reasoning	Score
Conciseness	The bulk is efficient actionable code, but the 'Handling Web Research Failures' section (including a hardcoded task ID 045aba2e-...) and the 'Why Direct Execution?' motivation block are unnecessary explanation that could be tightened, matching the 'mostly efficient but includes some unnecessary explanation' anchor rather than 4.	3 / 5
Actionability	Provides five complete, copy-paste-ready Python examples (Excel transforms, multi-sheet openpyxl, reportlab checklist, FPDF report, spreadsheet-to-PDF) plus an error-handling pattern and a troubleshooting table, fully executable and covering the common cases per the top anchor.	5 / 5
Workflow Clarity	A clear recommended pattern exists (write script to .py file, then execute) but there are no validation/verification checkpoints or fix-retry feedback loops for file-writing operations; per the rubric, missing validation for batch/destructive document operations caps workflow_clarity at 3.	3 / 5
Progressive Disclosure	Well-organized into clearly headed sections (When to Use, How to Use, Examples, Best Practices, Common Libraries, Troubleshooting) with no external bundle files to navigate and only minor organization gaps (the off-topic web-research subsection), matching the 'good structure; most content appropriately placed' anchor rather than 5 which requires one-level-deep reference links.	4 / 5
	Total	15 / 20 Passed

Description

57%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 clearly states the domain and primary action but omits an explicit 'Use when...' trigger clause and lacks multiple concrete actions or file-extension keywords, which cap specificity and completeness at the midpoint.

Suggestions

Add an explicit trigger clause, e.g. 'Use when generating or transforming spreadsheets, PDFs, or structured reports via Python scripts.'

Enumerate more concrete actions (e.g. extract, transform, merge, format) and include natural file extensions like .xlsx and .pdf.

Sharpen distinctiveness by framing the niche (direct run_shell execution for reliability) more prominently in the trigger phrasing.

Dimension	Reasoning	Score
Specificity	Names the domain ('document creation including spreadsheets, PDFs, and structured reports') and one concrete action ('creation'), but does not enumerate multiple specific actions like extraction, merging, or transformation, so it matches the 'domain and 1-2 concrete actions, but not comprehensive' anchor rather than 4.	3 / 5
Completeness	Has a clear 'what' (reliable document creation for spreadsheets/PDFs/reports) but no explicit 'when' / 'Use when...' trigger clause; per the rubric a missing 'Use when...' clause caps completeness at 3, and it is not the 4 anchor which requires both what and when.	3 / 5
Trigger Term Quality	Includes natural user-facing terms ('spreadsheets', 'PDFs', 'structured reports', 'document creation') with good coverage; just above the 3 anchor because it offers several natural phrases, but missing common synonyms/extensions like 'Excel', '.xlsx', or '.pdf' that would earn a 5.	4 / 5
Distinctiveness Conflict Risk	'Direct Python execution for document creation' is somewhat specific to a mechanism (direct execution) and a domain (documents), but the broad document-creation scope could overlap with other document/PDF/Excel skills, matching the 'somewhat specific but could still overlap' anchor rather than the more distinct 4.	3 / 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/spreadsheet-direct-python-merged/SKILL.md
Commit: 3827781

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