CtrlK
BlogDocsLog inGet started
Tessl Logo

stacked-chart-visualization

处理包含百分比字符串的分类占比数据,通过补全缺失维度并生成堆叠柱状图,直观展示多维度构成随时间或分类的变化趋势。

56

Quality

63%

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-visualization/stacked-chart-visualization/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 body is a well-sequenced, executable five-step recipe with a built-in validation checkpoint and clean structure. Its main weakness is consistent comment padding that restates the code rather than adding new information.

Suggestions

Trim restating comments (e.g., the '处理逻辑' block on convert_percentage and the DataFrame-construction prose) so comments only carry information the code does not already show, lifting conciseness toward 4-5.

Replace the hardcoded example data with a short, generic extraction snippet (e.g., reading a DataFrame column) so the actionability covers real input sources, reaching anchor 5.

Add a brief validate→fix→retry note around the final_check step to introduce an explicit feedback loop, which would move workflow_clarity toward 5.

DimensionReasoningScore

Conciseness

Code is mostly efficient but nearly every step carries a prose comment that restates what the code already shows (e.g., '处理逻辑:去除百分号并转换为 float'), matching anchor 3 rather than the 'minor instances' of anchor 4.

3 / 5

Actionability

Provides fully executable, copy-paste-ready Python across all five steps with the stacked 'bottom' logic spelled out, but the data-source step is a hardcoded example with a 'replace in real use' note, a minor gap keeping it below anchor 5.

4 / 5

Workflow Clarity

Five steps are clearly sequenced and Step3 includes an explicit 'final_check' validation checkpoint, fitting anchor 4; no error-recovery feedback loop is present, so it does not reach anchor 5.

4 / 5

Progressive Disclosure

A single self-contained SKILL.md with a clear H1 and five well-organized numbered steps, no nested references and no misplaced content; over 50 lines but genuinely needs no external files, fitting anchor 4 with minor structure gaps.

4 / 5

Total

15

/

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 states concrete capabilities in a specific niche but omits any explicit 'when to use' trigger guidance, capping completeness. Trigger terms are domain-accurate yet lack natural synonyms users would actually say.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g., 使用当用户需要绘制堆叠占比图、补全缺失分类维度、或可视化多维度构成变化时).

Include common synonyms and concrete artifact terms (堆叠图、占比图、.png 导出) so the description matches language users actually say.

Restate the description in third-person imperative voice and ensure both 'what' and 'when' are explicitly covered to lift completeness to 4-5.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('补全缺失维度', '生成堆叠柱状图', '展示...变化趋势'), sitting above anchor 3 but short of the comprehensive anchor 5.

4 / 5

Completeness

Provides a clear 'what' but no 'Use when...' trigger guidance, so per the judging guidelines completeness is capped at anchor 3.

3 / 5

Trigger Term Quality

Contains relevant domain terms ('百分比字符串', '分类占比', '堆叠柱状图') but misses common synonyms and natural user phrasings like '堆叠图' or '占比图', matching anchor 3.

3 / 5

Distinctiveness Conflict Risk

The missing-dimension completion plus stacked-proportion niche is mostly distinct with only minor overlap against general charting skills, fitting anchor 4.

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.