skills/return-refund-policy/SKILL.md
Write a clear, fair returns, refunds & exchanges policy for an online store. Use when asked to write a return policy, refund/exchange policy, or store returns page. Produces a customer-friendly policy — window, conditions, process, refund method/timing, exceptions, and shipping — in plain language that reduces support tickets and builds trust. Not legal advice.
npx skillsauth add mohitagw15856/pm-claude-skills return-refund-policyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
A clear returns policy is a conversion tool, not just fine print — shoppers check it before buying, and a fair, plain-English one removes a purchase objection. This skill writes a policy that's easy to understand and easy to act on, so customers trust it and your support team isn't answering the same questions all day.
Note: this is a drafting aid, not legal advice. Consumer-protection rules (statutory return rights, distance-selling/cooling-off, warranty law) vary by country and platform — have it reviewed against your jurisdiction and marketplace policies before publishing. Flag, don't rule on, legal questions.
Given "write a returns policy for my Shopify store", produce the full policy anyway — infer sensible, customer-friendly defaults (e.g. a 30-day window), and clearly mark each business-specific choice (set your value) so the owner confirms window, who pays return shipping, and exceptions. Never withhold for missing detail.
Ask for these only if they aren't already provided (else use a labelled default):
Mark each business-specific value (set your value) and add a note to confirm jurisdiction-specific rights.
E-commerce trust & CRO practice — transparent, plain-language returns policies that reduce purchase friction and support load.
business
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
development
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
testing
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
development
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.