Self-Improving Support
v1.1.0Captures ticket resolution delays, misdiagnoses, escalation gaps, SLA breaches, knowledge gaps, and customer churn signals to enable continuous support impro...
⭐ 0· 50·0 current·0 all-time
byJosé I. O.@jose-compu
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the included artifacts: documentation, templates, scripts to create .learnings/, and OpenClaw hook handlers for injecting a reminder. The files and hooks are proportionate to a support-learning capture workflow.
Instruction Scope
Runtime instructions direct the agent to create and append to local .learnings/ files in the project or OpenClaw workspace and to use hooks for optional automation. The skill warns not to log PII but cannot enforce anonymization; enabling the PostToolUse hook runs a script that reads the CLAUDE_TOOL_OUTPUT environment variable (provided by the host) and emits detection reminders. This behavior is within scope but worth noting because it touches command output and local files.
Install Mechanism
No install spec or external downloads are required. The package includes local scripts and hook handlers only. Manual install instructions point to a GitHub repo and copying hooks into the OpenClaw hooks directory, which is a standard, low-risk pattern.
Credentials
The skill declares no required credentials or config paths. Scripts read CLAUDE_TOOL_OUTPUT and rely on OpenClaw/Claude hook environments, which is normal for detection hooks but that environment var is not listed as a required env in the manifest—this is expected for hook-driven scripts but worth calling out. No secrets or unrelated cloud credentials are requested.
Persistence & Privilege
always is false and the skill is user-invocable. Hooks inject a virtual reminder file at agent bootstrap and scripts can create files under the workspace or ./skills (extract-skill.sh), but nothing forces persistent global changes or modifies other skills' configs. Enabling hooks is an explicit opt-in step.
Assessment
This skill appears coherent for support-process improvement. Before enabling: (1) review the scripts (activator.sh, error-detector.sh, extract-skill.sh) to confirm you’re comfortable with local file writes (/.learnings/ or ./skills/) and that no PII will be logged; (2) only enable the hooks you need—UserPromptSubmit (activator) is lightweight; PostToolUse (error detector) reads tool output and should be enabled only if you trust automated inspection of command outputs; (3) if you install manually, prefer reviewing the GitHub repo contents first; (4) consider adding a matcher in your hook configuration so reminders run only for support-related prompts; and (5) remember the skill can’t enforce anonymization—agents must follow the “never log PII” guidance.Like a lobster shell, security has layers — review code before you run it.
latestvk97528mgacnkhwg8qj86gy0axs84tq66
License
MIT-0
Free to use, modify, and redistribute. No attribution required.