ab-test-analyzer
Ab Test Analyzer - Auto-activating skill for Data Analytics. Triggers on: ab test analyzer, ab test analyzer Part of the Data Analytics skill category.
36
Quality
3%
Does it follow best practices?
Impact
98%
0.98xAverage 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/ab-test-analyzer/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 essentially a placeholder that provides almost no useful information for skill selection. It lacks any concrete capabilities, meaningful trigger terms, or guidance on when to use it. The repeated skill name as trigger terms suggests auto-generated content without human refinement.
Suggestions
Add specific capabilities: 'Analyzes A/B test results, calculates statistical significance, compares conversion rates between variants, determines sample size requirements, and visualizes experiment outcomes.'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user mentions A/B tests, split tests, experiment analysis, conversion comparison, statistical significance, or variant performance.'
Fix the duplicate trigger terms and add variations users would naturally say: 'ab test', 'a/b test', 'split test', 'experiment results', 'conversion rate', 'statistical significance'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Ab Test Analyzer') without describing any concrete actions. There are no specific capabilities listed like 'calculate statistical significance', 'compare conversion rates', or 'analyze experiment results'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. The 'Triggers on' field just repeats the skill name rather than providing meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('ab test analyzer, ab test analyzer'). Missing natural user phrases like 'A/B test', 'split test', 'experiment results', 'conversion analysis', 'statistical significance'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Ab Test Analyzer' is a somewhat specific domain, the lack of detail means it could overlap with general data analytics or statistics skills. The category mention 'Data Analytics' is too broad to provide clear differentiation. | 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 content is essentially a placeholder template with no actual instructional value. It contains only generic descriptions of what an A/B test analyzer skill might do, without any concrete guidance, code examples, statistical methods, or actionable steps for performing A/B test analysis.
Suggestions
Add concrete, executable code examples for A/B test analysis (e.g., Python/SQL for calculating statistical significance, sample size, conversion rates)
Define a clear workflow with steps: data collection, hypothesis formulation, statistical test selection, result interpretation, and decision criteria
Include specific statistical methods and when to use them (chi-square, t-test, Bayesian analysis) with example calculations
Remove all generic boilerplate text ('provides automated assistance', 'follows best practices') and replace with actual actionable content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance, no code examples, no specific commands, and no actual instructions on how to perform A/B test analysis. The content only describes what the skill claims to do without showing how. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, and no validation checkpoints. The skill mentions 'step-by-step guidance' but provides none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to detailed materials, no links to examples, and no structured navigation to additional resources. | 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
0c08951
- 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.