CtrlK
BlogDocsLog inGet started
Tessl Logo

text-normalization-and-large-file-processing

对Excel文件进行文本标准化清洗(如去除异常前缀、提取纯中文字符等),并,最终输出清洗后的Excel文件并提供下载链接。

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/text-normalization/SKILL.md
SKILL.md
Quality
Evals
Security

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 concise and actionable with concrete executable code, but lacks a validation/verification checkpoint for the batch cleaning operation, capping workflow clarity at 3.

Suggestions

Add an explicit validation step after cleaning (e.g., check that '_清洗后' columns exist, report rows converted to NaN, and verify the output file opens) before declaring the workflow complete.

Show the missing imports (`import pandas as pd`, `import gc`) or note that `df`/`pd`/`gc` are provided by the parent workflow so the snippets are self-contained.

Add a brief verification command after saving (e.g., reload and print row count) to confirm the output Excel file is valid before providing the download link.

DimensionReasoningScore

Conciseness

The body is lean: brief step descriptions plus directly usable code, with no padding or explanations of concepts Claude already knows; only minor prose could be trimmed.

4 / 5

Actionability

Both steps provide concrete, mostly executable Python code; minor gaps are the assumed `df`/`pd`/`gc` (pandas and gc not imported in the shown snippets) rather than pseudocode.

4 / 5

Workflow Clarity

Two steps are clearly sequenced and memory cleanup is included, but there is no validation/verification step for a batch data-cleaning operation that overwrites source values, which caps workflow clarity at 3 per the rubric.

3 / 5

Progressive Disclosure

The short body is well-organized into two steps with a clearly signaled one-level reference to the parent workflow SKILL.md; no bundle files exist to verify, so structure is good with only minor organization gaps.

4 / 5

Total

15

/

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 is specific and actionable about what it does, but omits any explicit 'Use when...' trigger guidance and lacks synonyms/file extensions, capping completeness and trigger-term quality at 3.

Suggestions

Add an explicit 'Use when...' clause listing concrete trigger phrases (e.g., 'Use when the user asks to clean Excel text, remove abnormal prefixes, extract Chinese characters, or needs a cleaned .xlsx download').

Include the .xlsx file extension and synonyms like '清洗/cleaning' and 'standardization' to broaden natural trigger coverage.

Fix the awkward '并,' punctuation in the description to improve readability.

DimensionReasoningScore

Specificity

The description lists several concrete actions ('文本标准化清洗', '去除异常前缀', '提取纯中文字符', '输出清洗后的Excel文件', '提供下载链接'), giving good coverage with only the '等' ellipsis leaving minor gaps.

4 / 5

Completeness

It clearly states the 'what' (cleaning and outputting Excel) but provides no explicit 'when' / 'Use when...' trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Relevant terms like 'Excel文件', '文本标准化清洗', '中文字符', and '下载链接' are present, but it lacks common synonyms and the .xlsx file extension, and there is no natural 'Use when...' phrasing.

3 / 5

Distinctiveness Conflict Risk

The niche (Excel text normalization with prefix cleaning and Chinese-character extraction) is fairly specific and distinct, with only minor overlap risk against other Excel-handling skills.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

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.