CtrlK
BlogDocsLog inGet started
Tessl Logo

large-file-parquet-analysis-and-highlight

当Excel文件总行数超过1万行时,通过转换为Parquet格式提升读取性能,提取目标指标并计算最大值,最后将结果输出为Excel并对特定行进行高亮标注。

54

Quality

60%

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/category-coloring/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 content provides mostly executable, well-sequenced code with end-of-workflow validation, but the core Parquet conversion step is assumed rather than shown and placeholders undermine actionability.

Suggestions

Replace the assumed conversion with an explicit Excel→Parquet code step (e.g., pd.read_excel then df.to_parquet) so the workflow is self-contained.

Replace the '目标指标名称' placeholder with concrete guidance on how to identify the target metric row, or parameterize it clearly.

Remove the fallback dummy 'result_data' block or move it to a clearly labeled standalone example to avoid mixing real and illustrative data.

DimensionReasoningScore

Conciseness

The body is mostly executable code with brief step introductions and no over-explanation of concepts Claude already knows; only minor padding (the fallback dummy 'result_data' block) could be trimmed.

4 / 5

Actionability

Real, executable Python is provided, but the headline Excel→Parquet conversion is only assumed ('假设已通过大文件处理技能将Excel转换为Parquet') and placeholders like '目标指标名称' leave key details missing.

3 / 5

Workflow Clarity

Three steps are clearly sequenced and Step3 includes output verification, but the Excel→Parquet conversion between Step1 and Step2 is absent, breaking the sequence with an implicit checkpoint.

3 / 5

Progressive Disclosure

No bundle files are present or needed; the single-file skill is organized into three clearly headed step sections with good navigation, satisfying the simple-skill exception with only minor organization gaps.

4 / 5

Total

14

/

20

Passed

Description

58%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 conveys a concrete multi-step pipeline with a specific trigger condition, but it lacks an explicit 'Use when...' invocation clause and natural-term synonyms, which limits trigger quality and completeness.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when an Excel file exceeds 10,000 rows and you need fast metric extraction with highlighted output') to raise completeness.

Include natural synonyms and the file extension (e.g., 'Excel', '.xlsx', 'large spreadsheet', 'big Excel file') to improve trigger-term coverage.

Restructure the action list so capabilities read as a discrete enumeration rather than one run-on sentence, making specificity clearer.

DimensionReasoningScore

Specificity

Lists several concrete actions — '转换为Parquet格式', '提取目标指标并计算最大值', '输出为Excel', '对特定行进行高亮标注' — but is a single procedural sentence rather than a comprehensive capability list, leaving minor gaps.

4 / 5

Completeness

The 'what' is clear, and '当Excel文件总行数超过1万行时' states a trigger condition, but there is no 'Use when...' clause explicitly directing Claude when to invoke the skill, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Contains relevant terms ('Excel文件', 'Parquet', '1万行', '高亮', '最大值') but misses common variations and the .xlsx extension, so keyword coverage is only partial.

3 / 5

Distinctiveness Conflict Risk

The combination of large-Excel handling, Parquet conversion, and row highlighting is a fairly distinct niche with only minor overlap risk against general Excel skills.

4 / 5

Total

14

/

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.