CtrlK
BlogDocsLog inGet started
Tessl Logo

excel-conditional-filtering-optimization

根据多维数值条件筛选 Excel 数据并导出结果,支持大规模数据的自动性能优化处理。

48

Quality

50%

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

Quality

Content

50%

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

The body delivers a clear, mostly executable four-step Excel filtering workflow with concise commentary. It is held back by placeholder-laden cleaning code, hardcoded example values, and an absence of validation checkpoints around the export step.

Suggestions

Replace the commented-out placeholder cleaning code in Step 2 with concrete, active logic or move optional variants into a clearly labeled 'adjust as needed' note.

Add a validation checkpoint before export (e.g. assert filtered result is non-empty, verify output file exists after to_excel) to satisfy the workflow-clarity feedback-loop expectation for write operations.

Parameterize hardcoded values (file_path, target_sheet, numeric column names) or provide a short config block so the examples are directly runnable.

DimensionReasoningScore

Conciseness

Instructions are lean and avoid explaining concepts Claude already knows, but commented-out placeholder lines (e.g. '# df.columns = [\'col_1\'...]') add noise; matches 'mostly efficient but could be tightened', not 3 because of the placeholder clutter.

2 / 3

Actionability

Steps 1, 3, and 4 provide executable pandas code, but Step 2 leaves key handling as commented placeholders ('调整占位符') and values are hardcoded, so it is not copy-paste ready; matches 'some concrete guidance but incomplete'.

2 / 3

Workflow Clarity

Step1–Step4 are clearly sequenced, but there are no validation checkpoints before or after the export write, and the scoring notes cap workflow clarity at 2 for batch/write operations lacking validation.

2 / 3

Progressive Disclosure

The ~74-line single-file body is well-sectioned into steps with a signaled parent-workflow note, but everything is inline with no progressive disclosure structure; it exceeds the under-50-line simple-skill threshold, matching 'some structure but content that could be separate is inline'.

2 / 3

Total

8

/

12

Passed

Description

50%

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 conveys the skill's purpose (filtering and exporting Excel data) with a couple of concrete actions, but relies on a vague optimization buzzword and omits any 'Use when' trigger guidance. It is adequate but not exemplary.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when the user asks to filter Excel rows by multiple numeric conditions or export filtered spreadsheet results.'

Replace the vague '自动性能优化处理' with a concrete capability such as 'chunked reading for large .xlsx files' so the action is specific rather than buzzwordy.

Include common trigger term variations (.xlsx, spreadsheet, 条件筛选) to improve trigger-term coverage and distinctiveness.

DimensionReasoningScore

Specificity

Names concrete actions ('筛选 Excel 数据', '导出结果') but pads them with the vague buzzword '自动性能优化处理'; closest to the 'names domain and some actions but not comprehensive' anchor, not 3 because the third action is fluff and not 1 because two real actions are stated.

2 / 3

Completeness

Clearly states what the skill does but has no 'Use when...' or equivalent explicit trigger clause, so per the judging guidelines completeness is capped at 2.

2 / 3

Trigger Term Quality

Includes natural terms a user would say ('Excel 数据', '筛选', '导出') but misses common variations like .xlsx, spreadsheet, or 条件格式; matches 'some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

Excel conditional filtering is a recognizable niche but overlaps with general Excel skills and lacks a distinct trigger, matching 'somewhat specific but could still overlap with similar skills'.

2 / 3

Total

8

/

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.