ecommerce-customer-service-pro
v2.0.1行业可选的智能电商客服技能。用于售前咨询、售中跟进、催付催单、发货物流、售后处理、退款退换、投诉安抚、差评挽回、FAQ整理、达人与机构商务沟通等场景；先识别行业与场景，再输出全面、合规、可直接发送的话术与处理建议。
⭐ 0· 459·1 current·1 all-time
byvx：17605205782@52yuanchangxing
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 (ecommerce customer service) matches the SKILL.md and the included reference files: the skill only contains templates, playbooks, platform notes and compliance guidance. There are no unrelated env vars, binaries, or external services required.
Instruction Scope
SKILL.md instructs the agent to (a) identify industry and scenario, (b) fill in or request minimal fields (brand, product, platform, order number etc.), (c) run a compliance checklist and (d) output several reply variants and internal notes. All of these are within the claimed scope. The instructions explicitly prohibit fabricating facts and collecting sensitive data beyond what is needed (order numbers, photos, partial contact info).
Install Mechanism
No install spec and no code files — the skill is instruction-only, so nothing is downloaded or written to disk as part of installation.
Credentials
The skill declares no required environment variables, credentials, or config paths. The SKILL.md does ask the agent to request user-provided order IDs or photos when needed, which is proportionate for the stated customer-service workflows.
Persistence & Privilege
Flags show no forced persistence (always: false) and normal autonomous invocation is allowed. The skill does not request modifications to other skills or system-wide settings.
Assessment
This skill appears coherent and low-risk because it is instruction-only and asks for no credentials or installs. Before using it in production: (1) review and customise the compliance rules and any policy-specific wording to match your legal/brand requirements (especially for food, health, or cross-border claims); (2) ensure operators and the agent are instructed not to request or store highly sensitive PII (full ID numbers, full bank/credit card numbers, payment passwords, verification codes); (3) test outputs for hallucinations or accidental promises about refunds/shipping times against your real backend policies; (4) restrict who can invoke the skill on sensitive cases (escalation to human agents for refunds/compensation above thresholds); and (5) if you integrate this with your customer database or ticketing system, audit that integration separately because those connectors (not present here) will introduce additional risk.Like a lobster shell, security has layers — review code before you run it.
latestvk972re6g0kgpqkhajp53tgsgvx82q3cw
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🛍️ Clawdis