CtrlK
BlogDocsLog inGet started
Tessl Logo

pie-chart-data-analysis

对多Sheet Excel或CSV数据进行分类汇总统计,自动识别关键字段并生成包含占比、数值及美化饼图的可下载分析报告。

63

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/sn-da-excel-workflow/capability/excel-data-visualization/pie-chart-visualization/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%

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

The content is executable and token-efficient, giving Claude concrete code to run end-to-end. Its gaps are the missing validation/verification checkpoints in the pipeline and the lack of progressive disclosure through bundled files.

Suggestions

Add an explicit validation/checkpoint between aggregation and report generation, e.g. assert total_val > 0 and verify summary_df is non-empty before charting, with a fix-and-retry loop.

Define or guard input_file (e.g. accept it as a parameter and validate the path exists) so the code is self-contained and runnable.

Move the longer code blocks into scripts/ with the steps in SKILL.md calling them, and reference those scripts to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is lean and code-forward with one-line step intros and brief inline comments, assuming Claude's competence and avoiding concept explanations.

3 / 3

Actionability

All four steps provide complete, executable Python (pandas, matplotlib, openpyxl) that is essentially copy-paste ready, with only the minor assumption that input_file is in scope.

3 / 3

Workflow Clarity

Steps are clearly sequenced (Step1–Step4) but there are no validation checkpoints or feedback loops for the batch data pipeline, and only an implicit try/except in Step1.

2 / 3

Progressive Disclosure

The ~130-line body is a single monolithic file with all code inline and no references or navigation; the four code blocks could be split into bundled scripts for better organization.

2 / 3

Total

10

/

12

Passed

Description

67%

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 distinguishable, clearly stating what the skill produces. Its main weakness is the complete absence of explicit trigger/usage guidance, which caps completeness and trigger-term quality.

Suggestions

Append an explicit 'Use when...' clause, e.g. 'Use when the user asks for Excel/CSV分类汇总、占比分析, or wants a 饼图分析报告.'

Add common trigger variations like '数据汇总', '分类统计', '占比饼图', 'Excel多Sheet统计' to broaden natural-term coverage.

Keep the concise third-person action phrasing while adding the when-guidance; avoid padding the existing capability list.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 分类汇总统计, 自动识别关键字段, and 生成包含占比、数值及美化饼图的可下载分析报告 — rather than vague language.

3 / 3

Completeness

It clearly answers 'what does this do' but provides no 'when should Claude use it' guidance, so per the judging guidelines completeness is capped at 2.

2 / 3

Trigger Term Quality

It contains some natural terms users might say (Excel, CSV, Sheet, 饼图, 分析报告) but misses common variations and lacks any 'Use when...' trigger phrasing.

2 / 3

Distinctiveness Conflict Risk

The niche — multi-sheet Excel/CSV categorical aggregation producing a pie-chart report — is specific with distinct triggers, making conflict with other skills unlikely.

3 / 3

Total

10

/

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.