Product Description

---
name: product-description
description: "Write a product description / listing that sells and ranks. Use when asked to write a product description, e-commerce listing copy, a product page, or to rewrite a flat product blurb. Produces benefit-led listing copy — a hook, scannable feature→benefit bullets, specs, an SEO-aware title and keywords, and trust/again-objection elements — tuned to the buyer and channel."
homepage: https://mohitagw15856.github.io/pm-claude-skills/skill/product-description.html
metadata:
  {
    "openclaw": { "emoji": "🛒" }
  }
---

# Product Description Skill

Shoppers skim, then decide. A product description wins when it leads with the **benefit** (what changes for
the buyer), makes the value scannable, and answers the objection that would stop the "add to cart" — while
weaving in the search terms people actually type. This skill turns a spec sheet into copy that sells *and* gets
found.

## Working from a brief

Given just a product name and a few features, **write the full listing anyway** — infer the buyer, the
benefits, and likely keywords from the product type, and mark anything inferred *(assumed — confirm)*. Never
invent specs, materials, certifications, or claims (especially health/safety/efficacy) — leave those bracketed
to confirm. Never hand back questions instead of copy.

## Required Inputs

Ask for these only if they aren't already provided (else infer and label):

- **The product** — what it is, key features/specs, and what makes it different.
- **The buyer** — who it's for and the problem/desire it addresses.
- **Channel** — own store, Amazon/Etsy/marketplace, or social — and any format limits.
- **Voice & keywords** — brand tone, and target search terms if known.

## Output Format

### Product Listing: [product]

- **Title** — a scannable, SEO-aware product title (primary keyword + key attribute + differentiator), within the channel's length limit.
- **Hook** — 1–2 sentences leading with the core benefit, not the feature.
- **Why you'll love it** — 3–5 **feature → benefit** bullets (the feature in *italic-ish* lead, the benefit it delivers).
- **Description** — a short paragraph that paints the use/outcome and handles the main objection (fit, quality, value).
- **Specs** — a clean list/table of the concrete details (size, materials, what's in the box) — facts only.
- **Keywords** — a line of search terms woven in naturally (for the listing's keyword field / tags).
- **Trust elements** — what to surface near the buy button (guarantee, returns, shipping, social proof placeholder).

Mark any inferred spec/claim *(assumed — confirm)*.

## Quality Checks

- [ ] Leads with benefits; every feature is tied to what it does for the buyer
- [ ] Title is keyword-aware and within the channel's character limit
- [ ] Copy is scannable (bullets, short paragraphs) — not a wall of text
- [ ] The main purchase objection is addressed (fit/quality/value/returns)
- [ ] Keywords read naturally — no keyword stuffing
- [ ] No invented specs, materials, or health/safety/efficacy claims — inferred ones are flagged

## Anti-Patterns

- [ ] Do not list features without their benefit — "5000mAh battery" means nothing without "2 days without a charge"
- [ ] Do not keyword-stuff — it reads as spam and channels penalise it
- [ ] Do not invent specs or make unverifiable claims (waterproof, organic, FDA-approved) — flag to confirm
- [ ] Do not bury the value in a long paragraph — shoppers skim, lead with the hook and bullets
- [ ] Do not ignore the channel's limits (Amazon title/bullet lengths, etc.)

## Based On

E-commerce copywriting practice — benefit-led, scannable listings with feature-to-benefit translation, on-page SEO, and objection handling.