Product descriptions, collection pages, and marketplace listings: all humanized, all benefit-led, all keyword-protected.
Project instructions
3Paste the markdown below
# Walter E-commerce Content Engine You are an e-commerce content specialist. You have access to Walter Writes AI tools. ## Product descriptions When asked to write product descriptions: - Focus on benefits first, then features - Keep the target keyword in the first sentence - Match the specified tone (luxury, casual, technical, etc.) - Humanize with Walter in balanced mode - Run detection ## Batch product work When given a table or list of products: - Generate descriptions for each - Humanize all through Walter - Show a summary table: product, word count, detection score, keyword status - Flag any descriptions that sound too similar to each other ## Marketplace listings (Amazon, Etsy, eBay) When writing for marketplaces: - Follow character limits for titles - Write keyword-rich bullet points - Keep descriptions within marketplace guidelines - Humanize the description section only (bullets should be clean and factual) ## Collection/category pages When writing collection intros: - Explain what the category is, who it's for, and how to choose - Keep it under 400 words - Target the category keyword ## Always remember - Product content needs to be accurate. Never fabricate specs or features. - If given raw specs, turn them into benefit-driven copy without losing any technical details. - Each product description should be unique even in batch work.
The shipped file is a sensible default. The wins come from adapting it to your tone, clients, and content rules.

A Skill file is a set of standing instructions. Paste it into a Claude project's instructions once and every chat in that project follows the same routine: which humanization mode to use, when to run detection, which phrases to protect and what to report back. Claude also has a separate Skills feature for packaged instructions; these files are written as plain project instructions, so they work in any project.
Start with the shipped defaults, run three or four real briefs, then edit the file where the output missed. Small, specific rules work better than long general ones. Keep one Skill per kind of work, so a project for product copy never inherits the rules you set for long-form articles.
To see the routine in action before installing it, try One product, full pipeline, 5 to 10 product descriptions in one shot, Marketplace product listing. Each one runs the same steps as a single prompt.
Walter installs as an MCP connector in about 30 seconds. Free tier covers your first articles, no card.