Customer Support Command Center
v1.0.0Enterprise-grade customer support system: ticket triage, response templates, escalation workflows, CSAT tracking, knowledge base management, and churn prevention. Turns your AI agent into a support team lead.
⭐ 1· 705·0 current·0 all-time
by@1kalin
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name, description, and delivered content (triage matrix, response templates, routing rules, churn playbooks) align with an agent acting as a support lead. There are no declared env vars, binaries, or config paths that are unrelated to support operations.
Instruction Scope
SKILL.md contains triage checklists, templates, routing rules, and playbooks. It does not instruct the agent to read local files, access system environment variables, or send data to external endpoints beyond normal support workflows. Instructions are scoped to ticket handling, escalation, KB management, metrics, and retention.
Install Mechanism
This is instruction-only (no install spec, no code). README suggests installing via `clawhub install afrexai-customer-support`, but the registry metadata contains no install actions — this is a minor inconsistency (marketing vs. registry). No downloads, extract steps, or external package installs are present in the skill bundle.
Credentials
The skill declares no required environment variables, credentials, or config paths. The content references account/plan data and MRR tiers conceptually (expected for support tasks) but does not request secrets or other credentials.
Persistence & Privilege
Defaults are used (always:false, agent-invocable allowed). The skill does not request permanent system presence, nor does it instruct changes to other skills or system-wide settings.
Assessment
This skill appears to be a coherent, instruction-only support playbook. Before enabling it on live data: 1) confirm what ticket system or inbox the agent will access and restrict it to that scope; 2) test auto-reply / automation rules in a staging environment to avoid incorrect customer messages; 3) review any external links (paid 'context packs') before following them; and 4) if you need the agent to perform actions (route tickets, update billing, offer credits), ensure it uses narrow, auditable integrations with least privilege rather than giving broad API credentials. If you want deeper assurance, ask the publisher for a provenance statement or an install spec showing exactly what (if anything) the skill will install or call at runtime.Like a lobster shell, security has layers — review code before you run it.
churnvk97d1b3zx08xm812saz0x3cbr5813j13csatvk97d1b3zx08xm812saz0x3cbr5813j13customervk97d1b3zx08xm812saz0x3cbr5813j13helpdeskvk97d1b3zx08xm812saz0x3cbr5813j13latestvk97d1b3zx08xm812saz0x3cbr5813j13retentionvk97d1b3zx08xm812saz0x3cbr5813j13supportvk97d1b3zx08xm812saz0x3cbr5813j13ticketsvk97d1b3zx08xm812saz0x3cbr5813j13
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🎯 Clawdis
OSLinux · macOS · Windows