translate

Translate text accurately — preserve formatting, handle plurals, and adapt tone per locale.

Security Scan

The skill is an instruction-only translation helper whose declared purpose matches its instructions; it doesn't request credentials, install anything, or access unrelated system resources.

Purpose & Capability

Name/description (translate text, preserve formatting, handle plurals/tone) align with the SKILL.md rules (preserve code/markup, placeholders, handle plurals/gender/formality). Nothing requested (no env vars, binaries, or installs) is surprising for a pure translation instruction set.

Instruction Scope

SKILL.md stays within translation responsibilities: preserving formatting, excluding code/URLs/placeholders from translation, cultural/localization rules, and quality checks. It does not instruct reading arbitrary system files, environment variables, or sending data to unexpected endpoints. The single potential ambiguity is the directive to “Read full context before translating,” which reasonably refers to the provided document/context rather than unrelated system data.

Install Mechanism

No install spec and no code files — instruction-only skills are lowest-risk because they don't write or execute new code on the host.

Credentials

The skill requires no environment variables, credentials, or config paths. There are no extraneous secret requests and no access to unrelated services.

Persistence & Privilege

always is false and the skill is user-invocable. Autonomous model invocation is allowed (platform default) but not combined with any elevated privileges or broad credential access here.

Assessment

This is a low-risk, instruction-only translation helper that appears coherent with its stated purpose. Before installing, consider whether you'll be translating sensitive or private text (the skill will instruct the agent to read and transform input content), and if so avoid sending secrets or PII to any external model/service the agent might call. Otherwise there are no credentials, installs, or system accesses that raise concern.

Master accurate translation that preserves meaning, formatting, and cultural context.

Formatting Preservation

• Never translate content inside code blocks, HTML tags, or markdown syntax
• Preserve placeholders like {name}, {{variable}}, %s, $1 exactly as-is
• Keep markdown structure intact: headers, links, bold/italic formatting
• Maintain JSON/XML structure and keys — translate only values where appropriate

Content Rules

• Don't translate: proper nouns, brand names, technical terms, URLs, email addresses
• Don't translate: code snippets, CSS classes, API endpoints, file extensions
• Preserve numbers, dates, and IDs in their original format unless locale conversion needed
• Keep consistent terminology throughout — create a glossary for repeated terms

Language-Specific Handling

• Plurals: Use correct plural forms per target language rules (not English patterns)
• Gender: Ensure noun-adjective agreement in gendered languages (Spanish/French/German)
• Formality: Choose appropriate register (tu/vous, tú/usted, du/Sie) based on context
• RTL languages: Consider text direction for Arabic/Hebrew but keep LTR elements (URLs, numbers)

Cultural Adaptation

• Adapt idioms and expressions rather than literal translation
• Convert units when culturally appropriate (miles↔km, Fahrenheit↔Celsius)
• Adjust date formats to locale standards (MM/DD vs DD/MM vs DD.MM)
• Use local currency symbols and number formatting (, vs . for decimals)

Context Awareness

• Disambiguate based on context: "bank" (financial vs river), "mouse" (animal vs computer)
• Maintain document tone: formal business vs casual blog vs technical manual
• Consider target audience: children's content vs academic paper vs marketing copy
• Preserve original intent and emotional nuance, not just literal meaning

Quality Control

• Read full context before translating to understand meaning
• Check that translated text flows naturally in target language
• Verify all formatting elements remain functional after translation
• Ensure consistent voice and terminology across the entire document