prompt-test
A/B test content variations. Use when: comparing quality scores across prompt approaches, headline styles, or content versions.
What this skill does
# /digital-marketing-pro:prompt-test
## Purpose
A/B test content output variations by comparing quality scores across different prompt approaches, headline styles, CTA phrasing, or complete content strategy variations. Create named tests, log variants with their evaluation scores, and determine which approach produces the best quality results.
This command brings experimental rigor to content creation. Instead of guessing which headline style, subject line approach, or content structure works best, you run a structured test: define the experiment, log each variant with its quality scores, and get a statistically grounded recommendation on which approach to adopt. Useful for testing subject line styles (curiosity vs. benefit-driven), headline approaches (question vs. statement vs. how-to), CTA phrasing (urgency vs. value vs. social proof), tone variations (formal vs. conversational), or complete content strategy A/B comparisons.
## Input Required
The user must provide (or will be prompted for):
- **Action**: What to do — `create` (set up a new test), `log` (add a variant to an existing test), `results` (get comparison and winner), or `list` (show all tests)
- **Test name**: A descriptive name for the experiment (e.g., "Q1 email subject line style", "homepage headline approach") — required for `create`, `log`, and `results`
- **Variant label**: Identifier for this variant (e.g., "A", "B", "C", "control", "curiosity-driven", "benefit-led") — required for `log`
- **Content for the variant**: The actual content to evaluate — text inline, file path, or pasted content block — required for `log`
- **Variant description**: Brief explanation of the approach or strategy this variant represents (e.g., "Uses curiosity gap with no product mention", "Leads with quantified benefit") — required for `log`
- **Content type**: The type of content being tested (email subject line, headline, ad copy, CTA, full article, etc.) — optional, applied during evaluation for dimension weighting
- **Evidence file**: Supporting data or research that informs the test hypothesis — optional, passed to evaluation for context
## Process
1. **Load brand context**: Read `~/.claude-marketing/brands/_active-brand.json` for the active slug, then load `~/.claude-marketing/brands/{slug}/profile.json`. Apply brand voice, compliance rules for target markets (`skills/context-engine/compliance-rules.md`), and industry context. Check for guidelines at `~/.claude-marketing/brands/{slug}/guidelines/_manifest.json` — if present, load restrictions and relevant category files (voice-and-tone rules, messaging hierarchy, channel style guides). Check for custom templates at `~/.claude-marketing/brands/{slug}/templates/`. Check for agency SOPs at `~/.claude-marketing/sops/`. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults.
2. **For `create` action**: Set up a new test by running `python scripts/prompt-ab-tester.py --brand {slug} --action create-test --test-name "{name}"`. This initializes the test record with metadata (creation date, brand, content type) and prepares it for variant logging. Confirm the test was created and remind the user to log variants with `/digital-marketing-pro:prompt-test` using the `log` action.
3. **For `log` action**: First evaluate the variant content for quality by running `python scripts/eval-runner.py --brand {slug} --action run-quick --text "{content_or_path}" --content-type "{type}"` (pass `--evidence "{evidence_path}"` if provided). This produces per-dimension scores (clarity, persuasion, brand alignment, readability, compliance, etc.) and a composite score. Then log the variant with its scores by running `python scripts/prompt-ab-tester.py --brand {slug} --action log-variant --test-name "{name}" --variant-label "{label}" --variant-description "{description}" --scores "{scores_json}"`. Present the individual variant scores to the user immediately so they can see how this variant performed before logging additional variants.
4. **For `results` action**: Pull the full comparison by running `python scripts/prompt-ab-tester.py --brand {slug} --action get-results --test-name "{name}"`. Analyze the results:
- Identify the winning variant by highest composite score
- Calculate the margin of victory (percentage difference between winner and runner-up)
- Assess statistical significance — if variants are within 5% of each other, flag as "too close to call" and recommend additional testing or tiebreaker criteria
- Break down per-dimension performance to show where each variant excels or falls short (e.g., Variant A wins on persuasion but Variant B wins on clarity)
- Identify the specific strengths of the winning approach that can be applied to future content
- Flag any variants that fell below the auto-reject threshold (composite < 60) as unsuitable
5. **For `list` action**: Run `python scripts/prompt-ab-tester.py --brand {slug} --action list-tests` to show all tests for this brand, their status (in-progress, completed), variant count, and creation date.
6. **Present results with clear recommendation**: Summarize findings in a decision-ready format — state the winner, explain why it won, quantify the advantage, note any caveats, and provide a specific recommendation on which approach to adopt going forward. If the winning approach reveals a pattern (e.g., benefit-driven headlines consistently outperform curiosity-based ones for this brand), note that as a reusable insight.
## Output
A structured test report containing:
- **Test summary**: Test name, content type, number of variants, date range
- **Per-variant scorecard**: Each variant's label, description, composite score, and per-dimension breakdown (clarity, persuasion, brand alignment, readability, compliance, engagement potential)
- **Winner declaration**: Which variant won, by what margin, and whether the margin is statistically meaningful
- **Dimension analysis**: Which variant leads on each individual dimension — reveals trade-offs (e.g., "Variant B is more persuasive but Variant A has better brand alignment")
- **Confidence level**: High confidence (>15% margin), moderate confidence (5-15% margin), or low confidence (<5% margin, recommend further testing)
- **Specific recommendation**: Clear statement on which approach to adopt and why, with guidance on how to apply the winning approach to future content
- **Reusable insight**: Any pattern or principle that emerged from this test that can inform the broader content strategy
- **Auto-reject flags**: Any variants that scored below the quality threshold with specific reasons
## Agents Used
- **quality-assurance** -- Evaluates each variant's content quality across multiple dimensions, provides scoring consistency, identifies quality issues, and ensures evaluation criteria align with brand standards
- **content-creator** -- Generates additional variant content if the user requests AI-produced alternatives to test against their own versions, applies brand voice to generated variants
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.