Identify and handle statistical outliers in datasets using z-score, IQR, or Grubbs methods with regulatory-ready documentation.
70
63%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./scientific-skills/Data analysis/outlier-detection-handler/SKILL.mdQuality
Discovery
50%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 excels at specificity by naming concrete statistical methods and outputs, and carves out a distinct niche. However, it critically lacks explicit trigger guidance ('Use when...') which would help Claude know when to select this skill, and could benefit from more natural user-facing keywords beyond technical statistical terms.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about detecting outliers, cleaning data anomalies, or needs statistical validation for compliance.'
Include common user-facing synonyms like 'anomaly detection', 'data cleaning', 'remove outliers', 'detect anomalies', or 'data validation' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Identify and handle statistical outliers' using specific methods (z-score, IQR, Grubbs) with a specific output type (regulatory-ready documentation). | 3 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes good technical terms like 'outliers', 'z-score', 'IQR', 'Grubbs' that users familiar with statistics would use, but misses common variations like 'anomaly detection', 'data cleaning', 'remove outliers', or 'detect anomalies'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of statistical outlier detection with specific methods (z-score, IQR, Grubbs) and regulatory documentation creates a clear, distinct niche unlikely to conflict with general data analysis skills. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with strong actionability and workflow clarity. The CLI interface is clearly documented with executable examples, and error handling covers important edge cases including security (path traversal) and graceful degradation. The main weaknesses are moderate verbosity in the template sections and lack of progressive disclosure to external files for the detailed templates.
Suggestions
Consider moving the Fallback Template and Response Template sections to a separate TEMPLATES.md file and referencing them, reducing the main skill file length
Trim the refusal instruction paragraph - the bold warning about firing first could be shortened since Claude understands instruction priority
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy (workflow steps repeated conceptually, verbose refusal instructions, template structures that could be trimmed). The parameter table and usage examples are appropriately concise. | 2 / 3 |
Actionability | Provides concrete CLI commands with specific flags, clear parameter documentation, executable usage examples, and a quick check section. The guidance is copy-paste ready and specific. | 3 / 3 |
Workflow Clarity | Clear numbered workflow with explicit validation as step 1, error handling section with specific failure modes and responses, fallback template for incomplete execution, and path traversal security check. Feedback loops are well-defined. | 3 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in one file. The response template and fallback template add bulk that could potentially be referenced externally. No references to separate documentation files for advanced usage. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
ca9aaa4
Table of Contents
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.