CtrlK
BlogDocsLog inGet started
Tessl Logo

condition-filtering-and-large-file-optimization

根据数据规模动态选择处理策略。

45

Quality

48%

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

Quality

Content

87%

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

The content is strong: it provides concrete, executable Python for conditional filtering and styled Excel export in a lean, well-organized two-step structure with a signaled parent-skill reference. The main gap is the absence of validation/verification checkpoints around the export step.

DimensionReasoningScore

Conciseness

The body is code-dense with only brief inline tips (e.g. '技巧:多条件组合筛选时使用 & 符号', 'errors=\'coerce\' 处理脏数据') and does not explain concepts Claude already knows, matching the 'lean and efficient; every token earns its place' anchor (3) rather than the 'mostly efficient but could be tightened' anchor (2).

3 / 3

Actionability

Both steps provide fully executable Python with real column names, a concrete regex pattern (r'--pct-'), openpyxl styling, and a copy-paste-ready download-link print, matching the 'fully executable code; copy-paste ready' anchor (3) rather than the pseudocode/incomplete anchor (2).

3 / 3

Workflow Clarity

Step1 and Step2 give a clear sequence, but there is no validation or verification checkpoint for the Excel export/styling batch operation (e.g. confirming the file was written or that filtered rows are non-empty), which per the rubric caps workflow clarity at 2 rather than 3.

2 / 3

Progressive Disclosure

The body is organized into two well-separated step sections with a clearly signaled one-level reference to the parent workflow SKILL.md (the 'Note' block) and no nested references, matching the 'clear overview with well-signaled one-level-deep references' anchor (3).

3 / 3

Total

11

/

12

Passed

Description

10%

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 too vague and generic: it states an abstract intent ('dynamically select a processing strategy based on data scale') without naming the concrete Excel filtering/export actions the skill performs, including any user-facing trigger terms, or providing a 'Use when' clause. It is barely distinguishable from other data-handling skills.

Suggestions

Rewrite the description in third person to list concrete actions, e.g. 'Cleans and filters Excel data by column synonyms, RGB color values, prefixes, and regex patterns, then exports styled results.'

Add an explicit trigger clause such as 'Use when the user needs conditional filtering, multi-criteria Excel cleaning, or large-file optimization on spreadsheets.'

Include natural keywords users would actually say (Excel/筛选/条件筛选/导出/large file) so the skill triggers on real requests instead of the generic '数据规模/处理策略'.

DimensionReasoningScore

Specificity

The phrase '根据数据规模动态选择处理策略' names a domain (data scale) and a single abstract action (selecting a processing strategy), but lists no concrete operations such as filtering, regex extraction, or Excel export, so it does not reach the 'multiple specific concrete actions' anchor (3) yet rises above pure vagueness (1).

2 / 3

Completeness

It offers a weak, abstract 'what' ('选择处理策略') and entirely omits any 'when'/'Use when' trigger guidance; since both the what and the when are weak or missing, it fits the 'Missing what OR when, or both very weak' anchor (1), not the 'has what but when implied' anchor (2).

1 / 3

Trigger Term Quality

The description contains only generic terms ('数据规模', '处理策略') and no natural keywords a user would actually say (e.g. Excel, 筛选, 条件, 导出, large file), matching the 'no natural keywords; overly generic' anchor rather than the 'some relevant keywords' anchor (2).

1 / 3

Distinctiveness Conflict Risk

'根据数据规模动态选择处理策略' is so generic it would plausibly trigger for many unrelated data-processing skills, matching the 'very generic; would conflict with many skills' anchor (1) rather than the somewhat-specific anchor (2).

1 / 3

Total

5

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

description_field

'description' is very short (15 chars), consider making it more detailed

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

14

/

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.