About content-variants
A marketing skill for cataloging and governing content variants across audiences, channels, and lifecycle stages. It organizes approvals, delivery references, testing details, and asset lifecycle records.
Key features
- 01Variant inventory and ownership
- 02Approval and compliance checklist
- 03Asset locations and version references
- 04Experiment IDs, KPIs, and guardrails
- 05Refresh and archival rules
Use cases
- 01Mapping creative assets to audience journeys
- 02Coordinating legal and localization reviews
- 03Auditing variant performance
- 04Retiring outdated content experiences
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/content-variantsin Claude Code to confirm it loaded.
Details
From the project READMEContent 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
- Variant Inventory – catalog base asset, variant name, audience, channel, owner, expiration.
- Approval Flow – document reviewers, compliance steps, localization, accessibility requirements.
- Asset Delivery – link storage locations (DAM, CMS, MAP) plus version IDs and CDN paths.
- Testing Hooks – note experiment IDs, KPIs, guardrails for each variant.
- 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-treesoutputs to ensure every branch has an approved asset.
Comments
Markdown supported