Ab Test Analyzer - Auto-activating skill for Data Analytics. Triggers on: ab test analyzer, ab test analyzer Part of the Data Analytics skill category.
Overall
score
24%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill ab-test-analyzerActivation
22%This description is essentially a placeholder that provides almost no useful information for skill selection. It names the skill and category but fails to describe any concrete capabilities, use cases, or trigger scenarios. The description would be nearly useless in a collection of 10+ skills where Claude needs to distinguish between options.
Suggestions
Add specific capabilities: describe what the skill actually does (e.g., 'Calculates statistical significance, compares conversion rates between variants, determines sample size requirements, and visualizes experiment results').
Add an explicit 'Use when...' clause with natural trigger terms like 'A/B test', 'split test', 'experiment', 'conversion rate', 'statistical significance', 'variant comparison'.
Remove the redundant trigger term ('ab test analyzer' is listed twice) and expand to include variations users would naturally say.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - it only states it's an 'Auto-activating skill for Data Analytics' without describing what it actually does (e.g., calculate statistical significance, compare conversion rates, analyze experiment results). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming itself, and has no explicit 'Use when...' clause or equivalent guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Contains 'ab test analyzer' as a trigger term (repeated twice), which is relevant but misses common variations users might say like 'A/B test', 'split test', 'experiment analysis', 'conversion rate', 'statistical significance'. | 2 / 3 |
Distinctiveness Conflict Risk | While 'ab test analyzer' is somewhat specific, the vague 'Data Analytics' category could overlap with other analytics skills. The lack of specific capabilities makes it unclear how this differs from general data analysis tools. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no substantive guidance for AB test analysis. It contains only meta-descriptions of what a skill should do without any actual instructions, code, statistical methods, or concrete examples. The content fails on all dimensions by being simultaneously verbose (with filler) and empty (of actionable content).
Suggestions
Add concrete code examples for AB test analysis (e.g., Python/SQL for calculating conversion rates, statistical significance tests like chi-square or t-tests)
Include a clear workflow: 1) Define metrics, 2) Calculate sample statistics, 3) Run significance test, 4) Interpret results with specific thresholds
Provide example input data structure and expected output format (e.g., p-value interpretation, confidence intervals)
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with specific statistical methods and decision criteria
| 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, no commands, no specific steps, no examples of actual AB test analysis. The content describes what the skill supposedly does without showing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. Claims to provide 'step-by-step guidance' but contains no actual steps. There's no sequence, no validation, and no process for performing AB test analysis. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic statements with no structure for discovery. No references to detailed materials, no examples, and no organized sections with actual content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
Reviewed
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.