CtrlK
BlogDocsLog inGet started
Tessl Logo

invalid-data-cleaning

用于大规模Excel数据的预处理,通过统计总行数判断是否转换为Parquet格式以提升读写效率,并使用正则表达式清洗指定文本列(如仅保留中文字符),最后导出清洗后的文件并提供下载链接。

56

Quality

63%

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 ./skills/sn-da-excel-workflow/capability/excel-data-cleaning/invalid-data-cleaning/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 provides mostly executable, reasonably concise code for each step in a clear sequence, but it lacks validation/verification checkpoints for a batch data operation, which caps workflow clarity.

Suggestions

Add validation checkpoints after conversion and cleaning (e.g., verify row counts before/after Parquet conversion, assert the cleaned column is non-empty) and a retry-on-failure loop.

Define the row-count threshold for '数据量过大' so the Parquet-conversion branch is unambiguous instead of left to inference.

Replace the 'target_column' placeholder with guidance on detecting or accepting the target column, and consolidate the repeated pandas imports across steps.

DimensionReasoningScore

Conciseness

Code blocks are tight with brief inline comments and no padding about pandas/regex basics, though repeated imports and a few comments that restate the step title keep it just below a 5.

4 / 5

Actionability

Each step ships concrete, executable pandas/regex code that is largely copy-paste ready, but placeholders like 'target_column' and an undefined row-count threshold leave minor gaps.

4 / 5

Workflow Clarity

Three steps are clearly sequenced (convert -> clean -> export), but this batch file-writing operation has no validation or verification checkpoints, which caps workflow clarity at 3 per the rubric.

3 / 5

Progressive Disclosure

As a short single-purpose skill with no bundle files, the well-organized header, parent-workflow pointer, and three labeled steps satisfy the simple-skill exception for a top score.

5 / 5

Total

16

/

20

Passed

Description

55%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 what the skill does with several concrete actions, but lacks an explicit 'when to use' trigger and has only partial keyword coverage, leaving it in the mid-range on completeness and trigger quality.

Suggestions

Add an explicit 'Use when...' trigger clause naming the natural phrases users would say (e.g., data cleaning, text-column normalization, large Excel preprocessing).

Broaden keyword coverage with synonyms and the .xlsx file extension so the description matches more natural user requests.

Sharpen distinctiveness by stating the specific large-scale condition (row-count threshold) that uniquely triggers Parquet conversion.

DimensionReasoningScore

Specificity

Names the domain (Excel data preprocessing) and several concrete actions — Parquet conversion by row count, regex text-column cleaning, and export with download link; minor coverage gaps keep it just below 5.

4 / 5

Completeness

The 'what' is clearly stated, but there is no explicit 'Use when...' trigger clause, so 'when' is only weakly implied; per the rubric a missing explicit trigger caps completeness at 3.

3 / 5

Trigger Term Quality

Contains relevant keywords ('Excel数据', 'Parquet格式', '正则表达式清洗', '中文字符') but misses common synonyms ('数据清洗', '数据预处理') and the .xlsx extension, so keyword coverage is partial rather than comprehensive.

3 / 5

Distinctiveness Conflict Risk

The Parquet-conversion-plus-Chinese-regex niche is somewhat specific, but it could still overlap with generic Excel/data-cleaning skills and lacks a narrow distinguishing trigger.

3 / 5

Total

13

/

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
OpenSenseNova/SenseNova-Skills
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.