跳到主要内容
知仓学习社ZHICANG

product-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, …

不碰外部(只输出文字)无严重或高危命中mohitagw15856/pm-claude-skills

它会碰到什么

扫了多少1 个文本文件,4 KB
它会碰到什么不碰外部(只输出文字)
命中总数0 处
命中统计严重 0 · 高 0 · 中 0 · 低 0

这一栏是扫描器报的事实,不是结论。命中多不等于有毒(安全工具、规则库、示例脚本本来就会包含危险写法),命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系,需要你自己看。

技能内容

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.

想直接用这个技能?

本站把开放许可(MIT / Apache 等)的技能按仓库打包整理到网盘,点一下转存到你自己的网盘,不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接,不打包。

同名技能的其他版本

有 3 个不同仓库或目录里都有叫 product-description 的技能。它们内容并不相同,别混用: