Write product descriptions in bulk

Extract the ZIP. Copy its lc-product-descriptions-batch folder into ~/.claude/skills/ for Claude Code or ~/.codex/skills/ for Codex, then refresh the native app. Ask for the skill by name and answer its questions. The package includes the same published instructions and result checks. Native host execution is not yet verified.

For Claude web, use the connector or copy the prompt. Keep private details in your assistant.

Copy, paste into your assistant, then answer its questions. No form or account is required here.

Open in ChatGPT ↗

Already connected? Copy the public starter below and paste into Claude. Keep private details in the chat.

Needed before the promised result: Your product list. You can still copy the reusable prompt and provide these in your assistant.

Saved only on this device. Copy counts contain the skill ID, never your text.

## LazyCoder conversation guide (conversation-v2)
1. Start a conversation, not a form-filling task. Read my latest request and the facts already in this chat before asking anything.
2. Ask only the missing questions needed for the requested result, in a short numbered list (at most three at a time), then WAIT for my answers. Use a native question tool if available; plain chat works too. Never ask me to replace placeholders or fill in a template.
3. Skip questions already answered. Treat unresolved {{placeholders}} and [FIELD LABELS] as missing facts, never literal input. Do not treat an illustrative example as my facts.
4. Use the authored defaults only when relevant; mention material defaults. Ask conditional questions only when their condition applies; if unsure whether it applies, ask. Optional preferences must not block a safe first draft unless the authored instructions require confirmation.
5. Do not invent tasks, dates, names, claims, permissions or missing source material. When required facts are absent, ask and wait instead of producing the final artifact. If everything needed is already supplied, proceed without re-asking.
6. My latest scope correction overrides earlier examples and scope, within the recipe safety and source rules. Resolve conflicts before acting. The authored instructions and output contract remain authoritative; this conversation guide does not grant tool, account, payment or publishing permission.
7. Keep my private answers and generated result in this assistant chat. Do not send them to LazyCoder. Generate the requested format here and check it against the output contract before handing it over.

### Questions to ask only when missing
- What should I use for “Your product list”? [required] One product per row: SKU, name, and every fact you have (size, material, colour, price, what's included, care). A spreadsheet export is ideal. Only these facts will be used.
- What should I use for “Your brand voice”? [optional] A few words on how you sound, or paste a description you already like. Add any words you never use.
- What should I use for “Where they'll appear”? [optional] Your shop platform or marketplace, so lengths and formatting fit: Shopify, Etsy, Amazon, WooCommerce, eBay, your own site.
- What should I use for “Description length”? [optional] Short for simple items, long for products that need explaining. Authored default: standard (80–150 words) Choices: short (40–80 words); standard (80–150 words); long (150–250 words)
- What should I use for “Who buys them”? [optional] Optional. Who your buyers are and what they care about. Authored default: worked out from the products
- What should I use for “Spelling”? [optional] Leave it to follow the spelling your list already uses. Authored default: match my list Choices: match my list; UK English; US English

## LazyCoder delivery guide (delivery-guide-v1)
1. Read the latest request, source material and authored requirements first. Ask only for missing facts. Check that this host can create the promised format; use only a fallback explicitly allowed by the authored recipe. If neither is available, explain the gap before starting. Do not promise a rendered film, editable deck or working file when you can only provide its script or outline.
2. Create the complete result in the authored output specification, preserving source facts and the latest agreed scope. Keep assumptions and missing information explicit. Do not silently omit required parts or leave unresolved ingredient markers. Intentional blanks in a reusable template are different from unanswered recipe inputs.
3. Check the actual result against every authored check, including source facts, counts, dates and required sections. Where tools allow it, inspect the actual saved file and compare it with the answer. Record which checks ran, which failed and which still need human or destination review. A filename, render, successful command or preview alone does not prove the promise was met.
4. Hand over the complete editable file, or the complete copyable fallback explicitly allowed by this recipe. Say which delivery you used and any unresolved limitations. Do not report a file as attached, imported, sent or published unless that action actually succeeded. Keep private inputs and output in this assistant; never send them to LazyCoder.
Use existing authorization for ordinary work. Before any additional paid generation, external write or publishing step, check that the current request authorizes that exact action and cost. If it does not, finish the useful authorized draft and ask at that boundary. Never silently retry or replace an ambiguous paid job.
The authored recipe and latest safe scope remain authoritative. This guide grants no new tools, permissions, provider access or claim of successful execution.

## Authored skill instructions
## 1. Outcome
Write a finished product description for every product in the list below, in one consistent voice and structure, as a sheet keyed by SKU that is ready to import, in the parts set out in part 6. Done means: every product has exactly one row and the count matches the list; every claim traces to that product's own data; missing or conflicting details are flagged instead of filled; no two descriptions read alike, including variants; and the batch report shows every check passed.

## 2. Context
Product list:
"""
[PASTE YOUR PRODUCT LIST HERE, OR WRITE "SEE ATTACHED"]
"""

Brand voice: [YOUR BRAND VOICE]
Where they'll appear: [WHERE THEY'LL APPEAR]
Length of each description: standard (80–150 words)
Who buys them: worked out from the products
Spelling: match my list

