a-b-test-config-creator
A B Test Config Creator - Auto-activating skill for ML Deployment. Triggers on: a b test config creator, a b test config creator Part of the ML Deployment skill category.
36
3%
Does it follow best practices?
Impact
100%
1.02xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/08-ml-deployment/a-b-test-config-creator/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 with no substantive content. It names the skill and its category but provides zero information about what it does, what actions it performs, or when it should be selected. The trigger terms are just the skill name duplicated, offering no value for skill selection.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Creates A/B test configuration files for ML model deployments, defining traffic splits, variant parameters, and experiment duration.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs to set up A/B tests, split tests, experiment configs, canary deployments, or traffic allocation for ML models.'
Include natural keyword variations users would actually say, such as 'A/B test', 'split test', 'experiment configuration', 'canary release', 'model variant', '.yaml config'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the skill ('A B Test Config Creator') and mentions 'ML Deployment' as a category, but provides no concrete actions. There is no explanation of what the skill actually does—no verbs describing capabilities like 'creates config files', 'defines traffic splits', or 'sets up experiment parameters'. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause or equivalent trigger guidance. The 'Triggers on' line is just the skill name repeated, not meaningful trigger context. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just the skill name repeated twice ('a b test config creator'). There are no natural user keywords like 'A/B test', 'experiment config', 'split test', 'feature flag', 'traffic allocation', or 'variant configuration' that a user would naturally say. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'A B Test Config Creator' and 'ML Deployment' provides some domain specificity that narrows the scope, but the lack of concrete actions or detailed triggers means it could still overlap with other ML or configuration-related 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 an empty shell with no actual instructional content. It consists entirely of meta-descriptions and placeholder text that repeatedly references 'a b test config creator' without ever providing concrete guidance, code examples, configuration templates, or actionable steps for creating A/B test configurations in an ML deployment context.
Suggestions
Add concrete, executable examples of A/B test configuration files (e.g., YAML/JSON configs for traffic splitting, model variant definitions, metric collection setup).
Define a clear step-by-step workflow: e.g., 1) Define variants and traffic split, 2) Configure metrics/KPIs, 3) Validate config schema, 4) Deploy with rollback plan.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill abstractly and replace with actual technical content.
Include validation steps such as config schema validation and a pre-deployment checklist to ensure safe A/B test rollouts.
| 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 technical content. Every section restates the same vague information about 'a b test config creator' without adding substance. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no configuration examples, no schemas, no specific steps for creating an A/B test configuration. The content only describes what the skill would do rather than actually doing it. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequencing, no validation checkpoints. The bullet 'Provides step-by-step guidance' is a claim without any actual steps provided. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of vague descriptions with no references to detailed materials, no links to examples or configuration schemas, and no meaningful structural organization beyond boilerplate headings. | 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
3076d78
- 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.