CtrlK
BlogDocsLog inGet started
Tessl Logo

excel-large-file-processing-and-cleaning

读取多 sheet Excel 文件,动态识别目标列进行统计,并使用正则清洗文本字段提取中文字符,最终输出标准化 Excel 文件。

58

Quality

66%

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-reading/structured-header-reading/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise and well-organized into three executable steps, but the code is not fully copy-paste ready (placeholders and undefined variables) and the workflow lacks validation checkpoints for its batch/output operations.

Suggestions

Replace placeholders and undefined variables (target_sheet, os, df) with concrete setup or clearly marked substitution so the code is copy-paste executable.

Add a validation/checkpoint step between processing and output (e.g., verify the cleaned column is non-empty and confirm the target column matched before writing the file).

Include the missing imports (os, pandas as pd) and a minimal df/sheet-loading preamble so each step runs standalone.

DimensionReasoningScore

Conciseness

Lean code blocks with a one-line scoping note and brief inline comments; no padding or explanation of concepts Claude already knows, so every token earns its place.

3 / 3

Actionability

Real Python is provided, but it includes placeholders ('目标清洗列' 占位示例) and undefined references (target_sheet, os, df), so it is not copy-paste executable without missing setup context.

2 / 3

Workflow Clarity

Three steps are clearly sequenced (Step1/Step2/Step3), but there are no validation checkpoints for the batch statistics and file-write operations, which per the guidelines caps workflow clarity at 2.

2 / 3

Progressive Disclosure

A compact, single-purpose skill under 50 lines organized into well-separated Step1/Step2/Step3 sections with no need for external references, satisfying the simple-skill exception for a score of 3.

3 / 3

Total

10

/

12

Passed

Description

60%

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 concretely describes several actions but omits any 'Use when' trigger guidance, capping completeness and weakening distinctiveness. Trigger terms are domain-relevant but lack natural-language and English variation coverage.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill (e.g., 'Use when cleaning or analyzing multi-sheet Excel files, extracting Chinese text, or counting column values').

Broaden trigger-term coverage with common variations users would actually say: 'Excel files, .xlsx, spreadsheets, 数据清洗, 统计列值'.

Reframe in third person with explicit trigger phrasing to better distinguish it from the parent Excel workflow and sibling sub-skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — '读取多 sheet Excel 文件', '动态识别目标列进行统计', '使用正则清洗文本字段提取中文字符', '输出标准化 Excel 文件' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Clearly states what the skill does, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Contains relevant domain keywords (Excel 文件, 统计, 清洗, 中文字符, 正则) but lacks common variations (xlsx, spreadsheets, .xlsx) and is not framed as natural user trigger phrasing.

2 / 3

Distinctiveness Conflict Risk

Describes a specific niche (column statistics plus Chinese-character text cleaning), but as a sub-skill of a broader Excel workflow it could overlap with sibling skills and has no explicit distinguishing triggers.

2 / 3

Total

9

/

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
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.