correlation-analyzer
Correlation Analyzer - Auto-activating skill for Data Analytics. Triggers on: correlation analyzer, correlation analyzer Part of the Data Analytics skill category.
28
0%
Does it follow best practices?
Impact
72%
0.92xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/12-data-analytics/correlation-analyzer/SKILL.mdQuality
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a boilerplate template with no substantive content. It lacks concrete actions, meaningful trigger terms, explicit 'when to use' guidance, and any distinguishing details that would help Claude select it appropriately from a pool of skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Computes Pearson and Spearman correlation coefficients, generates correlation matrices, and visualizes relationships between variables with scatter plots and heatmaps.'
Add a 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about correlations, relationships between variables, correlation matrices, scatter plots, r-squared values, or wants to identify which variables are related in a dataset.'
Remove the duplicated trigger term and expand with natural language variations users would actually say, such as 'correlate', 'relationship between columns', 'covariance', 'association between features'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('Data Analytics') and a tool name ('Correlation Analyzer') but provides no concrete actions. There is no mention of what the skill actually does—no verbs like 'compute', 'visualize', 'identify correlations', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and there is no 'when should Claude use it' clause. The 'Triggers on' line is just the skill name repeated, not meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'correlation analyzer' repeated twice. There are no natural user phrases like 'correlation', 'relationship between variables', 'scatter plot', 'r-squared', or 'correlate columns' that a user would naturally say. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic—'Data Analytics' could overlap with dozens of other analytics skills. Without specific actions or file types, it would easily conflict with any other data analysis skill. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template with no actual content. It contains only generic boilerplate that repeats the phrase 'correlation analyzer' without providing any actionable guidance, code examples, statistical methods, or workflow steps for performing correlation analysis. It adds zero value beyond what Claude already knows.
Suggestions
Add concrete, executable code examples for common correlation analysis tasks (e.g., Pearson/Spearman correlation in Python with pandas/scipy, SQL-based correlation queries).
Define a clear workflow: load data → check assumptions (normality, linearity) → compute correlations → interpret results → visualize with heatmaps, with validation at each step.
Remove all boilerplate sections (Purpose, When to Use, Example Triggers, Capabilities) that describe the skill meta-information rather than teaching how to do correlation analysis.
Add specific guidance on pitfalls (e.g., correlation vs causation, handling missing data, multicollinearity) and include example output interpretation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'correlation analyzer' excessively, and provides zero substantive information about how to actually perform correlation analysis. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no code, no commands, no specific steps, no examples of correlation analysis techniques. Every section is vague and abstract, describing what the skill supposedly does rather than instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, no validation checkpoints. The phrase 'step-by-step guidance' is mentioned but never delivered. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of generic placeholder text with no meaningful structure, no references to detailed materials, and no navigation to deeper content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
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 | 9 / 11 Passed | |
- Commit
4dee593
- 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.