Skip to content
Back to skills

Product Copy

ASecurity

Use when writing or rewriting a product description, product title, benefit list, feature bullets, or on-page product messaging for an online store — e.g. "write a description for this product", "rewrite my product copy", "how many benefits should I list", "should I say 500g or 25 servings", "name this color", "should we mention it's lab-tested".

  • 2 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 19, 2026
ai-agentsgo

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned October 19, 2026

npx -y skills add checkout-page/ecommerce-skills --skill product-copy --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Product Copy?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Product Copy
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/checkout-page-product-copy/badge)](https://www.skillsdirectory.com/skills/checkout-page-product-copy)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: product-copy
description: Use when writing or rewriting a product description, product title, benefit list, feature bullets, or on-page product messaging for an online store — e.g. "write a description for this product", "rewrite my product copy", "how many benefits should I list", "should I say 500g or 25 servings", "name this color", "should we mention it's lab-tested".
---

# Product copy

Write product descriptions that people find persuasive, easy to grasp, and worth paying more for. The rules change how copy is *structured* and *measured* — number of claims, units, names, register — which move purchase intent and willingness to pay more than adjectives do.

## When to use

- Writing or rewriting a description, title, bullets, or hero message
- Choosing which features to mention, how many, in what units and register

## When not to use

- Auditing the whole page → `product-page`; photo/video direction → `product-visuals`
- Discount or promotion wording → `discounts` / `promotions`

## Inputs

Collect, or state your assumption:

- Product facts: materials, quantity, specs, ingredients or components (any branded?)
- The full list of candidate benefits
- Audience and how technical they are
- Where the copy sits and the length limit

> **Classify the product first.** *Hedonic* = bought for enjoyment, pleasure, or the experience (chocolate, fashion, decor, travel, spa, perfume). *Utilitarian* = bought to do a job, judged on function and value (detergent, appliances, insect repellent, tools, accounting software). If it's mixed, decide by what the buyer is optimizing for at the moment of purchase.

## Procedure

1. **Pick three claims.** Rank the benefits; keep the top three (three claims were 10.4% more persuasive than four; skepticism starts at the fourth). Move the rest to a spec table.
2. **Best features only.** Don't pad with merely good features — the impression sinks to the weakest claim.
3. **Units people use.** Uses or pieces (30 washes, 8 cans), not standardized measures (750 g, 96 oz). Raises product evaluations and willingness to pay.
4. **Smaller units for precision.** Drop to the next unit down: 180 seconds, not 3 minutes; 180 minutes, not 3 hours; 32 oz, not a quarter gallon. Reads more precise and credible; strongest for time.
5. **Evocative color names.** "Midday sky blue", not "light blue".
6. **Feature branded components.** A branded ingredient or part (Gore-Tex, a licensed enzyme blend) goes up front; demand up to 40% higher. †
7. **Register by product type.** Utilitarian → science and effectiveness language works. Hedonic → avoid it ("lab-formulated" on a treat: up to 30% less likely to be chosen). †
8. **Plain language.** Unknown terms make the product seem worse and pricier; define or drop. †
9. **Describe touch** where feel matters (textiles, skincare) — the top online clothing pain point.
10. **Rational up, emotional down** in vertical layouts.
11. **Frame as an experience** (coffee with friends, not bean origin) when you want reviews. †

## Output

1. Headline and body within the length limit.
2. Rules table:

| Rule | Where |
|---|---|
| Three claims | stain removal, cold water, gentle on skin |
| Intuitive units | "30 washes" for "750 g" |
| Branded ingredient | licensed enzyme blend, first sentence |

3. What was cut and where it can go.

## Common mistakes

- Working every supplied benefit in — six benefits read as a pitch; pick three.
- Leading with pack weight or volume — lead with uses.
- Keeping the supplier's color name.
- "Lab-tested" on a hedonic product.

## Quick reference

| Element | Rule |
|---|---|
| Claims | Exactly three, best only |
| Quantity | Uses/pieces, not grams/ounces |
| Precision | Smaller unit |
| Colors | Evocative names |
| Components | Name the brand |
| Register | Science only if utilitarian |
| Vocabulary | Plain |
| Texture | Describe if feel matters |
| Layout | Rational up, emotional down |

† No primary citation on file for this rule — a practitioner tip, not a measured finding.

Evidence and effect sizes: see [reference.md](reference.md).

Files in this skill

  • SKILL.md4 KB
  • reference.md5.8 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.