CtrlK
BlogDocsLog inGet started
Tessl Logo

line-chart-visualization

提取结构化数据并进行特征清洗与聚类分析,生成包含趋势对比、分布特征与参数敏感性的多维度综合可视化图表,适用于各类趋势预测与多维对比场景。

60

Quality

70%

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/line-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 skill delivers lean, fully executable code organized into a clear four-step pipeline, but it omits validation checkpoints for batch operations and keeps all content inline rather than progressively disclosing it across reference files.

Suggestions

Insert explicit validation/verification checkpoints between steps (e.g., assert expected columns exist, verify row counts after loading, confirm the chart rendered before saving) to add a feedback loop for this batch operation.

Split the longer code blocks (e.g., Step4 visualization or Step3 clustering) into reference scripts under scripts/ and link to them from SKILL.md to enable progressive disclosure.

Add brief guidance on how to adapt the placeholder column names (group_col, value_col1, value_col2) to a real dataset so the executable example is unambiguous in practice.

DimensionReasoningScore

Conciseness

The body is code-forward with one-line step descriptions and short comments, and it does not pad with explanations of concepts Claude already knows (e.g., what KMeans or standardization is).

3 / 3

Actionability

Each step provides fully executable pandas/sklearn/matplotlib code with concrete file paths and copy-paste-ready blocks; the placeholder column names are explicitly flagged as examples, justifying the flexibility.

3 / 3

Workflow Clarity

Step1 through Step4 are clearly sequenced, but the batch data-processing pipeline has no validation or verification checkpoints (e.g., confirming loaded row counts or verifying output before save), which caps workflow clarity at 2.

2 / 3

Progressive Disclosure

At ~168 lines with no bundle files (references/, scripts/, assets/ absent), everything is inline in one SKILL.md; the four labeled steps provide structure but no content is split into one-level-deep references.

2 / 3

Total

10

/

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 conveys a concrete, multi-action capability but relies on implied applicability language instead of an explicit 'Use when' trigger, leaving the when/trigger guidance only partially specified.

Suggestions

Append an explicit 'Use when...' clause naming concrete user triggers (e.g., 'Use when the user asks for trend comparison, distribution analysis, or multi-dimensional chart visualization').

Add common natural keyword variations users would actually say (e.g., '折线图', '数据可视化', '趋势分析') to broaden trigger-term coverage.

Sharpen distinctiveness by naming the distinguishing feature (clustering-driven multi-panel charts) up front so it does not collide with generic plotting skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — '提取结构化数据', '特征清洗', '聚类分析', and '生成...可视化图表' — matching the anchor for enumerating several specific actions rather than vague language.

3 / 3

Completeness

The 'what' is explicit, but the 'when' is only implied via '适用于各类趋势预测与多维对比场景' rather than an explicit trigger clause, which caps completeness at 2.

2 / 3

Trigger Term Quality

Includes some natural terms a user might say ('趋势预测', '多维对比', '可视化图表') but lacks a 'Use when' trigger and omits common variations, so it does not reach full coverage.

2 / 3

Distinctiveness Conflict Risk

The clustering-plus-multi-dimensional-visualization niche is fairly specific, yet it could overlap generic charting/data-analysis skills and lacks distinct trigger phrasing to prevent conflicts.

2 / 3

Total

9

/

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.