CtrlK
BlogDocsLog inGet started
Tessl Logo

document-python-direct-exec

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

52

Quality

57%

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

Quality

Content

65%

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 executable, copy-paste-ready examples and good library guidance, but it is verbose, lacks an explicit validation checkpoint in its core workflow, and remains a monolithic single file rather than progressively disclosing detail into references.

Suggestions

Add an explicit validate/verify step to the main workflow (e.g., after generating a file, open/parse it back to confirm it is well-formed before reporting success).

Move the extended PDF report and FPDF examples plus the troubleshooting section into separate reference files linked from a concise Quick Start section to improve progressive disclosure and conciseness.

Trim the "Why Direct Execution?" rationale and consolidate overlapping best-practice bullets to reduce token overhead.

DimensionReasoningScore

Conciseness

The body is mostly efficient with code that earns its place, but six full worked examples plus lengthy troubleshooting and library tables make it long; the "Why Direct Execution?" rationale and some best-practice items could be trimmed without losing clarity.

2 / 3

Actionability

Examples are fully executable and copy-paste ready (pandas/openpyxl/reportlab/fpdf with concrete imports, usage calls, and named output files), and the library-choice tables give specific, actionable recommendations.

3 / 3

Workflow Clarity

The recommended write-to-file-then-execute pattern is sequenced in two clear steps, but there is no explicit validation or verify-the-output checkpoint for operations that overwrite or batch-generate files, which caps workflow clarity at 2.

2 / 3

Progressive Disclosure

The skill is a single monolithic file with all examples, troubleshooting, and library references inline; with no bundle files present, content that could be split out (extended examples, troubleshooting) keeps it from the well-signaled one-level-deep structure of a 3.

2 / 3

Total

9

/

12

Passed

Description

50%

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 clear and reasonably specific about its approach and domain, but it lacks an explicit use-when trigger and a list of concrete sub-actions, leaving all dimensions at the mid-level anchor.

Suggestions

Add an explicit "Use when..." clause naming natural trigger terms, e.g. "Use when generating Excel spreadsheets, PDF reports/checklists, or Word documents with precise layout control."

Enumerate concrete actions (e.g., "apply formulas and formatting to multi-sheet Excel files, generate PDF checklists and tabular reports") to lift specificity to 3.

Include common file-format terms users say (Excel, .xlsx, Word, .docx, reports, invoices) to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The description names a concrete approach ("direct Python execution") and a clear domain ("spreadsheet and document/PDF generation operations"), but it describes generation at a high level rather than listing multiple distinct concrete actions like extraction, filling, or merging.

2 / 3

Completeness

It answers "what" (direct Python execution for document generation) but provides no explicit "Use when..." trigger guidance, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

"spreadsheet", "document", and "PDF" are natural user terms, but common variations users would actually say (Excel, .xlsx, reports, invoices) are absent, so coverage is partial.

2 / 3

Distinctiveness Conflict Risk

The "direct Python execution" framing gives it a distinct angle, but the broad "spreadsheet and document/PDF generation" scope could still overlap with general PDF or document-generation skills.

2 / 3

Total

8

/

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.