Product description writer
Writes the single on-site PDP master copy - a benefit-led, scannable product detail page in the brand's voice - from a raw spec sheet or feature list. Use when you have a spec list, feature bullets, or a bare template description for one product and need conversion copy for its on-site product detail page. Do NOT use for Amazon or marketplace listings - use amazon-listing-optimizer instead; do NOT use to spin one master into many size/color variants - use variant-copy-scaler instead.From its SKILL.md
npx -y skills add SkillMedev/skills --skill product-description-writerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.5 KB, 706 tokens by cl100k_base, as published. Nobody here has run it
Product Description Writer
Translate a product's specs into the on-site PDP master copy: benefit-led, scannable, in the brand's voice, decidable in eight seconds on a phone.
Workflow
- Gather inputs. Get the spec/feature list, the target customer, and the brand voice. If voice is unknown, infer it from the category and ask exactly one calibrating question. If the spec list is thin, ask for the one detail competitors omit - do not pad with fluff.
- Find the one reason they buy. Name the core transformation or job-to-be-done, not the product category ("slices a ripe tomato without crushing it," not "knife"). This is the lead hook.
- Translate each spec to a benefit. For every spec write feature + "which means" + benefit ("316 stainless steel, which means it won't rust in a salt-air bathroom"). Keep the spec for credibility, the benefit for desire. Drop any feature that translates to nothing the buyer cares about.
- Surface and answer objections. Name the silent doubt - sizing, fit, durability, returns, "will this work for me" - and give one reassuring line each, woven into bullets or a short "Good to know" note. If it runs small, say so.
- Assemble for the F-pattern scan. Open with the lead hook, then a 2-3 sentence intro, then 3-5 benefit bullets with the payoff word front-loaded and the first 2-4 words bold. Close with a benefit-restating CTA. Put a "Details" or "Specs" block at the bottom for literal numbers, dimensions, materials, and care.
- Calibrate voice. Match sentence length, vocabulary, and warmth to the brand (premium skincare is calm and precise; a snack brand is playful).
Quality bar
- The first line works as a standalone hook - many shoppers read nothing else.
- Every benefit traces to a spec in the source; every spec that survives earns its place.
- Sentences stay under 20 words; bullets front-load the payoff.
- Spec-hunters can find every literal number in the Details block without it cluttering the sell.
- Every objection a buyer would have before adding to cart is answered honestly.
Deliverable
Produce the complete PDP master copy as one paste-ready block: lead hook line, 2-3 sentence intro, 3-5 benefit bullets (payoff front-loaded, opening words bold), objection-handling lines or a "Good to know" note, a benefit-restating CTA, and the Details/Specs block with every literal number, dimension, material, and care instruction from the source. Flag any spec you dropped and why, and any claim you could not support from the inputs.
Do NOT
- Do not invent performance numbers, certifications, materials, or health/safety/earnings claims. Use only what the source provides; if asked to claim an outcome the source doesn't support, refuse and offer a compliant alternative.
- Do not open with "premium quality" or any generic category claim.
- Do not fabricate scarcity, countdowns, or low-stock urgency. Use urgency only when it is true (limited batch, seasonal, real low stock).
- Do not keep features that translate to no buyer benefit.
- Do not end with a bare "Buy now" - restate the benefit in the CTA.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most docs writing skills give in 706 tokens
Counted across 1,637 of the 3,044 authors here whose files we hold, read 2026-08-07
- Announce the skill at startin 54 of 1637, across 26 files
- Convert legacy doc files before editingin 45 of 1637, across 7 files
- Predict questions readers might askin 42 of 1637, across 4 files
- Generate clarifying questions for initial contextin 42 of 1637, across 3 files
- Create document scaffold with placeholder textin 42 of 1637, across 3 files
- Brainstorm content options for each sectionin 42 of 1637, across 3 files
- Test the document with a fresh context-less instancein 42 of 1637, across 3 files
- Include exact file paths in every taskin 42 of 1637, across 15 files
- Ask interview questions one at a timein 42 of 1637, across 27 files
- Apply surgical edits during refinementin 41 of 1637, across 2 files
- Offer structured workflow or freeformin 40 of 1637, across 1 file
- Ask for document meta-contextin 40 of 1637, across 2 files
Said here and by no other author read
- ask one calibrating question if voice is unknown
- ask for one omitted detail if specs are thin
- name the core transformation as the lead hook
- translate every spec using a benefit format
- drop features that translate to no buyer benefit
- surface and answer buyer objections honestly
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.