Customer Support

v1.0.0

Resolve issues, communicate with empathy, and turn frustrated customers into loyal advocates.

4· 1.8k·11 current·12 all-time
byIván@ivangdavila
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
Name and description match the content: SKILL.md contains customer-support rules and best practices. The skill requests no binaries, env vars, installs, or config paths that would be unrelated to its stated purpose.
Instruction Scope
Instructions are limited to agent behavior and response style. A few lines (e.g., 'Check account history before asking for repeated information' and 'Reproduce issues when possible') implicitly assume access to customer account or systems, but the skill itself does not request credentials or provide mechanisms to access those systems. This is a reasonable guidance note, but operators should ensure the agent only accesses customer data when explicitly authorized and instrumented by other skills or connectors.
Install Mechanism
No install spec (instruction-only). Nothing is written to disk or downloaded, which minimizes install risk.
Credentials
The skill requires no environment variables, credentials, or config paths. No disproportionate or unrelated secret access is requested.
Persistence & Privilege
always is false and the skill does not request any elevated or persistent platform privileges. It does not modify other skills or system settings.
Assessment
This skill is a plain set of customer-support guidelines and is internally coherent. It does not itself access systems or request credentials, but several rules assume the agent will access customer accounts or reproduce issues using other tools. Before enabling this skill in an agent that has CRM/production access, verify: (1) the agent's connectors and other skills that provide account access are limited to the minimum necessary, (2) identity verification and data-handling policies are enforced, and (3) audit/logging is enabled so any access to customer data is traceable. If you don't want the agent to access accounts, keep this skill as a behavioral guide only and do not grant the agent connectors that expose customer data.

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

latestvk979t0zp432fb46bmxzhq6nqg180t8fb

License

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

Runtime requirements

🎧 Clawdis
OSLinux · macOS · Windows

Comments