CtrlK
BlogDocsLog inGet started
Tessl Logo

outlier-detection-and-quality-assessment

执行全面的异常值检测与数据质量评估,利用 IQR 方法识别异常值并结合偏度、峰度分析数据分布特征,适用于非正态分布数据的预处理阶段。

59

Quality

67%

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-cleaning/outlier-detection/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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 skill is highly actionable with lean, executable code and clear section structure, but lacks validation checkpoints for its batch and destructive-handling steps, which caps workflow clarity.

Suggestions

Add validation checkpoints after outlier detection (e.g. review outlier_ratio before acting) and before applying handle_outliers, especially for the destructive 'drop' method.

Add a brief error-recovery note for common failures (missing file, non-numeric data, empty columns) so the workflow has a feedback loop.

Consider splitting the boxplot visualization and handling-skeleton steps into reference files to keep the main SKILL.md closer to an overview.

DimensionReasoningScore

Conciseness

The body is almost entirely executable code with brief section-label comments and no padding or explanations of concepts Claude already knows; a few inline comments merely narrate the following line and could be trimmed.

4 / 5

Actionability

Steps 1–4 are fully executable, copy-paste-ready code covering load, IQR outlier detection, boxplot visualization, and skewness/kurtosis analysis, with the intentionally-labeled Step 5 skeleton clearly marked.

5 / 5

Workflow Clarity

Steps are clearly sequenced 1–5, but the workflow loops over all numeric columns (batch) and includes a destructive handle_outliers skeleton (drop/cap) with no validation checkpoints or error-recovery guidance, capping workflow clarity at 3 per the batch/destructive guideline.

3 / 5

Progressive Disclosure

Content is well-organized into five clearly headed Step sections with no nested references (and no bundle files exist); at ~148 lines it slightly exceeds the simple-skill threshold, so a couple of sections (visualization, handling) could optionally be split out, leaving minor organization gaps.

4 / 5

Total

16

/

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 clearly states concrete capabilities and a defined niche, but lacks an explicit trigger clause and relies on somewhat technical terminology, which limits trigger-term quality and completeness.

Suggestions

Add an explicit 'Use when...' / "使用当..." trigger clause naming concrete user cues (e.g. finding outliers, checking data quality before modeling).

Include more natural synonyms and variations users would say, such as 'outliers', 'boxplot', or '数据清洗', alongside the statistical terms.

Mention the visualization (箱线图) and handling-suggestion outputs so the description covers the full body workflow.

DimensionReasoningScore

Specificity

Names the domain plus several concrete actions — "利用 IQR 方法识别异常值" and "结合偏度、峰度分析数据分布特征" — with only minor gaps (visualization and handling steps from the body are omitted).

4 / 5

Completeness

The "what" is clear (IQR outlier detection plus skewness/kurtosis analysis) but there is no explicit "Use when..." trigger clause; the "适用于...预处理阶段" phrase only weakly implies when, capping completeness at 3 per the guidelines.

3 / 5

Trigger Term Quality

Relevant terms like "异常值检测", "数据质量评估", "IQR", "偏度", "峰度" are present but lean technical; common variations or synonyms (e.g. boxplot, outliers) are missing.

3 / 5

Distinctiveness Conflict Risk

The niche is fairly specific — IQR plus skewness/kurtosis for non-normal data preprocessing — making it mostly distinct from generic data-analysis skills with only minor overlap risk.

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.

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.