SKILLEMALL.ai
RU Sign in

AB technical-support-communication

Technical support communication: draft or revise customer and stakeholder messages, de-escalate tense interactions, coach empathic listening, or apply IT service people skills.

ClawHub Agent Skills author: wei v1.0.1 MIT-0 16 files body ≈ 1 621 tokens Open the sourceclawhub.ai↗ analyzed 30 h ago

Technical support communication: draft or revise customer and stakeholder messages, de-escalate tense interactions, coach empathic listening, or apply IT…

As a process B 76/100 · Nearly there — weak spots: inputs and preconditions, running it twice, progress reporting

ProcedureOperations and projectstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
76
Run on models
none yet
Process rating
B
76/100
Nearly there
Inputs and preconditions w 11
0
Progress reporting w 2
0
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 16. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 76/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 9 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 70When it triggers. States when to use, but not when not to
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 37 steps
  • 100Result and completion. Output format and completion criterion are stated
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1621 tokens

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +4No input/output examples
  • +2Single-language instructions
  • +3Description length 176: enough signal without eating the budget
  • +4Structure: 9 headings
  • +3Step-by-step instructions: 37 items
  • +3Output format is stated explicitly
  • +4Reference files are cited in the instructions (5 of 12)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.

External checks

ClawHub: clean
This skill is a communication-coaching guide that reads its own reference files and does not request risky access or perform actions on the user's system.
LLM: benign (high) · VirusTotal: · 31 Jul 2026