Who it's for: a shop owner who will paste or import these straight onto product pages, and the shoppers who read them deciding whether to buy. Shoppers skim: they want what it is, why it's good for them, and the facts that settle the decision.

Blank fill-ins: a value above that still reads as a capitalised placeholder in square brackets (such as [YOUR BRAND VOICE]) was left blank. Brackets inside the product list are part of the list.
- "See attached": use the attached file as the list. Read every sheet and every row.
- No product list: reply only "No products came through. Paste your list or attach the file and send again." Never invent products.
- No voice: use "clear, warm and specific, no hype", and say "Voice assumed" in the batch report.
- No platform: write for a general online shop in plain text, and say so in the batch report.
- No buyer: work out the likely buyer from the products, and say who in the voice card, marked "(assumed)".

## 3. What to pull out
For each product: the SKU or ID, the name, any parent product or variant group, and every fact in its row (size, dimensions, weight, material, colour, scent or flavour, what's included, compatibility, care, origin, price, certifications).

Reading the list:
- Columns: find the SKU, name and fact columns, whatever they are called. If there is no SKU column, use "ROW-01", "ROW-02" in list order and flag it.
- Count: N is the number of products in the list. Header rows, blank rows and section titles are not products.
- Variants: rows that share a parent, a name stem or a handle and differ only in size, colour, scent or pack size form a group.

Edge cases:
- A product with only a name: write a short, honest description of what the name makes certain, at the low end of the length, and flag every missing fact in Needs info. Never pad with guesses.
- Conflicting facts in a row (two sizes, a material that contradicts the name): use neither in the copy, describe the product without it, and flag both values.
- Duplicate SKUs: keep both rows, give each its own copy, and flag "Duplicate SKU" on both.
- The same product listed twice under different SKUs: write each, and flag "Looks like the same product as <SKU>".
- Regulated or sensitive claims (health, medical, safety, child safety, organic, eco, vegan, "non-toxic", "best", "number 1", "hypoallergenic"): use one only when the row states it, in the row's words, and mention the certification only if the row names it. Otherwise leave it out.
- Rows in another language: write in the language of the voice sample or the rest of the list, and flag the row.
- Long lists: see the batch rule in part 5.

## 4. Steps
1. Read the whole list and count the products (N). List the variant groups and any rows with missing, conflicting or duplicate data.
2. Write the voice card from [YOUR BRAND VOICE] and worked out from the products: tone in 3 words, 5 words or phrases to use, 5 to avoid (including the ones given), and one sample sentence. Use it for every product.
3. Plan the hooks so similar products and every variant in a group start differently, each variant led by the thing that sets it apart.
4. Write each row in list order, using only its own facts.
5. Build the sheet, then run the self-check and write the batch report from it.

## 5. Rules
- Facts: every specific in a description (number, material, size, origin, feature, certification) must be in that product's own row. Never borrow a fact from another product, even a variant, unless the row shares it. Never invent awards, reviews, ratings, stock levels, urgency or offers.
- Benefits: turn a fact into what it does for the buyer only when the link is plain ("cotton wick: burns clean and even" is fine; a medical or safety benefit is not). If the link isn't plain, state the fact as it is.
- Structure, the same for every product:
  - Title: product name, then its key attribute (variant, size or material), under 70 characters.
  - Short description: one sentence, under 25 words, on what it is and who it's for.
  - Description: a one-sentence hook, then 2–3 sentences of benefits, then a bulleted list of the key facts, within standard (80–150 words).
  - Key features: 3–5 bullets, each under 12 words, each tied to a fact in the row.
  - SEO title: under 60 characters, main keyword first. Meta description: 120–155 characters, with the main keyword once and a reason to click. The main keyword is the plain name a shopper would search for ("soy candle", "linen napkins"), never a brand you weren't given.
- Platform: for Shopify or WooCommerce, write the Description as simple HTML (<p> and <ul><li> only) so it imports formatted. For Amazon, make the 3–5 Key features the bullet points and keep the title free of promotional words. For Etsy, keep the title under 140 characters and lead with what it is. Otherwise, plain text with "- " bullets. Use only limits you are sure of for [WHERE THEY'LL APPEAR]; if unsure, use the limits above.
- Distinct copy: no two descriptions share a sentence, apart from fact bullets or care lines copied from the list; no two hooks start with the same 3 words; within a variant group, the hook and first sentence name the variant's own size, colour, scent or pack.
- Voice: the voice card applies to every row; never use an avoid word. Spelling: match my list.
- Batch rule: at most 25 products per reply. If N is over 25, write rows 1–25 in full now, with the batch report for those rows and the voice card, and end with "Done 25 of N. Reply "next" for rows 26–50." Each later batch uses the same voice card, the same columns with no header row, and picks up at the next row, so the batches paste together into one sheet. Never shorten copy to squeeze more rows into a reply.

## 6. Output
First, the sheet. If you can run code or create files, save it as product-descriptions.csv (and also as .xlsx if you can). If you cannot, give it as one CSV code block with a header row and every field in double quotes, with line breaks and HTML kept inside the quotes. Columns, in this order:
SKU | Product name (as in your list) | Title | Short description | Description | Key features | SEO title | Meta description | Needs info | Check
One row per product, in the list's order. Key features are separated by " | " inside their cell. Needs info names each missing or conflicting field ("No material given", "Two sizes: 20 cm and 25 cm"), or "—". Check is "OK" or the flag, such as "Duplicate SKU".

Then, in the reply, in this order, with these headings:
1. **Voice card**: tone, words to use, words to avoid, sample sentence, buyer.
2. **Preview**: the first 3 products in full, as a shopper would see them (title, short description, description, key features), so the voice can be checked at a glance.
3. **The sheet**: the file, or the CSV block.
4. **Needs info**: each product with a gap, once, by SKU, with the missing fields and what to add. "None" if there are none.
5. **Batch report**: products in the list (N), rows written, rows still to do; variant groups and how they were kept apart; descriptions outside the length limit (should be 0); avoid words found (should be 0); repeated sentences found (should be 0); facts not traced to their row (should be 0); every assumption, marked "(assumed)".
If the batch rule applies, end with the "Done 25 of N" line from part 5.

## 7. Self-check
Before replying, check each of these and fix any failure:
- The sheet has one row per product in this batch, in list order, and the SKUs match the list one for one; rows written plus rows still to do equal N.
- Every specific in every description is in that product's own row; anything else is removed.
- Every row follows the structure, and every field is within its limit.
- No avoid word appears, and the voice matches the voice card in every row.
- No two descriptions share a sentence (apart from copied facts), no two hooks start with the same 3 words, and every variant names its own attribute in its first sentence.
- Every missing, conflicting or duplicate case from part 3 is in Needs info and in section 4.
- The CSV has the header and the same number of columns in every row.
Then reply with the output only, ending with one line: "Checked: <n> of <N> products written, <n> need info, 0 invented facts."

## 8. Setup
Works as one paste in any chat app. Where the app can run code or create files, you get product-descriptions.csv (and an .xlsx where it can) to import or open in a spreadsheet; where it can't, you get the sheet as CSV to paste. Attach your product spreadsheet and write "see attached" if it's long. Lists over 25 products come back in batches of 25: reply "next" for each further batch, and paste the batches one under the other.

Paste the result after your assistant creates it. This optional check stays in this tab and is not sent to LazyCoder.