home / skills / gtmagents / gtm-agents / content-variants

content-variants skill

safe

/plugins/personalization-engine/skills/content-variants

This skill helps plan, approve, and version personalized creative assets across channels with structured variant governance and lifecycle tracking.

npx playbooks add skill gtmagents/gtm-agents --skill content-variants

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

1.3 KB

---
name: content-variants
description: Use when planning, approving, and versioning personalized creative assets.
---

# Content Variant System Skill

## When to Use
- Mapping creative requirements for each decision tree branch.
- Coordinating design, copy, and legal reviews across multiple channels.
- Auditing variant performance or sunsetting outdated experiences.

## Framework
1. **Variant Inventory** – catalog base asset, variant name, audience, channel, owner, expiration.
2. **Approval Flow** – document reviewers, compliance steps, localization, accessibility requirements.
3. **Asset Delivery** – link storage locations (DAM, CMS, MAP) plus version IDs and CDN paths.
4. **Testing Hooks** – note experiment IDs, KPIs, guardrails for each variant.
5. **Lifecycle Management** – set refresh cadences, archival rules, and dependency tracking.

## Templates
- Variant matrix (channel × persona × lifecycle stage).
- Approval checklist (copy, design, legal, localization, accessibility).
- Performance tracker (variant → impressions → engagement → conversion → decision).

## Tips
- Assign unique IDs to every variant for analytics + rollback references.
- Bundle variants into kits aligned with key journeys for easier governance.
- Pair with `decision-trees` outputs to ensure every branch has an approved asset.

---

Overview

This skill helps teams plan, approve, version, and manage personalized creative assets across channels and audiences. It provides a structured framework to inventory variants, coordinate reviews, track delivery, and enforce lifecycle rules. The goal is faster approvals, reliable experiments, and safer rollbacks.

How this skill works

The skill inspects asset requirements for each decision branch and generates a Variant Inventory with unique IDs, owners, channels, and expiration. It builds an Approval Flow listing reviewers and compliance steps, maps Asset Delivery links (DAM/CMS/MAP) with version IDs, and attaches Testing Hooks with experiment IDs and KPIs. Finally, it creates Lifecycle Management rules for refresh cadences, archival, and dependencies.

When to use it

Planning creative for multiple audience branches in a decision tree
Coordinating design, copy, legal, localization, and accessibility reviews
Versioning assets deployed across DAM, CMS, MAP, and CDN
Preparing variants for A/B tests and experiment tracking
Auditing live variants and sunsetting outdated experiences

Best practices

Assign unique, human-friendly IDs to every variant for analytics and rollback
Bundle related variants into kits aligned to customer journeys for governance
Require explicit approver signoffs for legal, localization, and accessibility before publish
Store canonical version IDs and CDN paths in the Asset Delivery record
Attach KPI guardrails and experiment IDs to each variant to simplify performance audit

Example use cases

Create a channel × persona variant matrix before a product launch to ensure coverage
Run a compliance-driven approval flow for international marketing campaigns
Link creative variants to experiment IDs and KPIs for systematic A/B testing
Audit and archive stale variants based on lifecycle rules and expiration dates
Package persona-specific variant kits for sales and customer success enablement

FAQ

How do I track which variant is in an experiment?

Include the experiment ID and KPI fields in the Testing Hooks section of the variant record. Tie impressions and conversions back to the variant unique ID.

What if a variant needs emergency rollback?

Use the unique variant ID and stored version/CDN path to revert to the prior approved asset and trigger the archival and notification steps defined in Lifecycle Management.