CtrlK
BlogDocsLog inGet started
Tessl Logo

excel-threshold-analysis-and-styling

根据 Excel 数据量级自动判断处理策略,执行数值列清洗、条件过滤,并使用 openpyxl 对符合条件的单元格进行样式标记与导出。

52

Quality

58%

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-filtering/threshold-filtering/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 first three steps are concrete and runnable, but the skill is truncated before its key openpyxl-styling step and contains no validation checkpoints for its batch/destructive operations. Structure is minimal and would benefit from proper headers.

Suggestions

Complete Step 4: the openpyxl styling/export code is missing and the section ends mid-sentence ('对原始文件中'), so the skill never delivers its stated core purpose.

Add validation checkpoints (e.g. verify cleaned-row count, confirm filter result count, assert the exported .xlsx opens) — this is a batch/destructive workflow and currently lacks any verification loop.

Replace plain 'Step1/Step2' labels with proper markdown headers (##) and add a brief summary/overview so the single-file structure is easier to navigate.

DimensionReasoningScore

Conciseness

Mostly efficient, but the Chinese prose before each code block restates what the code does (e.g. "强制转换数值类型,无法转换的内容变为 NaN 并删除") and several inline comments duplicate the code's intent.

3 / 5

Actionability

Steps 1–3 provide complete, executable pandas code, but Step 4 — the openpyxl styling/export that is the skill's core deliverable — is truncated mid-sentence with no code at all, leaving key details missing.

3 / 5

Workflow Clarity

A Step1–Step4 sequence is present, but there are no validation checkpoints and Step 4 is cut off; the rubric caps workflow_clarity at 3 for batch/destructive operations lacking validation, and this cap applies.

3 / 5

Progressive Disclosure

The skill is a single ~50-line file with step numbering, but it uses plain 'Step1/Step2' labels instead of markdown headers, has no clear section structure, and the one reference (to a 'parent workflow SKILL.md') is not a discoverable local file.

3 / 5

Total

12

/

20

Passed

Description

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

A specific, well-scoped description that clearly states what the skill does, but it lacks an explicit 'when to use it' trigger clause and a few natural synonyms/file extensions. Adding a Use-when clause would lift its weakest dimension.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when the user needs to clean numeric Excel columns, filter records by a threshold, and export a styled .xlsx file.'

Include the '.xlsx' file extension and a synonym like 'spreadsheet/表格' so the description matches more natural user phrasings.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "数值列清洗", "条件过滤", "样式标记", "导出", plus magnitude-based strategy selection — giving strong specific coverage with only minor gaps.

4 / 5

Completeness

The 'what' is clearly stated but there is no 'Use when...' clause or equivalent trigger guidance, so per the rubric completeness is capped at 3.

3 / 5

Trigger Term Quality

It includes natural terms like "Excel", "openpyxl", "条件过滤", and "单元格", but omits common synonyms ("表格"/spreadsheet) and the ".xlsx" file extension that anchor 5 requires.

4 / 5

Distinctiveness Conflict Risk

The threshold-judgment plus openpyxl-styling niche is mostly distinct, with only minor overlap risk against generic Excel-handling skills.

4 / 5

Total

15

/

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.