CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

detecting-data-anomalies

Process identify anomalies and outliers in datasets using machine learning algorithms. Use when analyzing data for unusual patterns, outliers, or unexpected deviations from normal behavior. Trigger with phrases like "detect anomalies", "find outliers", or "identify unusual patterns".

Quality

74%

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 ./plugins/ai-ml/anomaly-detection-system/skills/detecting-data-anomalies/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 presents a well-sequenced, logically organized detection pipeline with clear algorithm-selection guidance and a genuinely useful error-handling table, supported by real one-level-deep reference files. Its main weaknesses are the total absence of executable code in the body and redundancy with both Claude's existing knowledge and the bundled implementation guide.

Suggestions

Add a compact executable snippet (e.g., sklearn IsolationForest with contamination set and score thresholding) to the Instructions or a Quick start section so the pipeline is copy-paste runnable rather than abstract.

Trim explanations Claude already knows (what StandardScaler/MinMaxScaler do, when to use each algorithm) and move version pins like "scikit-learn >= 1.3" into the referenced implementation guide to tighten token usage.

Link references/examples.md from the Examples section (or replace the inline scenarios with a pointer to it) and remove placeholder scripts/assets README entries for files that don't exist, such as data_loader.py.

DimensionReasoningScore

Conciseness

The body is mostly efficient but restates knowledge Claude already has (e.g., "Apply StandardScaler or MinMaxScaler to numeric features to normalize magnitude differences" and the algorithm-selection rationales) and pins time-sensitive versions ("Python 3.9+ with scikit-learn >= 1.3") outside any deprecated/setup section. It sits at anchor 3 rather than 4 because several such spots could be trimmed without losing guidance.

3 / 5

Actionability

Steps include concrete specifics ("Set the contamination parameter to the expected anomaly proportion (start with 0.01-0.05)", named algorithms, thresholds) but the body contains no executable code or commands for a skill whose work is Python-based, matching anchor 3's "missing key details" rather than anchor 4's "concrete code or commands".

3 / 5

Workflow Clarity

The 10 numbered steps form a clear ingestion-to-report sequence with an early checkpoint ("verify schema, column types, and row count") and error-recovery guidance ("Lower contamination to 0.01; verify StandardScaler applied"). Not anchor 5 because most validation checkpoints are implicit rather than explicit gate steps.

4 / 5

Progressive Disclosure

The overview body clearly signals real, one-level-deep references ([references/implementation.md], [references/errors.md]) at the right points, matching anchor 4. It falls short of anchor 5 because references/examples.md is never linked from the body, the Instructions section largely duplicates implementation.md, and the scripts/assets READMEs advertise files (e.g., data_loader.py) that do not exist in the bundle.

4 / 5

Total

14

/

20

Passed

Description

78%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 does the essential job well: explicit what, explicit when, and concrete natural-language trigger phrases in third person. Its weaknesses are a grammatically broken opening clause ("Process identify anomalies") and a generic "machine learning algorithms" method claim that keeps specificity and trigger coverage slightly below the top anchors.

Suggestions

Fix the opening to a clean third-person verb phrase, e.g., "Identify anomalies and outliers in datasets using machine learning algorithms" (currently "Process identify anomalies...").

Name the concrete techniques or outputs (e.g., Isolation Forest, One-Class SVM, LOF, autoencoders) instead of the generic "machine learning algorithms" to raise capability specificity.

Add common trigger variations such as "anomaly detection" and "outlier detection" to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

It names the domain and one core action ("identify anomalies and outliers in datasets using machine learning algorithms") but the method stays generic and no list of several concrete capabilities appears, matching anchor 3 rather than anchor 4's "lists several specific actions".

3 / 5

Completeness

It explicitly answers what ("identify anomalies and outliers in datasets using machine learning algorithms"), when ("Use when analyzing data for unusual patterns, outliers, or unexpected deviations from normal behavior"), and supplies concrete trigger phrases, matching anchor 5. The garbled opening "Process identify anomalies" is a grammar flaw, not a missing element, so it does not fall to anchor 4.

5 / 5

Trigger Term Quality

"detect anomalies", "find outliers", and "identify unusual patterns" are natural user phrases with good coverage, but common variations like "anomaly detection" or "outlier detection" are absent, placing it at anchor 4 rather than anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Anomaly/outlier detection is a clear niche with distinct triggers, but the broad "analyzing data" framing leaves minor overlap risk with general data-analysis skills, matching anchor 4's "minor overlap risk with closely related skills" rather than anchor 5's minimal conflict risk.

4 / 5

Total

16

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

jeremylongshore/tons-of-skills-marketplace

Path

plugins/ai-ml/anomaly-detection-system/skills/detecting-data-anomalies/SKILL.md

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.