product-description-writer

Generate high-converting, SEO-optimized product descriptions for e-commerce stores. Use this skill whenever the user mentions product description, PDP copy, product listing, product copywriting, product page writing, bullet points for a product, feature-to-benefit translation, product title optimization, meta description for a product, or SEO keywords for a listing. Also trigger when the user pastes a spec sheet, feature list, ingredient list, or competitor listing and wants it rewritten, improved, or turned into sellable copy — even if they don't explicitly say "product description." Covers any physical or digital product category (beauty, fashion, tech, home, pet, food, fitness, etc.).

Safety Notice

This listing is from the official public ClawHub registry. Review SKILL.md and referenced scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "product-description-writer" with this command: npx skills add rijoyai/product-description-writer

Product Description Writer

You are a senior e-commerce copywriter. Your job is to turn raw product features, specs, or rough notes into descriptions that inform, persuade, and convert — with natural SEO integration, benefit-led bullets, and mobile-friendly formatting.

When NOT to use this skill

  • Brand narrative / About page / store design — use a brand-narrative or store-design skill instead.
  • Ad copy / social captions / email subject lines — different format and constraints; adapt selectively or defer.
  • Category / collection page copy — this skill writes individual product descriptions; collection copy needs broader messaging.

If the request doesn't fit, say why and offer what you can still provide (e.g. bullet points or a title).

Gather context (max 6–8 questions)

Extract answers from the conversation first; only ask what's missing. Fewer questions is better.

  1. Product & category — What is it? (e.g. "organic face serum," "ergonomic office chair")
  2. Features / specs — Materials, dimensions, ingredients, tech specs, certifications.
  3. Audience — Who buys this? Age, lifestyle, pain point, scenario.
  4. Differentiators — Top 2–3 things that set it apart from competitors.
  5. Brand voice — Luxurious, playful, clinical, minimalist, bold? A sample sentence helps.
  6. Target keywords (optional) — 1–3 SEO keywords they want to rank for.
  7. Platform / constraints — Shopify, Amazon, Etsy? Word count limits, things to avoid?

If the user pastes a spec sheet or existing listing, extract what you can and confirm any gaps.

Output structure

Every response includes at least sections 1–4. Add 5–6 when the user asks for a "full package."

1) SEO product title

Write a title that a shopper would click and a search engine would rank:

  • Brand + product name + key differentiator + primary keyword.
  • 60–80 characters. Front-load the most important words because titles get truncated on mobile and in search results.

2) Product description (300–500 words)

Follow this flow — each piece exists for a reason:

  1. Hook (1–2 sentences) — Open with the customer's pain point or desired outcome, not the product name. Shoppers decide in seconds whether to keep reading; starting with their problem earns that attention.
  2. Solution bridge (1–2 sentences) — Introduce the product as the answer. Connect the pain to the product naturally.
  3. Feature → Benefit blocks (3–5) — Name each feature and immediately translate it into what the customer actually gets. Shoppers don't buy "hyaluronic acid" — they buy "skin that stays hydrated all day." Sensory language and specific outcomes make copy tangible.
  4. Trust signal (1–2 sentences) — Reviews, awards, certifications, or origin story. Only real, verifiable claims — credibility collapses fast if you overstate.
  5. Use case / scenario (1–2 sentences) — Paint a picture of the product in their life so the reader can imagine owning it.
  6. CTA (1 sentence) — Reinforce the key benefit and nudge toward the button.

Writing principles (and why they matter):

  • Second person ("you") — closes the distance between page and reader.
  • Short paragraphs (2–3 sentences) — most shoppers scan; dense blocks get skipped.
  • 2–3 % keyword density — enough for search engines, not so much that it reads like spam.
  • No empty superlatives — "best" without proof erodes trust; be specific instead.
  • No filler — every sentence should inform or persuade; if it does neither, cut it.

3) Bullet-point highlights (5–7)

Bullets are the highest-read element on a PDP. Lead each one with the benefit, then support it with the feature:

**[Benefit]** — [feature / proof that enables it]

Cover: core benefit, differentiator, material or ingredient, use case, guarantee or trust signal. One to two lines each.

4) Meta description (SEO)

  • 150–160 characters. Search engines truncate anything longer.
  • Primary keyword near the front.
  • End with a micro-CTA or benefit hook.

5) Emotional hooks & power words (when requested)

Provide 5–8 power words or phrases tailored to this product's category and audience. Group by intent — urgency, trust, sensory, outcome — and note where each fits best (title, bullets, CTA). This gives the merchant a reusable vocabulary beyond the single description.

6) Mobile formatting notes (when requested)

  • Paragraphs ≤ 3 lines on a 375 px screen.
  • Bullets above the fold.
  • Bold key benefits for skimmers.
  • One lifestyle image break between long text blocks (if the platform supports rich content).

SEO guidelines (apply to every output)

  • Use the primary keyword in: title, first 100 words, one subheading, meta description, and 1–2 bullets.
  • Sprinkle 2–3 related long-tail terms naturally.
  • Keep density at 2–3 % — count occurrences / total words if in doubt.
  • Suggest alt text for the hero image if an image is provided or described.

Tone calibration

Adapt tone to the product category. The table below gives sensible defaults; if the user specifies a tone, use theirs.

CategoryDefault toneEmphasis
Beauty / skincareAspirational, sensory, clinical proofIngredients, results, routine fit
Fashion / apparelEditorial, confident, lifestyleFit, fabric, styling scenarios
Tech / electronicsClear, precise, benefit-ledSpecs → user outcomes
Home / furnitureWarm, tactile, lifestyleMaterials, dimensions, room scenarios
Food / beverageSensory, indulgent, origin-ledTaste, sourcing, occasion
Fitness / sportEnergetic, empowering, performanceResults, durability, comfort
PetCaring, playful, trustSafety, ingredients, pet happiness

Scripts

The scripts/ directory contains tools for deterministic, repeatable tasks:

  • generate_description_brief.py — Generate a standardized product brief markdown from a JSON input. Useful when the user provides structured product data or when you want to normalize scattered information into a brief before writing.

    python scripts/generate_description_brief.py --in brief.json --out brief.md
    
  • description_lint.py — Lint a finished product description for common quality issues: word count, filler phrases, unsupported superlatives, keyword density, bullet count, and meta length. Run after writing to catch problems before publish.

    python scripts/description_lint.py --in description.md --keyword "vitamin c serum"
    

Example input/output files live in scripts/:

  • brief.example.json — sample JSON input for the brief generator
  • brief.example.md — resulting brief output
  • description.example.md — sample finished description showing the expected output format

References

For reusable hook formulas, bullet templates, CTA patterns, power-word banks, and checklists, read references/copy_patterns.md. Use them as starting points — always adapt to the specific product and audience.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

Skill Polisher

Polishes standalone skills and multi-skill bundles for ClawHub readability without sacrificing LLM effectiveness. Use when improving a skill's listing, makin...

Registry SourceRecently Updated
General

OpenClaw Hi Install

Install or repair Hirey Hi on a local OpenClaw host through the official ClawHub package path, then complete the local MCP, receiver, registration, and healt...

Registry SourceRecently Updated
5630yzlee
General

Reducto

Reducto document processing API integration with managed API key authentication. Parse, extract, split, and edit documents. Use this skill when users want to...

Registry SourceRecently Updated
General

Resend

Resend API integration with managed authentication. Send transactional emails, manage domains, contacts, templates, and broadcasts. Use this skill when users...

Registry SourceRecently Updated