CtrlK
BlogDocsLog inGet started
Tessl Logo

categorical-comparison-analysis

对两类分类数据进行对比分析,统计数量差异与比例关系并生成可视化图表。

55

Quality

61%

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-analysis/comparison-analysis/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 content is concrete, executable, and well-structured into five sequenced steps with efficient code. Its main weakness is the absence of validation/verification checkpoints for a batch file-writing workflow, which caps workflow clarity.

Suggestions

Add validation checkpoints: verify the input file/sheets exist before processing, assert total_count > 0 before computing ratios, and confirm the output Excel/PNG files were written successfully.

Fix the Step 2 gap where `df` is referenced but never defined in the preceding snippet — load the target sheet into `df` explicitly so each step is independently runnable.

Replace placeholder values ('category_a_column', exclude_val='代码') with a brief note on how to identify the correct columns and which header placeholders to exclude, improving actionability.

DimensionReasoningScore

Conciseness

The body is mostly lean code with task-relevant Chinese comments and no padding about concepts Claude already knows; a few comments and the hardcoded exclude_val could be trimmed, so not a 5.

4 / 5

Actionability

Provides concrete, mostly copy-paste-ready pandas/matplotlib code across all five steps; minor gaps (df is undefined in Step 2, placeholder column names like 'category_a_column') keep it below 5.

4 / 5

Workflow Clarity

Five steps are clearly sequenced, but this batch/file-writing operation has no validation or verification checkpoints (e.g. confirming the file exists, checking output), capping workflow clarity at 3 per the rubric.

3 / 5

Progressive Disclosure

No bundle files exist and none are needed; the body is well-organized into five labeled steps with clear structure, fitting the 'good structure, minor gaps' anchor rather than 5 because it is not a minimal <50-line single-purpose skill.

4 / 5

Total

15

/

20

Passed

Description

55%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 clearly states what the skill does with several concrete actions, but omits any 'Use when...' trigger guidance and lacks file-extension/synonym terms. It is moderately specific but has overlap risk with the parent Excel workflow.

Suggestions

Add an explicit 'Use when...' clause naming trigger phrases (e.g. 'Use when comparing two categorical columns in an Excel file, or when the user asks for category count differences, proportions, or comparison charts').

Include natural trigger terms and file extensions such as 'Excel', '.xlsx', '分类对比', '占比', '柱状图/饼图' to broaden keyword coverage.

Sharpen distinctiveness by framing the niche more narrowly (two-category comparison with visualization) versus the general Excel parent workflow.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions — "对比分析", "统计数量差异", "比例关系", "生成可视化图表" — giving clear capability breadth; not a 5 because file reading, data cleaning, and export are omitted.

4 / 5

Completeness

Provides a clear 'what' but no 'when'/Use-when trigger clause, so completeness is capped at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Contains several relevant natural terms (对比分析, 分类数据, 可视化图表) but lacks file extensions (e.g. .xlsx) and common synonyms, matching the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The two-category comparison niche is somewhat specific, but the body references a parent Excel workflow, indicating real overlap risk with related analysis skills.

3 / 5

Total

13

/

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.

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.