CtrlK
BlogDocsLog inGet started
Tessl Logo

time-series-and-categorical-analysis

对时间序列或分类数据进行多维度趋势分析、百分比清洗、绩效分级建模与预测,并生成高分辨率的可视化综合报告,适用于业务指标监控与预测场景。

65

Quality

77%

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/time-series-analysis/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 is concise and highly actionable with executable code and a clear step sequence, but it lacks validation checkpoints and keeps all content inline with no progressive disclosure.

Suggestions

Add explicit validation/verification steps — e.g., assert expected columns exist after loading, check for NaNs after percentage conversion, and confirm the PNG was written before reporting.

Split the long inline report-generation and visualization code into a referenced script (e.g. scripts/generate_report.py) and keep SKILL.md as an overview that points to it.

DimensionReasoningScore

Conciseness

The body is lean — one-line step descriptions plus executable code with only purposeful comments, no padding or explanation of concepts Claude already knows.

3 / 3

Actionability

Each step provides fully executable Python (pandas/numpy/matplotlib/seaborn) that is copy-paste ready; placeholder column names are explicitly flagged as 占位示例.

3 / 3

Workflow Clarity

Five steps are clearly sequenced (Step1–Step5), but there are no explicit validation checkpoints or error-recovery feedback loops — Step1's shape/columns print is only an implicit check.

2 / 3

Progressive Disclosure

Content is organized into stepped sections, but it is a single ~150-line monolithic file with no bundle references; material that could live in separate reference files is all inline.

2 / 3

Total

10

/

12

Passed

Description

75%

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 uses natural trigger terms, but it omits an explicit 'Use when...' clause, leaving the activation context only implied and capping completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when analyzing time series or categorical data, cleaning percentage fields, grading performance tiers, or forecasting business metrics.'

Sharpen distinctiveness by naming the unique combination (percentage cleaning + tier grading + forecasting) as the trigger rather than generic data analysis.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "多维度趋势分析", "百分比清洗", "绩效分级建模与预测", and "生成高分辨率的可视化综合报告" — matching the multiple-specific-actions anchor.

3 / 3

Completeness

The 'what' is clear, but the 'when' is only implied via "适用于业务指标监控与预测场景" with no explicit 'Use when...' trigger clause, which caps completeness at 2 per the guidelines.

2 / 3

Trigger Term Quality

Natural user-facing terms are well covered (时间序列, 分类数据, 趋势分析, 百分比, 预测, 可视化报告, 业务指标监控), the kind of vocabulary a user would actually say.

3 / 3

Distinctiveness Conflict Risk

The combination (percentage cleaning + grading + forecasting + viz) is somewhat specific, but without explicit trigger guidance it could overlap with general data-analysis skills rather than claiming a clear niche.

2 / 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.