product-descriptions
Skill1 starsChanged 20 days agoMITView on GitHub
Write or rewrite Shopify product descriptions, plus SEO title and meta description. Use when the user shares product details, an existing description, a product URL or photos.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- tesslagoblin/fashion-brand-claude-skillstheir own version, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- tesslagoblin/fashion-brand-claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- cod-rto-analysisSkill
- dead-stock-clearanceSkill
- demand-plannerSkill
- returns-reason-analysisSkill
- true-profitSkill
- weekly-kpi-digestSkill
- catalog-photoshootSkill
- conversion-optimiserSkill
- shopify-catalog-uploadSkill
- size-chart-builderSkill
- angry-customer-replySkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Write a product description a shopper takes in at a glance, which answers the questions they would otherwise email about, plus the SEO …
- Distinctive: line 37
Leave the price out. Shopify shows it beside the description.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Product Descriptions
Write a product description a shopper takes in at a glance, which answers the questions they would otherwise email about, plus the SEO fields. Every fact in it comes from the user.
1. Get the facts
Take what the user gave you (details, an old description, a product page, photos). Then ask once, in one message, for whatever is missing from this list:
- What it is, and what's in the box.
- The specs shoppers check: size or dimensions, materials, capacity, compatibility, care.
- Who buys it and why: the job it does for them.
- Voice: two or three of the store's existing descriptions to match, or a few words ("playful", "no-nonsense").
Any spec you still lack goes in a square-bracket placeholder such as [WIDTH]. A photo shows colour and shape but not size or material, so ask for those.
Done when: you have the facts, or each gap is a placeholder.
2. Write the description
Shape:
- Opening line: what the shopper gets, in their words. It's the headline most shoppers read, so it carries the sale. Spend it on the benefit, since the product title already sits right above it.
- 3 to 5 bullet points, each one benefit first, then the fact that proves it: "Keeps drinks cold for 24 hours (double-wall steel)".
- The details paragraph: the practical answers people email about. Size and fit, care, what's in the box, and any delivery or personalisation notes the user mentioned. Every question this paragraph answers is one less support email.
Style:
- 80 to 150 words for most products. Go longer only for expensive or technical products, where shoppers compare specs.
- Concrete over grand: "holds a 15-inch laptop" beats "spacious". Every adjective is backed by a fact.
- Second person ("you"), present tense, and the store's spelling (UK or US).
- Match the voice examples when given; otherwise plain and warm.
- Leave the price out. Shopify shows it beside the description.
Where a claim is regulated (health, supplements, cosmetics, food, children's products), use only the claims the user supplied, word for word, and flag them in the notes.
3. Write the SEO fields
These go in the Search engine listing section at the bottom of Shopify's product editor.
- Page title: under 60 characters, so Google shows it in full. The product type plus the main thing that sets it apart, then
| [STORE NAME]if it fits. - Meta description: under 155 characters. The two or three facts a searcher compares on, as a plain sentence.
Done when: you have counted the characters in both fields, both are under their limits, and every fact in them also appears in the description.
4. Hand it over
Give, in this order: the description, the page title, the meta description, then a short Before you publish list of placeholders to fill and claims to check.
Format the description as plain text with bullet points, which pastes cleanly into Shopify's description box. If the user asks for HTML (for the code view or a CSV import), use only <p>, <ul>, <li> and <strong>.
For several products, write the first one and ask whether the voice and length are right. Then write the rest in the same shape.
Example
User: Ceramic pour-over coffee dripper. Makes 1 to 4 cups. Takes size 02 paper filters. Dishwasher safe. Handmade in Portugal, so the glaze varies. £34. Our customers are people getting into specialty coffee.
Description:
Make café-style pour-over coffee at home, with a dripper made by hand in Portugal.
- Makes 1 to 4 cups, so it suits a quiet morning or a pot for friends
- Takes standard size 02 paper filters
- Dishwasher safe, so cleaning up is easy
- Handmade, so every glaze is a little different
Because each dripper is glazed by hand, yours won't match the photo exactly. It measures [BASE DIAMETER] across the base, so check it sits on your mug or carafe before you buy.
Page title: Handmade Ceramic Pour-Over Coffee Dripper (41 characters)
Meta description: Handmade in Portugal. Brews 1 to 4 cups, takes size 02 filters and goes in the dishwasher. Every glaze is one of a kind. (120 characters)
Before you publish:
- Fill in
[BASE DIAMETER].
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

