CtrlK
BlogDocsLog inGet started
Tessl Logo

large-file-conditional-formatting

根据Excel总行数自动切换Parquet加速读取,计算特定维度的时间序列平均值,并使用openpyxl输出带有条件格式(如低于均值标绿)和自定义样式的分析报告。

60

Quality

70%

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-cell-coloring/threshold-cell-coloring/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 skill provides concrete, executable code across a clear three-step sequence but lacks validation checkpoints and has a variable-continuity gap between Step1 and Step2. Structure is reasonably well organized for a single-file sub-skill.

Suggestions

Add validation/verification checkpoints, e.g., assert the output file exists or handle empty target rows, to lift workflow clarity above 3.

Fix the data-flow gap: Step2 uses `df` but Step1 only assigns `df_temp`; explicitly carry the relevant DataFrame forward or reload it.

Remove a few redundant inline code comments (e.g., '# 计算平均值') to tighten conciseness.

DimensionReasoningScore

Conciseness

The body is mostly executable code with brief step introductions and avoids explaining concepts Claude already knows, though a few inline comments like '# 计算平均值' and '# 定义样式' could be trimmed.

4 / 5

Actionability

Three complete, mostly copy-paste-ready Python blocks cover the task, but Step2 references an undefined `df` (Step1 only defines `df_temp`) and uses a placeholder target entity, leaving minor gaps.

4 / 5

Workflow Clarity

Step1→Step2→Step3 are clearly sequenced, but there are no validation or verification checkpoints (e.g., confirming the output file or checking for empty data), which caps this dimension.

3 / 5

Progressive Disclosure

Content is organized into a Skill Steps section with three labeled steps and a clear note pointing to the parent workflow; no bundle files exist, and the inline structure is appropriate with only minor organization gaps.

4 / 5

Total

15

/

20

Passed

Description

71%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 concrete with strong keyword coverage, but lacks an explicit 'Use when' trigger clause, which limits its completeness. Distinctiveness is good thanks to the Parquet-acceleration niche.

Suggestions

Add an explicit 'Use when...' clause naming the trigger situations (e.g., large Excel files, conditional formatting reports, time-series averages).

Include common synonyms/file extensions such as .xlsx, spreadsheets, or 'large Excel files' to broaden natural trigger terms.

Clarify the threshold logic for 'large file' so the trigger is more distinguishable from generic Excel skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions—'自动切换Parquet加速读取', '计算特定维度的时间序列平均值', and '输出带有条件格式...和自定义样式的分析报告'—with comprehensive, specific coverage.

5 / 5

Completeness

The 'what' is clearly stated across three actions, but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Good keyword coverage including Excel, Parquet, openpyxl, 条件格式, 时间序列, and 均值, but missing common synonyms and file extensions like .xlsx or spreadsheets that users would naturally say.

4 / 5

Distinctiveness Conflict Risk

The combination of row-count-based Parquet switching plus conditional-formatted openpyxl reports is a fairly distinct niche, though it retains minor overlap risk with general Excel analysis skills.

4 / 5

Total

16

/

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.

Validation — 16 / 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.