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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill a-b-test-config-creatorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder that provides almost no useful information for skill selection. It lacks concrete actions, meaningful trigger terms, and explicit usage guidance. The only distinguishing element is the skill name and category, which is insufficient for Claude to make informed decisions when choosing among multiple skills.
Suggestions
Add specific actions the skill performs, e.g., 'Creates A/B test configuration files, defines experiment variants, sets traffic allocation percentages, and configures success metrics.'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user mentions A/B testing, split tests, experiment setup, traffic splitting, variant configuration, or feature experiments.'
Replace the redundant trigger list with varied natural phrases users would actually say, such as 'AB test', 'A/B experiment', 'split test config', 'experiment configuration'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('A B Test Config Creator') without describing any concrete actions. There are no verbs explaining what the skill actually does - no mention of creating configs, defining variants, setting traffic splits, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' clause is just a circular reference to the skill name. There is no explicit guidance on when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just the skill name repeated twice ('a b test config creator'). Missing natural user phrases like 'A/B test', 'split test', 'experiment config', 'traffic allocation', 'variant setup', or 'feature flag'. | 1 / 3 |
Distinctiveness Conflict Risk | The 'ML Deployment' category and 'A B Test Config Creator' name provide some specificity to the domain, but without concrete actions or proper trigger terms, it could still conflict with other ML or testing-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder with no substantive content. It describes what an A/B test config creator skill would do in abstract terms but provides zero actionable guidance, no code examples, no configuration templates, and no actual instructions for creating A/B test configurations in ML deployment contexts.
Suggestions
Add concrete, executable examples of A/B test configuration files (e.g., YAML/JSON schemas for traffic splitting, variant definitions, metrics collection)
Include a step-by-step workflow for creating an A/B test config: define variants → set traffic allocation → configure metrics → validate config → deploy
Provide specific code snippets for common ML serving platforms (e.g., KServe, Seldon, SageMaker) showing how to implement A/B testing
Remove all generic boilerplate text ('provides automated assistance', 'follows best practices') and replace with actual technical content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actionable information. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific steps, no examples of actual A/B test configurations. The skill describes what it does rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The 'Capabilities' section lists vague promises without any actual process. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no structure pointing to detailed materials, no references to configuration schemas, examples, or related documentation. | 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
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.