product-description-generator
E-commerce product description generator for any platform. Generates optimized titles, bullet points, descriptions, and backend keywords using competitor research + keyword scoring + FABE copywriting. Two modes: (A) Create โ generate listing from product specs with optional competitor analysis, (B) Optimize โ improve existing listing with keyword gap analysis. Supports Amazon, eBay, Walmart, Shopify, Etsy, TikTok Shop, Lazada, Shopee. No API key required. Use when: (1) writing a new product listing, (2) analyzing what makes competitors rank, (3) improving an underperforming listing.
What this skill does
# Product Description Generator ๐ Generate platform-optimized product copy โ titles, bullet points, descriptions, and backend keywords โ for any major e-commerce platform. No API key required. ## Installation ```bash npx skills add nexscope-ai/eCommerce-Skills --skill product-description-generator -g ``` > **For Amazon listings**, use our dedicated skill with Cosmo algorithm optimization: > ```bash > npx skills add nexscope-ai/Amazon-Skills --skill amazon-listing-optimization -g > ``` > See: [amazon-listing-optimization](https://github.com/nexscope-ai/Amazon-Skills/tree/main/amazon-listing-optimization) ## Two Modes | Mode | When to Use | Input | |------|-------------|-------| | **A โ Create** | Writing a new listing | Product specs + optional competitor URLs | | **B โ Optimize** | Improving existing listing | Current listing or URL + optional competitor URLs | Both modes support competitor analysis โ just include competitor URLs to enable it. ## Supported Platforms | Platform | Output Components | |----------|-------------------| | **Amazon** | Title (โค200) + 5 Bullets (โค500 each) + Description (โค2000) + Backend (โค250 bytes) | | **eBay** | Title (โค80) + HTML Description | | **Walmart** | Title (โค75) + Short Desc (โค150) + 10 Features + Long Desc | | **Shopify/DTC** | SEO Title (โค60) + Meta Desc (โค160) + Product Description | | **Etsy** | Title (โค140) + Description + 13 Tags (โค20 each) | | **TikTok Shop** | Title (โค255) + Description (โค1000) | | **Lazada/Shopee** | Title (โค120) + 5 Highlights + Description | ## Usage Examples ### Mode A โ Create ``` Create a listing for my yoga mat on eBay UK. Competitors: https://www.ebay.co.uk/itm/123456789, https://www.ebay.co.uk/itm/987654321 My product: 6mm TPE, non-slip, carrying strap included. Brand: ZenMat. Tone: Friendly. ``` ``` Platform: Etsy. Product: hand-poured soy candle, lavender scent, 8oz glass jar, 40-hour burn time. Target audience: gift buyers. Tone: Luxury. ``` ### Mode B โ Optimize ``` Optimize this Shopify listing: https://mystore.com/products/portable-blender Beat these competitors: https://amazon.com/dp/B09V3KXJPB, https://walmart.com/ip/123456 ``` ``` Find keyword gaps and rewrite this Etsy listing: [paste current title, description, and tags] ``` --- ## Handling Incomplete Input If user doesn't provide enough info, ask upfront: ``` To generate your listing, I need: **Required:** - Platform (eBay / Walmart / Shopify / Etsy / TikTok Shop / Lazada / Shopee) - Product name and key features - Brand name **Recommended (better results):** - 1-3 competitor URLs to analyze - Target audience - Tone preference (Professional / Friendly / Urgent / Luxury) Which mode? - **A โ Create**: I'm writing a new listing from scratch - **B โ Optimize**: I have an existing listing to improve ๐ก For Amazon listings, I recommend using [amazon-listing-optimization](https://github.com/nexscope-ai/Amazon-Skills/tree/main/amazon-listing-optimization) โ it's optimized for Amazon's Cosmo algorithm. ``` --- ## Mode A Workflow โ Create New Listing ### Step 1: Collect Product Info | Field | Required | Example | |-------|----------|---------| | `product_name` | โ | Portable blender | | `platform` | โ | Etsy | | `brand` | โ | BlendJet | | `key_features` | โ | USB-C, 6 blades, BPA-free | | `specs` | โ | 380ml, 175W motor | | `target_audience` | ๐ | Gym-goers, travelers | | `use_cases` | ๐ | Smoothies, protein shakes | | `competitor_urls` | ๐ | 1-3 URLs to analyze | | `tone` | Optional | Professional (default) / Friendly / Luxury / Urgent | ### Step 2: Gather Keywords **If competitor URLs provided:** 1. Fetch each competitor page: ``` Use web_fetch on each competitor URL. Extract: title, bullets/features, description, price, review count, brand name. ``` 2. If `web_fetch` fails or returns incomplete data: ``` Fallback: web_search for "[product title from URL]" site:[platform].com Extract data from search snippets. ``` 3. Parse competitor content and extract keywords in these categories: - **Product-type terms**: What it IS (yoga mat, exercise mat) - **Feature terms**: What it DOES (non-slip, eco-friendly) - **Use-case terms**: WHERE/WHEN used (home gym, yoga studio) - **Audience terms**: WHO buys (beginners, athletes) - **Attribute terms**: Specs (6mm, TPE material) 4. Expand beyond competitors: ``` web_search: "[product type]" best seller features what buyers want web_search: "[product type]" review complaints common issues web_search: site:[platform].com "[product type]" ``` **If no competitor URLs provided:** 1. Discover keywords via web search: ``` web_search: "[product name]" best seller [platform] features web_search: "[product name]" review what customers love web_search: "[product name]" vs alternatives comparison web_search: site:[platform].com "[product name]" ``` 2. Extract keywords from top 5 results following the same categories above. โ ๏ธ **Critical**: Remove all competitor brand names โ never include them in output. ### Step 3: Score and Prioritize Keywords Score each keyword (1-9 points): | Dimension | Scoring | |-----------|---------| | **Frequency** | In 3+ competitor titles = 3 pts / In 1-2 = 2 pts / Bullets only = 1 pt | | **Relevance** | Core descriptor = 3 pts / Feature = 2 pts / Peripheral = 1 pt | | **Opportunity** | Few competitors use = 3 pts / Most use = 2 pts / All use = 1 pt | Assign to tiers: ``` ๐ด Primary (7-9 pts) โ Title ๐ก Secondary (4-6 pts) โ Bullets / Features ๐ข Tertiary (2-3 pts) โ Description โช Backend (1 pt) โ Tags / Search Terms ``` ### Step 4: Generate Copy Proceed to **Generate Copy** section. --- ## Mode B Workflow โ Optimize Existing Listing ### Step 1: Analyze Current Listing User may provide: - **Full listing copy** (title, bullets, description pasted directly) - **Product URL** (e.g., `https://www.etsy.com/listing/123456`) - **Platform + product identifier** (e.g., "Etsy listing 123456") **If user provides URL or identifier only:** ``` Use web_fetch on the provided URL. Extract: current title, bullets/features, description, tags (if visible), price. ``` If `web_fetch` fails: ``` Fallback: web_search for the product title or identifier. Ask user to paste the listing content manually if data is incomplete. ``` **Once listing content is obtained**, parse and extract: - All keywords currently present - Structure and format used - Obvious gaps (missing features, weak benefits, no FABE structure) ### Step 2: Gather Target Keywords **If competitor URLs provided:** Follow the same competitor analysis process as Mode A Step 2: 1. `web_fetch` each competitor URL 2. Extract their keywords 3. Expand via web search **If no competitor URLs provided:** Discover ideal keywords for the product type: ``` web_search: "[product type]" top keywords [platform] 2024 2025 web_search: "[product type]" best seller features web_search: site:[platform].com "[product type]" top listings ``` ### Step 3: Gap Analysis Compare current keywords vs. target keywords: ``` ## Keyword Gap Analysis ### โ Keywords You Already Have | Keyword | Title | Bullets | Description | |---------|-------|---------|-------------| | yoga mat | โ | โ | โ | | exercise mat | โ | โ | โ | ### โ Keywords You're Missing | Keyword | Priority | Recommendation | |---------|----------|----------------| | non-slip | ๐ด High | Add to title | | eco-friendly | ๐ก Medium | Add to bullet 2 | | extra thick | ๐ก Medium | Add to bullet 3 | Current Coverage: 12/20 keywords (60%) Target Coverage: 90%+ ``` ### Step 4: Rewrite Generate optimized copy incorporating missing keywords. Show **Before โ After** for each component. Proceed to **Generate Copy** section. --- ## Generate Copy Final step for all modes after keyword priority table is built. ### Writing Framework: FABE Apply to every bullet: ``` F โ Feature: What the product HAS or DOES A โ Advantage: Why this is BETTER than alternatives B โ Benef
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product โ visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".