CtrlK
BlogDocsLog inGet started
Tessl Logo

spreadsheet-source-validated

Execute Python scripts for spreadsheet operations with mandatory source data validation and fallback protocols

54

Quality

60%

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-enhanced-enhanced-2e6773/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%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 an excellent validate-then-execute workflow and strong feedback loops, but it is noticeably verbose and keeps everything inlined in one large file rather than splitting reusable code into reference files. Tightening the repeated validation examples and externalizing library code would meaningfully improve it.

Suggestions

Consolidate the near-duplicate validation functions into a single canonical example and move the full library-style implementations into a references/ file that the body points to.

Trim verbose prose (e.g. the 'Why Direct Execution?' rationale and docstrings on obvious functions) to respect the token budget and assume Claude's competence.

Fix the small executable gaps such as the missing datetime import in report_data_access_failure so all snippets are truly copy-paste ready.

DimensionReasoningScore

Conciseness

The body is noticeably verbose: multiple full Python functions with docstrings and near-duplicate validation patterns (validate_source_data, validate_spreadsheet_integrity, validate_external_source, complete workflow) repeat the same idea, exceeding what Claude needs. It is not pure padding, so it stays above 1, but several sections could be trimmed or moved to a reference file.

2 / 5

Actionability

Provides mostly executable, copy-paste-ready code and concrete shell commands ('python3 validate_sources.py || exit 1', 'cat > validate_sources.py << EOF'); minor gaps like the report_data_access_failure snippet using datetime without importing it keep it just below 5.

4 / 5

Workflow Clarity

A clear validate -> process -> report sequence with explicit checkpoints ('Only proceed when validation passes', retry limits, fallback loops) and error-recovery feedback loops, matching the 5-anchor for sequenced validation with feedback.

5 / 5

Progressive Disclosure

All content is inlined in a single ~365-line file with no bundle files present; the reusable validation library code and troubleshooting section could be split into references, so structure is present but not well separated.

3 / 5

Total

14

/

20

Passed

Description

58%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 communicates what the skill does but omits any 'Use when...' trigger guidance and lacks common user-facing synonyms and file extensions. It is specific and reasonably distinct, yet its discoverability is limited by the missing trigger clause.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when working with Excel/.xlsx files that require source data validation before processing.'

Include natural synonyms and extensions users would actually say ('spreadsheets', 'Excel', '.xlsx', 'validate data sources') to improve trigger-term coverage.

Tighten the framing so the validation/fallback niche reads as a distinct trigger rather than a general spreadsheet execution skill.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('Execute Python scripts for spreadsheet operations', 'mandatory source data validation and fallback protocols'), with only minor gaps in coverage; not as exhaustive as the 5-anchor.

4 / 5

Completeness

Clearly states the 'what' but provides no 'Use when...' trigger clause; per the judging guidelines a missing explicit 'when' caps completeness at 3.

3 / 5

Trigger Term Quality

Contains relevant keywords ('Python scripts', 'spreadsheet operations', 'source data validation') but misses common natural variations and file extensions users would say (Excel, .xlsx, spreadsheets, 'validate data'), keeping it just below the 4-anchor.

3 / 5

Distinctiveness Conflict Risk

The validation-and-fallback framing creates a fairly distinct niche with minor overlap risk against generic spreadsheet skills, but lacks the sharp trigger phrases of the 5-anchor.

4 / 5

Total

14

/

20

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.