Customer Support Operations Engine
v1.0.0Build and run a world-class customer support operation — from ticket management to team scaling. Complete methodology with templates, scoring systems, and au...
⭐ 0· 584·1 current·1 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 promise a support operations methodology; the SKILL.md and README contain templates, routing logic, metrics, and playbooks that align with that purpose. There are no unexpected binaries, cloud credentials, or unrelated capabilities declared.
Instruction Scope
Runtime instructions are prose/frameworks for assessing and designing support orgs and producing templates. They do not instruct the agent to read system files, environment variables, or call external endpoints beyond recommending third-party tools; the content expects user-provided business context (metrics and descriptions), which is appropriate for this use case.
Install Mechanism
No install specification and no code files — instruction-only. This is the lowest-risk install model; nothing will be written to disk or downloaded by the skill itself.
Credentials
The skill declares no required environment variables, no credentials, and no config paths. That matches the nature of a methodology/template skill and is proportionate to its functions.
Persistence & Privilege
always is false (not force-included). The skill allows normal autonomous invocation (platform default), which is expected for skills; there is no request for elevated or persistent system privileges or for modifying other skills/configs.
Assessment
This skill is a text-based playbook and appears internally consistent and low-risk. Before installing: (1) avoid pasting secrets or production credentials into prompts or templates — the skill asks for business metrics but doesn't need credentials; (2) be cautious about following external paid links in the README and verify any third-party site before providing payment or sensitive data; (3) confirm your agent platform's permissions for any skills you enable (autonomous invocation is normal but review what actions your agent can take in your environment); and (4) if you expect integrations with live systems (ticketing APIs, phone providers), prefer adding dedicated, minimal-scope credentials later rather than entering them into free-form prompts.Like a lobster shell, security has layers — review code before you run it.
customer-supportvk971zm3f1e6fqnavg6g0q6w09x81e1fpcxvk971zm3f1e6fqnavg6g0q6w09x81e1fphelpdeskvk971zm3f1e6fqnavg6g0q6w09x81e1fplatestvk971zm3f1e6fqnavg6g0q6w09x81e1fpsupport-opsvk971zm3f1e6fqnavg6g0q6w09x81e1fpticketingvk971zm3f1e6fqnavg6g0q6w09x81e1fp
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🎧 Clawdis
OSLinux · macOS · Windows