CtrlK
BlogDocsLog inGet started
Tessl Logo

trend-analysis

基于多维度数据进行分级评估与趋势预测,通过设定差异化增长率计算预测值,并生成对比可视化图表,适用于绩效评估、目标设定等场景。

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

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/trend-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

87%

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

The content is a lean, fully-executable four-step Python workflow with strong actionability and clean organization, but it lacks explicit validation/verification checkpoints for its batch computations.

Suggestions

Add a verification checkpoint after data loading (e.g., assert expected columns exist, check for empty groups) and a guard before forecasting to raise workflow clarity.

Add a brief one-line overview or '## Quick start' header before Step1 so the workflow's purpose is visible without reading all the code.

DimensionReasoningScore

Conciseness

The body is code-forward with minimal prose and purposeful comments ('前30%为高', font setup); it assumes Claude knows pandas/matplotlib and avoids explaining basic concepts, matching the score-3 'lean and efficient' anchor rather than the padded score-2 example.

3 / 3

Actionability

Each step is fully executable Python (groupby, forecasting, barh plotting), not pseudocode; placeholders like 'your_data.xlsx' and '分组列名' are intentionally parameterized with examples, matching the score-3 'fully executable, copy-paste ready' anchor.

3 / 3

Workflow Clarity

Step1–Step4 are clearly sequenced, but there are no explicit validation/verification checkpoints for the batch groupby/forecasting operations, which per the scoring notes caps workflow_clarity at 2; not 1 because the sequence is clear.

2 / 3

Progressive Disclosure

This is a simple, single-purpose skill with no need for external references; the four well-labeled sequential steps are appropriately organized inline, qualifying under the simple-skills exception at score 3 rather than the score-2 'could be better organized' anchor.

3 / 3

Total

11

/

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 states concrete capabilities clearly but provides only a weak, applicability-style trigger clause with vague scope, leaving 'when to use it' only implied and risking overlap with general analysis skills.

Suggestions

Add an explicit 'Use when the user mentions performance evaluation, goal setting, or trend forecasting…' trigger clause to raise completeness and trigger quality.

Broaden trigger terms with common variations (e.g., 数据预测, 业绩评估, 增长率预测) instead of the vague '等场景'.

Sharpen distinctiveness by naming the unique method (差异化增长率分级预测) so it is less likely to fire for generic data-analysis or charting requests.

DimensionReasoningScore

Specificity

Quotes '分级评估与趋势预测', '设定差异化增长率计算预测值', '生成对比可视化图表' — multiple specific concrete actions listed, matching the score-3 anchor rather than the score-2 'some actions' anchor.

3 / 3

Completeness

'What' is clearly stated, but 'when' is only an applicability clause ('适用于绩效评估、目标设定等场景') with a vague '等' rather than an explicit 'Use when…' trigger, which per the guidelines caps completeness at 2; not 1 because the when-context is present.

2 / 3

Trigger Term Quality

Includes relevant terms ('绩效评估', '目标设定', '趋势预测') but leans technical ('差异化增长率', '分级评估') and the trigger clause is narrow, so it sits at the score-2 'some relevant keywords, missing common variations' anchor rather than score-3 broad coverage.

2 / 3

Distinctiveness Conflict Risk

The tiered growth-rate forecasting niche is somewhat specific, but triggers ('绩效评估', '目标设定') could overlap with generic data-analysis/visualization skills, matching the score-2 'somewhat specific but could still overlap' anchor.

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.