smithery.ai

content-variants

Use when planning, approving, and versioning personalized creative assets.

First seen Mar 26, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,348 B
  • docs SUMMARY.md 98 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

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.