Customer Skills

Customer Skills are versioned rule bundles, playbooks you author, that tell your campaigns how your brand talks and what it will and will not say. A skill turns the marketing know-how that usually lives in one person's head into a named, reusable asset your whole team can draw on.

A skill is written once and used everywhere your copy is generated. Instead of re-explaining your voice in every brief, you capture it as a skill, version it like anything else worth keeping, and let the system apply it consistently across your sends.

What goes in a skill

A skill is a bundle of the rules you would give a sharp new hire on their first day:

• Brand voice: how you sound, the words you favor, and the tone you hold.
• Dos and don'ts: the lines you never cross and the claims you never make.
• Offers: the promotions and hooks that are on the table, and the ones that are not.

Written down and versioned, these stop being tribal knowledge that walks out the door when someone changes teams. A new teammate, or a new agent, inherits your standards instead of guessing at them.

You do not have to capture everything at once. A skill can start small, one page of voice and a few hard rules, and grow as you learn what your campaigns keep getting wrong. Because it is versioned, that growth is tracked rather than lost.

Versioned, and safe to turn on

Every skill is versioned, so you can see what changed, compare two versions, and roll back if a change does not land. That history is the same idea as optimization lineage: you always know which rules produced which copy.

The send path uses skills in a way that is gated and parity-proven. In plain terms, a skill only changes what you have decided it should change, and it was tested to produce identical output everywhere nothing was meant to differ. Turning a skill on does not quietly rewrite everything else.

Safety like this is what lets a skill graduate from a nice idea into something you actually run. You can adopt one on a Tuesday, watch a few sends, and roll it back on Wednesday if it is not right, all without a migration or a leap of faith.

Fork a skill into an experiment

Because a skill is a discrete, versioned object, you can fork it into variants and test them head to head. Fork your voice playbook, change one thing (a bolder offer, a softer tone), and run the two as an A/B against real audiences.

You: Fork the "Weeknight voice" skill into a variant with a
stronger urgency hook, and A/B it against the original on the
lapsed 30 days audience.

Skill Lab: Forked to "Weeknight voice (urgency)". A/B armed:
50/50 split, original held as control.

This is how a playbook earns its place. You are not arguing about which voice is better in a meeting, you are letting two versions of the skill settle it in the sends themselves, then keeping the winner as the next version.

Forking is cheap, which is the point. A variant is a copy of a known-good skill with one deliberate change, so a test never starts from scratch and never risks your baseline. The control keeps doing what it already did while the variant proves itself, or does not.

The Skill Lab

Skills are authored in the Skill Lab, where you can write, preview, train, and promote them:

1. Author a new skill or edit an existing one.
2. Preview the copy it would produce before anything ships.
3. Train it by feeding examples of what good looks like.
4. Promote a version once it is ready to inform live sends.

Nothing you do in the Lab touches live sends until you promote a version, so authoring and experimenting stay safely separate from what customers actually receive.

The Lab pairs naturally with your copy guardrails: guardrails are the floor every message must clear, and a skill is the voice and strategy layered on top. Together they turn your marketing standards into something you can write down, test, and improve on purpose, so your best thinking becomes an asset the whole harness can reuse.