statistical-significance-calculator
Statistical Significance Calculator - Auto-activating skill for Data Analytics. Triggers on: statistical significance calculator, statistical significance calculator Part of the Data Analytics skill category.
35
3%
Does it follow best practices?
Impact
94%
1.02xAverage 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/statistical-significance-calculator/SKILL.mdQuality
Discovery
7%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 extremely weak—it essentially repeats the skill name without describing any concrete capabilities, natural trigger terms, or explicit usage guidance. It reads like auto-generated boilerplate rather than a useful selection aid. It would be nearly indistinguishable from other data analytics skills and provides no actionable information for Claude to decide when to use it.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Calculates p-values, runs t-tests, chi-square tests, and A/B test significance analysis for comparing sample groups.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about p-values, hypothesis testing, A/B test results, confidence intervals, statistical significance, or comparing sample means.'
Remove the duplicated trigger term and replace with diverse natural language variations users would actually say, such as 'significance level', 'is this result significant', 'A/B test', 'sample size calculator'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('Data Analytics') and the tool name ('Statistical Significance Calculator') but does not describe any concrete actions like computing p-values, comparing sample means, running hypothesis tests, etc. It is essentially just a title repeated. | 1 / 3 |
Completeness | The description fails to clearly answer 'what does this do' beyond restating the name, and there is no explicit 'Use when...' clause explaining when Claude should select this skill. The 'Triggers on' line is just the skill name repeated. | 1 / 3 |
Trigger Term Quality | The only trigger term listed is 'statistical significance calculator' repeated twice. It misses natural variations users would say such as 'p-value', 'hypothesis test', 'A/B test', 'significance level', 'chi-square', 'confidence interval', or 't-test'. | 1 / 3 |
Distinctiveness Conflict Risk | The phrase 'statistical significance calculator' is somewhat specific to a niche domain, which reduces conflict risk compared to fully generic descriptions. However, the vague 'Data Analytics' category and lack of concrete scope could still cause overlap with other analytics or statistics skills. | 2 / 3 |
Total | 5 / 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 essentially a placeholder template with no substantive content. It repeatedly describes itself in abstract terms without providing any actual statistical significance calculation methods, formulas, code examples, or actionable guidance. It fails on every dimension because it contains no real instructional content.
Suggestions
Add executable code examples for common statistical significance tests (e.g., t-test, chi-squared, z-test for proportions) using Python's scipy.stats or statsmodels libraries.
Include a concrete workflow: define hypotheses → choose test → calculate test statistic → interpret p-value, with specific code for each step.
Provide a practical example with sample data showing input (e.g., A/B test conversion rates and sample sizes) and expected output (p-value, confidence interval, significance determination).
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actual statistical formulas, decision criteria for choosing tests, and interpretation guidelines.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual statistical significance calculation guidance, formulas, code, or concrete information. Every section restates the same vague concept. | 1 / 3 |
Actionability | There is zero concrete guidance—no formulas, no code, no specific statistical tests, no examples of inputs/outputs. The skill describes rather than instructs, offering only vague promises like 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. There are no instructions for performing any statistical significance calculation, no validation checkpoints, and no sequenced operations. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive document with no meaningful structure. There are no references to detailed materials, no code examples to organize, and the sections are all meta-descriptions rather than substantive 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.