1
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill ntaksh42/agents --skill translator- SKILL.md5.4 KB
Overview
This skill translates code comments, technical documentation, and UI strings between multiple languages while preserving code and developer context. It recognizes code blocks, variable names, and technical terms, keeping them intact or annotated as specified. The skill supports over 50 languages and provides consistent terminology via glossaries. It is optimized for internationalizing applications and translating developer-facing content.
How this skill works
The translator detects and protects code blocks, identifiers, and markup so only human-readable text is translated. It applies a configurable glossary to maintain consistent translations for technical terms and can leave specific terms in the source language or add parenthetical annotations. Outputs preserve original formatting (Markdown, JSON, JSDoc) and can produce parallel translations for UI resource files.
When to use it
- Converting technical documentation and manuals for global teams
- Translating inline code comments, docstrings, and API docs
- Localizing UI strings, error messages, and labels
- Preparing language variants while preserving code blocks and identifiers
- Standardizing technical terminology across a project or product
Best practices
- Provide context: indicate target audience and where text appears (UI, README, inline comment)
- Supply a glossary of project-specific terms for consistent results
- Keep code blocks and build artifacts out of translation scope
- Review outputs with a native or technical reviewer before release
- Translate in stages: docs → comments → UI strings for manageability
Example use cases
- Translate an English README into Japanese while keeping code fences and commands unchanged
- Convert inline Japanese JSDoc comments to English without modifying function names or types
- Produce JSON localization files for five target languages from a single source
- Apply a glossary to ensure terms like API, JSON, and Docker remain standardized
- Annotate rare technical terms with original-language hints for clarity
FAQ
No. The skill preserves code, identifiers, and syntax by default; only human-readable comments and strings are translated.
Can I enforce specific translations for project terms?
Yes. Provide a glossary or term list and the skill will apply those mappings consistently across the corpus.