Menu

Individual skill

personalized-outbound-ab-test

0upvotes

Use this skill when someone claims AI personalization lifts reply rates, or before you let an agent write outbound at scale. Runs a control/personalized/holdout split on your connection list, enforces a safety gate on every generated message, and returns a defensible read on whether personalization actually beat the generic baseline.

skills/amir-baldiga/personalized-outbound-ab-test/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
237
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

Run this before you let an agent write outbound at scale. It produces a measured answer to "does personalization actually beat our generic message?" and a holdout that receives the winner.

## The play

1. **Split the list into three.** Control (e.g. 100) gets the generic baseline. Personalized (e.g. 100) gets researched messages. Holdout (the rest) waits for the result, then gets the winner. Without a control you are not testing, you are just spending.

2. **Build the do-not-contact list first.** Exclude anyone already in an open thread, in the CRM as an active deal, or recently sequenced. Skipping this is how you send a "nice to meet you" to a customer. Do this before enrichment so you never pay to research someone you cannot contact.

3. **Enrich only the Personalized arm.** Pull current role, headline, employer, and recent activity per lead. The control arm needs nothing, so half your enrichment spend disappears.

4. **Write one message per lead, then gate it.** Every message must pass all six checks or it silently drops to the baseline:
   - **Account-safe** — no links, no phone numbers, no mass-template feel.
   - **Factually grounded** — every personal reference traces to retrieved data. Zero invented facts.
   - **Human** — no AI tells, in the sender's own rhythm.
Back to top