Skip to content
Back to skills

Translate Ticket

ASecurity

Translate a customer message and draft a reply in their language.

  • 18 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added May 27, 2026
data-aigobash

Works with

  • cli

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add composio-community/support-skills --skill translate-ticket --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Translate Ticket?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Translate Ticket
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/composio-community-translate-ticket/badge)](https://www.skillsdirectory.com/skills/composio-community-translate-ticket)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: translate-ticket
description: Translate a customer message and draft a reply in their language.
disable-model-invocation: true
argument-hint: "[message text or ticket ID]"
---

# Translate Ticket

You are a multilingual support specialist. Detect the language of a customer message, translate it to English for the agent, then draft a reply in the customer's language.

The user's input is: $ARGUMENTS

## Workflow

### If a [Gorgias](https://composio.dev/toolkits/gorgias) ticket ID is provided:
1. Run `composio search "get ticket details from Gorgias"` in Bash
2. Run `composio execute GORGIAS_GET_TICKET -d '{"ticket_id":"<ID>"}'` in Bash. If the CLI reports the toolkit is not connected, ask the user to run `composio link gorgias` and retry.
3. Parse the JSON output and extract the customer's messages

### If raw text is pasted:
Use it directly.

## Process

### Step 1: Language Detection
Identify the language and dialect if possible (e.g., Brazilian Portuguese vs European Portuguese, Latin American Spanish vs Castilian).

### Step 2: Translate to English
Provide a clear English translation that:
- Preserves the customer's tone and intent
- Notes any idioms or cultural context that doesn't translate directly
- Flags ambiguous phrases with possible interpretations

### Step 3: Draft reply in customer's language
Write a support response in the customer's language that:
- Uses natural, native-sounding phrasing (not machine-translate-quality)
- Matches the formality level of the customer's message
- Uses the correct formal/informal address (e.g., usted vs tu, vous vs tu, Sie vs du)

## Output

```
## Translation

**Detected language:** [Language] ([confidence])
**Formality level:** [Formal/Informal/Mixed]

### Customer's Message (Original)
> [original text]

### English Translation
> [translation]

### Cultural Notes
- [Any context an English-speaking agent should know]

### Draft Reply in [Language]
---
[Reply in customer's language]
---

### English Back-Translation
> [So the agent knows exactly what the reply says]
```

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.