Immediate result: A natural reply in the customer's language and register, with an English version for the record.
Problem it solvesCustomers write in Hindi, Tamil or Hinglish and replies come back in stiff English.
'bhai mera refund abhi tak nahi aaya' · answer: refund sent 20 Oct, 5–7 working days
Detected: Hinglish, casual.
Reply: 'Hi! Aapka refund 20 Oct ko bhej diya gaya hai. Bank mein dikhne mein 5–7 working days lagte hain…'
English: 'Your refund was sent on 20 Oct…'
Customers write in Hindi, Tamil or Hinglish and get replies in stiff English, which feels distant. This skill detects the language and register of the message, then writes a natural reply in the same language rather than a word-for-word translation, keeping product names, amounts and dates exact. It also gives an English version for your ticket record. For legal or financial wording it recommends a check by a native speaker before sending. To use it, paste the skill into your assistant and send the customer's message and your answer (in English); the reply is laid out as “Detected language and register”, “Reply” and “English version”.
# Skill: Multilingual reply
You are running the "Multilingual reply" skill for me. I work as: Support agent. What I need from you: a natural reply in the customer's language and register, with an English version for the record.
## When I send you the customer's message and my answer (in English)
1. Detect the language and register (formal, Hinglish, casual).
2. Write the reply in that language naturally, not word-for-word.
3. Keep product terms and amounts exact.
4. Provide the English version for the ticket record.
## Reply in this format
- Detected language and register
- Reply
- English version
## Rules
- Ask a native speaker to check legal or financial wording.
- Use only the facts I give you; mark anything you had to assume with [ASSUMPTION].
- If something essential is missing, ask me one short question, then continue.
- No preamble or filler: start with the result.
Confirm you're ready in one line, then wait for me to send the customer's message and my answer (in English).Then sendThe customer's message and your answer (in English). For example: 'bhai mera refund abhi tak nahi aaya' · answer: refund sent 20 Oct, 5–7 working days
Upload it to Claude, add it to ChatGPT's Codex app, clone it into Claude Code, or download the SKILL.md for any agent. Full guide with screenshots →
Download the ZIP and upload it in Claude. Claude then uses the skill on its own whenever a request matches.
Download ZIP
OpenAI's Codex app reads the same SKILL.md format. Copy the skill into your Codex skills folder:
$ git -c http.version=HTTP/1.1 clone https://scienceofapps.com/skills/ai-skills.git
$ cp -r ai-skills/multilingual-reply ~/.codex/skills/
Clone the library and copy this skill into your Claude Code skills folder.
$ git -c http.version=HTTP/1.1 clone https://scienceofapps.com/skills/ai-skills.git
$ cp -r ai-skills/multilingual-reply ~/.claude/skills/~/.claude/skills/ for all projects, or .claude/skills/ inside one project.Download the skill file and put it in a folder named after the skill.
Download SKILL.md~/.claude/skills/multilingual-reply/SKILL.md.Repositoryscienceofapps.com/skills/ai-skills.git · all 200 skills, one folder each, plain git over HTTPS
Customers write in Hindi, Tamil or Hinglish and replies come back in stiff English. The skill fixes that: a natural reply in the customer's language and register, with an English version for the record.
Copy the skill and paste it as the first message of a new chat, then send your input. To keep it, paste it into a ChatGPT Project or custom GPT, a Claude Project or a Gemini Gem, or upload the SKILL.md file as a Claude Skill.
Send the customer's message and your answer (in English). If something essential is missing, the skill asks you one short question and then continues.
Yes. It's free to copy, use and adapt, with no sign-up, and works in the free versions of ChatGPT, Claude, Gemini and Copilot.
ProblemTicket quality reviews are subjective and feedback to agents is vague.
Thread: 6 messages, refund handled, customer asked twice for timeline
Resolution 5 · Efficiency 3 — timeline only given after the second ask.
Coaching: put the 'when' in the first reply.
Better: 'Refund sent today; it shows in 5–7 working days.'
Immediate resultA scored review of a ticket against a rubric with specific coaching feedback.
ProblemDuring an outage, customer updates are late, vague or contradict each other.
UPI payments failing for ~30% of users since 10:40, cause unknown
Investigating (10:52): Some UPI payments are failing. Cards and wallets work. Next update by 11:20.
Banner: 'UPI is having trouble — try card or wallet for now.'
Resolved: 'UPI payments are working again. Any money debited for a failed order will be refunded automatically.'
Immediate resultStatus page updates, an in-app banner, a social reply and a resolution email for the incident.
ProblemReplies to upset customers come out either robotic or over-apologetic, and the issue drags on.
'Third time my order is late. Useless app.' · policy: ₹100 credit for delays over 30 min
Wants: to be taken seriously, and some compensation.
Reply: 'Three late orders in a row is genuinely frustrating — I'm sorry. I've added a ₹100 credit for today's delay…'
Internal note: tag 'repeat delay', check rider allocation for this pin code.
Immediate resultA reply that acknowledges the feeling, answers the question, states the next step and closes the loop.
All 12 customer support skillsAll 200 skillsRead it in the articleProve it: AI for Customer Support Certification (free test)
60 research-backed principles in 6 categories — what each one means, why it works on the human brain and how to use it on your own screens. Written by Sushant Singh, founder of Science of Apps, who has scaled consumer apps to lacs of users and spent 10+ years leading product across startups and digital businesses in the US, EU & India.
110 real paywalls from top apps, taken apart, rated out of 5 and decoded with the Laws of UX — plus the frameworks, copy and checklists to ship your own. By Sushant Singh, founder of Science of Apps.