Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Resolve issues, communicate with empathy, and turn frustrated customers into loyal advocates.
Resolve issues, communicate with empathy, and turn frustrated customers into loyal advocates.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Acknowledge the problem before solving it โ "I understand this is frustrating" Apologize for the experience, not necessarily fault โ "I'm sorry you're dealing with this" Set expectations on timeline โ "I'll have an answer within X" beats silence Use their name โ personalization matters
Understand the actual problem, not just the stated one โ ask clarifying questions Check account history before asking for repeated information Reproduce issues when possible โ "I just tried this and saw the same thing" Explain what you're doing โ silence while working feels like being ignored Verify the solution worked before closing
Match their tone and formality level โ casual users want casual, business wants professional Short sentences, clear language โ no jargon unless they use it One question at a time โ multiple questions overwhelm Read the whole message before responding โ don't miss part of their question
Let angry customers vent before responding โ interrupting escalates Never take insults personally โ they're frustrated with the situation "I would feel the same way" validates without admitting fault Offer something concrete โ discount, extension, escalation path Know when to escalate โ some situations need supervisor authority
Lead with what you can do, not what you can't Explain the why when possible โ policies make sense with context Offer alternatives โ "I can't do X, but I could do Y" Don't hide behind policy โ "Our policy says..." feels robotic
Templates for common issues โ but personalize each use Internal notes save future agents time โ document non-obvious context Know when a call/video beats endless back-and-forth Close resolved tickets promptly โ open tickets create noise
Document solutions for new issues โ first person to solve it helps everyone Update docs when processes change โ outdated help docs create tickets Escalation paths must be clear โ don't leave agents guessing Flag patterns โ repeated issues signal product problems
Promise only what you can deliver โ overpromising erodes trust Don't make exceptions you can't repeat โ creates unfair precedent Know your authority limits โ escalate when you genuinely can't help Protect customer data โ verify identity before sharing sensitive info
Swift resolution often creates more loyalty than no problem at all Follow up after resolution โ "Just checking everything is working" Thank them for patience and for bringing issues to attention Negative feedback is free product research โ channel it constructively
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.