Refund Policy Clarifier

v1.0.0

Clarifies and rewrites ecommerce refund policies into clear, customer-friendly language without expanding or changing the store’s actual refund terms.

0· 98·0 current·0 all-time
byLeroyCreates@leooooooow
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description (rewrite refund policies into customer-facing language) aligns with the SKILL.md instructions. It asks for the policy text and contextual details that are relevant to rewriting—no unrelated services, binaries, or credentials are requested.
Instruction Scope
Runtime instructions are limited to reading the provided policy text, separating rules from unclear wording, producing rewrites, and flagging ambiguities. The skill does not instruct the agent to read system files, access external endpoints, or collect unrelated data. It explicitly avoids giving legal advice.
Install Mechanism
This is an instruction-only skill with no install spec or code files. Nothing is downloaded or written to disk by an installer, which minimizes installation risk.
Credentials
No environment variables, credentials, or config paths are required. The inputs requested in SKILL.md (policy text, store/channel/type, product category, windows/exclusions, etc.) are proportional to the stated task.
Persistence & Privilege
Flags show always:false and default user-invocable/autonomous invocation settings. The skill does not request permanent presence or elevated privileges and does not modify other skills or system settings.
Assessment
This skill appears low-risk and coherent for rewriting refund policies. Before using it: (1) do not paste customer personal data or sensitive credentials into prompts; (2) remember the tool is not a substitute for legal advice—have a lawyer verify policy wording for compliance; (3) review the rewritten text carefully to ensure it doesn't unintentionally expand customer rights; and (4) test published copy in a staging/help-center environment before making it public.

Like a lobster shell, security has layers — review code before you run it.

latestvk978z0tjwz43384ym5f772qeed832j7z

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments