CtrlK
BlogDocsLog inGet started
Tessl Logo

dynamic-percentage-and-large-file-analysis

根据文件行数动态切换大文件处理策略(Parquet转换),通过逐行扫描或列匹配提取关键指标并计算占比、均值等统计量,最终输出结构化Excel报告及可视化图表。

50

Quality

55%

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-statistics/percentage-calculation/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 skill provides concrete, mostly-executable Python for a three-step percentage-analysis workflow, but it lacks validation checkpoints, leaves placeholder literals unresolved, and signals its only cross-reference vaguely. Adding verification steps and resolving the dynamic placeholders would materially improve it.

Suggestions

Add validation/feedback steps — e.g. verify key_values were found before computing, and confirm the .xlsx/.png files exist after writing — to satisfy the workflow-clarity checkpoint requirement.

Resolve the 'target_value_col' placeholder dynamically (as target_col is) or document it explicitly, and clarify which literals are user-configurable versus dynamic.

Tighten code comments that restate the following logic, and give the parent-workflow reference an explicit path or section anchor so navigation is clearly signaled.

DimensionReasoningScore

Conciseness

The body is mostly efficient executable code, but several comments restate the immediately-following logic (e.g. '# 计算占比' before the percentage calc, '# 条件筛选与统计') and could be tightened, matching the 'mostly efficient but includes some unnecessary explanation' anchor rather than the lean level-3 anchor.

2 / 3

Actionability

Concrete pandas/matplotlib APIs are provided, but unfilled placeholders ('指标A'/'指标B'/'特定类别' and a static 'target_value_col' that is never dynamically resolved) leave key details missing, so it is not fully copy-paste ready at level 3.

2 / 3

Workflow Clarity

Step1→Step2→Step3 are clearly sequenced (extract/compute, save Excel, generate chart), but there are no validation checkpoints or feedback loops for the file-writing/batch steps, which caps workflow clarity at 2 per the guidelines.

2 / 3

Progressive Disclosure

Content is organized as inline steps, but the only reference ('see the parent workflow SKILL.md') is not clearly signaled with a path and no bundle files exist, matching the 'some structure but references not clearly signaled' anchor.

2 / 3

Total

8

/

12

Passed

Description

60%

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 action-rich, clearly conveying what the skill does, but it omits any explicit 'when to use' trigger guidance and leans on technical jargon over natural user keywords. Adding a 'Use when…' clause with user-facing trigger terms would raise both completeness and trigger-term quality.

Suggestions

Append a 'Use when…' clause with natural triggers, e.g. 'Use when the user asks for percentage/占比 analysis of large Excel files, dynamic big-file processing, or Excel report + chart generation.'

Soften technical jargon by adding user-facing terms alongside Parquet/row-count language (e.g. 'large spreadsheets', '占比统计', '大表格').

Sharpen distinctiveness by framing the niche more narrowly (large-file percentage/statistics analysis) to reduce overlap with generic Excel skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — dynamically switching large-file strategies (Parquet conversion), line-by-line scanning or column matching to extract metrics, computing proportions/averages, and outputting Excel reports plus visualization charts — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

The 'what' is thoroughly answered but there is no 'Use when…' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2 rather than 3.

2 / 3

Trigger Term Quality

Mixes technical jargon ('Parquet转换', '文件行数', '逐行扫描') with a few natural terms ('Excel报告', '占比', '可视化图表'); coverage of user-natural keywords is partial and missing common variations, so it is not at the level-3 'good coverage' anchor.

2 / 3

Distinctiveness Conflict Risk

The large-file/Parquet/percentage-analysis niche is somewhat specific, but the Excel-report and visualization-chart framing overlaps with general data-analysis skills and there are no distinct triggers to prevent conflict, matching the 'somewhat specific but could still overlap' anchor.

2 / 3

Total

9

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 missing

Warning

Total

15

/

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.