What it does
Takes the store's stated return window, condition requirements, refund method, and any restocking fee, and writes them into a clear return and refund policy page rather than adapting a generic legal template. Explicitly asks the user to confirm any detail, like return window length or who pays return shipping, that isn't already documented somewhere on the site.
Install
This skill isn't packaged in an installable registry. It's a plain SKILL.md file you can copy directly. Copy it from the SKILL.md tab and save it at the path for your assistant:
Use it in your AI assistant
Claude Code
.claude/skills/return-refund-policy-writer/ (or ~/.claude/skills/return-refund-policy-writer/ for all projects)
GitHub Copilot (VS Code)
.github/skills/return-refund-policy-writer/
OpenAI Codex
.codex/skills/return-refund-policy-writer/
Cursor
.cursor/skills/return-refund-policy-writer/ (or ~/.cursor/skills/return-refund-policy-writer/ globally)
Compatibility
WordPress with WooCommerce active. Works from information supplied by the user or found on existing store pages, no special API access required beyond reading existing content.
The complete SKILL.md for this skill:
---
name: return-refund-policy-writer
description: Use when a user wants a return and refund policy page drafted or revised to match their store's actual return process, timeframes, and fees.
---
# Return and Refund Policy Writer
## When to use
A store needs a return and refund policy page written or updated, based on its real return window, condition requirements, and refund method.
## Procedure
1. Gather the store's actual return window (days from delivery), condition requirements (unopened, tags attached, etc.), and who covers return shipping.
2. Check any existing policy page or FAQ content on the site first, so the new draft doesn't contradict something already published.
3. Draft the page in plain sections: how to start a return, timeframe, condition requirements, refund method and timing, and any exceptions (final sale items, digital products).
4. If a detail is missing, such as a restocking fee or exchange policy, list it as an open question for the user rather than filling in a plausible-sounding default.
5. State refund timing in terms the store can actually meet (e.g. "within X business days of receiving the return") rather than a vague promise.
6. Keep the language plain and specific, avoid legal boilerplate that doesn't match how the store actually operates.
## Guardrails
- Never state a return window, fee, or refund timeframe that the user hasn't confirmed.
- Never publish the page directly, this is a policy document and should go through the user's own review first.