Dispute Resolver
v1.0.0Generate professional, evidence-grounded responses to refund requests and customer disputes that protect the seller while keeping the buyer relationship intact.
⭐ 0· 52·0 current·0 all-time
byLeroyCreates@leooooooow
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name, description, and required inputs (dispute summary, evidence, preferred resolution) align with the behavior described in SKILL.md. It targets ecommerce dispute responses and does not request unrelated capabilities (cloud credentials, platform access, or system files).
Instruction Scope
SKILL.md confines the agent to generating written response documents based on user-provided context and evidence. It explicitly states it does NOT submit to platform portals or access live systems. It does not instruct reading of local files, environment variables, or transmission to third parties.
Install Mechanism
No install spec or code files are present (instruction-only), so nothing will be written to disk or downloaded during install. This minimizes supply-chain risk.
Credentials
The skill declares no required environment variables, credentials, or config paths. That is proportionate for a text-generation helper that formats user-supplied evidence and references platform policies.
Persistence & Privilege
always:false (default) and autonomous invocation allowed (disable-model-invocation:false). Autonomous invocation is the platform default; combined with this skill's lack of extra privileges or credentials, the persistence/privilege level is appropriate.
Scan Findings in Context
[no_scan_findings] expected: The static scanner had no code files to analyze; this is expected because the skill is instruction-only (SKILL.md only). Absence of findings is not evidence of safety but is consistent with an instruction-only skill.
Assessment
This skill appears coherent and low-risk because it only generates text and asks you to paste evidence. Before installing or using it: 1) Don't paste unnecessary personal or sensitive data (full customer PII, payment details, or government IDs) into prompts — only include the evidence needed for the response. 2) Treat generated outputs as drafts: verify factual accuracy, platform policy citations, and legal implications (this is not legal advice). 3) If you need automatic submission to marketplaces or integration with case portals, do not rely on this skill — it explicitly says it will not submit on your behalf. 4) If your workflow requires storing dispute history or automating submissions, prefer a skill that explicitly declares required credentials and install steps and review those carefully. Overall, the skill is internally consistent but standard operational caution about handling customer data and verifying legal/policy statements still applies.Like a lobster shell, security has layers — review code before you run it.
latestvk97fdj02qx1dnabjzf673c299d83s9jy
License
MIT-0
Free to use, modify, and redistribute. No attribution required.