Messaging Ab Tester logo

Messaging Ab Tester

OrganizationPopular
gooseworks-ai
messaging-ab-tester

Generate 3-5 messaging variants for a value proposition, design structured A/B tests, and analyze results to determine which framing resonates most with ICP. Tests can run via LinkedIn organic posts, cold email subject line splits, or both. Pure reasoning for variant generation and analysis — the user deploys the tests through their own tools. Use when a team can't decide between messaging angles and needs data, not opinions.

Overview

Publishergooseworks-ai
Repositorygoose-skills
Skill namemessaging-ab-tester
Stars
1.2K
Forks
216
Bundled files
1
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by gooseworks-ai on GitHub. Read the source before you install it.

Installation

Install the Messaging Ab Tester AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/gooseworks-ai/goose-skills/tree/main/skills/brand/composites/messaging-ab-tester
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git /tmp/goose-skills
mkdir -p .claude/skills
cp -r /tmp/goose-skills/skills/brand/composites/messaging-ab-tester .claude/skills/messaging-ab-tester
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Messaging Ab Tester in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Messaging Ab Tester on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Messaging Ab Tester is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Messaging A/B Tester

Stop debating which message is better — test it. Generate messaging variants, deploy them through real channels, and measure which framing actually resonates with your ICP.

Core principle: At seed/Series A, you don't have enough traffic for website A/B tests. But you do have enough LinkedIn impressions and cold email sends to test messaging angles fast.

When to Use

  • "Which of these value props should we lead with?"
  • "Test our messaging angles and tell me which works"
  • "I can't decide between [message A] and [message B]"
  • "What messaging resonates most with [ICP]?"
  • "Run a messaging test for [product/feature]"

Phase 0: Intake

What to Test

  1. Core value prop — The claim or positioning you want to test (e.g., "We help growth teams run outbound 10x faster")
  2. Test goal — What are you deciding? (Headline for website, cold email angle, LinkedIn content strategy, ad copy direction)
  3. ICP — Who should this resonate with? (Title, company type, stage)
  4. Current messaging — What are you using today? (Baseline to beat)

Test Channel

  1. Where to test:
    • LinkedIn organic — Post variants across consecutive days, compare engagement
    • Cold email — A/B test subject lines or opening hooks via Smartlead
    • Both — Run in parallel for fastest signal
  2. Sample size available:
    • LinkedIn: followers/typical impressions per post
    • Email: list size available for testing

Constraints

  1. Number of variants — 3-5 recommended (more = slower signal)
  2. Test duration — How long to run? (Default: 1 week for LinkedIn, 3-5 days for email)

Phase 1: Generate Messaging Variants

Create 3-5 variants that test different angles, not just different words. Each variant should represent a distinct strategic bet:

Variant Types

TypeWhat It TestsExample
Outcome-drivenLeading with the result"3x your pipeline in 30 days"
Pain-drivenLeading with the problem"Tired of spending 4 hours a day on manual prospecting?"
Identity-drivenLeading with who they are"Built for growth teams who move fast"
Proof-drivenLeading with evidence"How [Customer] went from 10 to 50 demos/month"
Contrast-drivenLeading with what you're not"Not another CRM. An outbound engine."

Variant Template

For each variant:

VARIANT [N]: [Type — e.g., "Outcome-driven"]

Hypothesis: This framing will resonate because [reasoning tied to ICP psychology]

LinkedIn post version:
---
[Full post copy — 100-200 words, native LinkedIn format]
---

Email subject line version:
[Subject line — max 50 chars]

Email opening hook version:
[First 2 sentences of an email]

Headline version:
[Website headline — max 10 words]

Phase 2: Deploy Tests

Option A: LinkedIn Organic Test

Setup:

  1. Schedule variants as consecutive posts (1 per day, same time of day)
  2. Each post should be similar length and format (control for post structure)
  3. Don't boost any posts — organic only for clean comparison

Measurement (after 48 hours per post):

  • Impressions
  • Reactions (likes, celebrates, etc.)
  • Comments
  • Comment sentiment (positive/negative/neutral)
  • Profile visits (if trackable)
  • DMs received mentioning the post

Option B: Cold Email A/B Test

Setup via your outreach tool (Smartlead, Instantly, Lemlist, or any tool with A/B testing):

  1. Create campaign with all variants as A/B test sequences
  2. Split list evenly across variants (minimum 50 per variant for signal)
  3. Same send time, same sender, same CTA — only the messaging changes

Measurement (after 5 days):

  • Open rate (tests subject line)
  • Reply rate (tests full message resonance)
  • Positive reply rate (tests conversion quality)
  • Click rate (if link included)

Option C: Both (Recommended)

Run LinkedIn and email in parallel. Different channels may show different winners — that's valuable signal about where each message works best.

Phase 2B: Collect Results

After the test has run for the planned duration, gather your results:

How to provide data:

  • Paste metrics — Copy open rates, reply rates, engagement numbers directly into the chat
  • CSV export — Export campaign analytics from your outreach tool and share the file
  • Screenshot — Take a screenshot of your dashboard/analytics and share it
  • Manual input — Just tell the agent the numbers: "Variant A got 45% open rate and 3% reply rate, Variant B got 52% open rate and 5% reply rate"

For LinkedIn tests: Go to your post analytics (click "View analytics" on each post) and share impressions, reactions, comments, and profile visits per post.

For email tests: Export or screenshot your campaign's variant/A-B test results showing sends, opens, and replies per variant.

The agent will normalize whatever format you provide into the scoring framework below.

Phase 3: Analyze Results

Scoring Framework

MetricWeight (LinkedIn)Weight (Email)
Engagement rate30%—
Comment quality30%—
Open rate—30%
Reply rate—40%
Positive reply rate—30%
Impressions20%—
Profile visits / clicks20%—

Statistical Significance Check

For email tests:

  • Minimum sends per variant: 50 (for directional signal), 200+ (for confident decisions)
  • Minimum difference to call a winner: >20% relative difference in primary metric

For LinkedIn tests:

  • Minimum posts per variant: 1 (you're testing with limited data — treat as directional)
  • Minimum impressions: 500 per post to be comparable

Winner Selection

WINNER: Variant [N] — [Type]

Primary metric: [X] (vs average of [Y] across other variants)
Relative improvement: [Z%] over baseline

Why it won:
[1-2 sentences on what this tells us about ICP messaging preferences]

Runner-up: Variant [N]
[1 sentence on when this might work better — different channel, different segment]

Phase 4: Output Format

markdown
# Messaging A/B Test Results — [DATE]
Value prop tested: [description]
ICP: [target audience]
Test duration: [dates]

---

## Test Design

| Variant | Type | Hypothesis |
|---------|------|-----------|
| A | [Type] | [Hypothesis] |
| B | [Type] | [Hypothesis] |
| C | [Type] | [Hypothesis] |

---

## Results

### LinkedIn Test

| Variant | Impressions | Reactions | Comments | Engagement Rate | Score |
|---------|------------|-----------|----------|----------------|-------|
| A | [N] | [N] | [N] | [X%] | [weighted] |
| B | [N] | [N] | [N] | [X%] | [weighted] |
| C | [N] | [N] | [N] | [X%] | [weighted] |

### Email Test

| Variant | Sends | Opens | Open Rate | Replies | Reply Rate | Positive | Score |
|---------|-------|-------|-----------|---------|------------|----------|-------|
| A | [N] | [N] | [X%] | [N] | [X%] | [N] | [weighted] |
| B | [N] | [N] | [X%] | [N] | [X%] | [N] | [weighted] |
| C | [N] | [N] | [X%] | [N] | [X%] | [N] | [weighted] |

---

## Winner: Variant [N] — "[Headline]"

**Why it won:** [Analysis — what does this tell us about how our ICP thinks?]

**Recommended deployment:**
- Website headline: "[adapted version]"
- Sales deck opening: "[adapted version]"
- LinkedIn bio: "[adapted version]"
- Cold email default: "[adapted version]"

---

## Variant Details & Copy

### Variant A: [Full copy used in test]
### Variant B: [Full copy used in test]
### Variant C: [Full copy used in test]

---

## What to Test Next

Based on these results, the next messaging test should explore:
1. [Angle suggested by results — e.g., "test more specific proof points since proof-driven won"]
2. [Segment test — e.g., "test winning message against different ICP segment"]

Save to the current working directory or wherever the user prefers.

Cost

ComponentCost
Variant generationFree (LLM reasoning)
LinkedIn postingFree (organic)
Email testingIncluded with your outreach tool's plan
Results analysisFree (LLM reasoning)
TotalFree

Tools Required

None. Pure reasoning for variant generation, test design, and result analysis. The user deploys tests through their own tools:

  • LinkedIn organic — post variants manually or via scheduling tool
  • Cold email — set up A/B tests in whatever outreach tool they use (Smartlead, Instantly, Lemlist, etc.)
  • Results — user provides metrics (screenshots, CSV exports, or manual input) for analysis

Trigger Phrases

  • "Test which messaging angle works best for [ICP]"
  • "Run a messaging A/B test for [value prop]"
  • "Which of these messages should we lead with?"
  • "Help me decide between these positioning options"

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Messaging Ab Tester AI skill do?

Generate 3-5 messaging variants for a value proposition, design structured A/B tests, and analyze results to determine which framing resonates most with ICP. Tests can run via LinkedIn organic posts, cold email subject line splits, or both. Pure reasoning for variant generation and analysis — the user deploys the tests through their own tools. Use when a team can't decide between messaging angles and needs data, not opinions.

Why use Messaging Ab Tester on TypingMind?

Because you install it once and use it with any model. Messaging Ab Tester is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Messaging Ab Tester in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/gooseworks-ai/goose-skills/tree/main/skills/brand/composites/messaging-ab-tester. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Messaging Ab Tester?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Messaging Ab Tester?

As many as you like. As long as a model supports skills, you can use Messaging Ab Tester with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Messaging Ab Tester AI skill free?

Yes. It is published on GitHub by gooseworks-ai under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