Individual skill

variant-copy-scaler

Generates distinct, on-brand copy for every size, color, and bundle variant from a single master description, splitting a shared core from a thin per-variant layer so variant pages avoid thin or duplicate-content problems. Use when someone asks "write descriptions for all 12 colorways", "our variant pages are cannibalizing each other", "should each SKU get its own page", or when one product ships in many variants and needs per-variant PDP copy, or near-identical variant pages are creating duplicate-content or canonical problems. Do NOT use to write the single master or parent PDP description from specs - use product-description-writer instead; do NOT use for category or collection page copy - use category-page-copywriter instead.

skills/variant-copy-scaler/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 6, 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)
24
Repository last updated
Oct 13, 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

# Variant Copy Scaler

Scale one master product description across many variants so each page is distinct enough to rank and to answer "is THIS the one I want," without rewriting the brand story per SKU. The costly mistake this prevents is twofold: thin near-duplicate pages that compete with each other and dilute authority, and the wasted effort of hand-writing thirty full descriptions when only 20% of each page should differ.

## Operating procedure

The order is strict: the indexing decision comes before any copy, because consolidation makes per-variant copy unnecessary and writing it first wastes the work.

### Step 1: Gather inputs

- The master description (the parent PDP copy). If it does not exist, stop and route to product-description-writer first.
- The full variant matrix: every color, size, and bundle, with SKU and any attribute that genuinely differs (dimensions, weight, price, materials).
- Platform behavior: does each variant mint a separate indexable URL, or does one URL serve all variants via a selector?
- Brand voice constraints, if documented.