ab-test-setup
Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness.
52
41%
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 ./.agent/skills/ab-test-setup/SKILL.mdQuality
Discovery
32%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 identifies a clear domain (A/B testing) and hints at a structured workflow with mandatory checkpoints, which is useful. However, it lacks explicit trigger guidance ('Use when...'), misses common synonym terms users might say, and doesn't enumerate specific concrete actions the skill performs.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user wants to design an A/B test, split test, or experiment, or needs help with hypothesis formulation or test metrics'.
Include natural keyword variations such as 'split testing', 'experiment design', 'conversion testing', 'variant testing' to improve discoverability.
List more specific concrete actions like 'define hypotheses', 'select success metrics', 'determine sample size', 'validate execution readiness' to clarify capabilities.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (A/B tests) and mentions some actions (setting up, gates for hypothesis, metrics, execution readiness), but doesn't list multiple concrete specific actions like 'define control groups', 'calculate sample sizes', or 'analyze results'. | 2 / 3 |
Completeness | Describes what it does (structured guide for A/B test setup with gates) 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 'A/B tests' which is a natural term users would say, but misses common variations like 'split testing', 'experiment', 'variant testing', 'conversion testing', or 'multivariate test'. | 2 / 3 |
Distinctiveness Conflict Risk | The A/B testing focus provides some distinctiveness, but 'structured guide' and 'metrics' are generic enough to potentially overlap with other experiment, analytics, or planning skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
50%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 table of contents with minimal overview content. While it's concise and has a clear structure pointing to sub-skills, it fails to provide any actionable guidance in the main file itself. A user cannot understand what to do at any step without clicking through to 11 separate files.
Suggestions
Add a concrete quick-start section showing the minimum viable workflow (e.g., 'Before starting: 1. Write hypothesis in format X, 2. Calculate sample size using Y, 3. Pass readiness checklist')
Include at least one executable example - such as a hypothesis template, a sample size calculation formula, or a metrics definition format
Add brief descriptions to each sub-skill link explaining what it covers and when to use it, rather than just numbered links
Include the key validation criteria for the 'Hard Gates' directly in this file so Claude knows what must pass before proceeding
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is extremely lean - no unnecessary explanations of what A/B testing is or how statistics work. Every line serves a purpose: scope, prerequisites, and navigation to sub-skills. | 3 / 3 |
Actionability | The skill provides no concrete guidance, code, commands, or examples. It's entirely a table of contents with vague bullet points like 'Prevents peeking' without explaining how or what to do. | 1 / 3 |
Workflow Clarity | The numbered sub-skills suggest a sequence (1-11), and 'Hard Gate' labels indicate checkpoints. However, the actual workflow steps, validation criteria, and what happens at each gate are completely absent from this file. | 2 / 3 |
Progressive Disclosure | References to sub-skills are one level deep and clearly linked, which is good. However, the overview provides almost no substantive content - it's essentially just a link list with no quick-start guidance or summary of what each module covers. | 2 / 3 |
Total | 8 / 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 | |
- Repository
- Dokhacgiakhoa/antigravity-ide
- Commit
332e58b
- 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.