ClawKit Logo
ClawKitReliability Toolkit
Back to Registry
Official Verified developer tools Safety 4/5

translate-cli

End-user guide for running and configuring the `translate` CLI across text/stdin/file/glob inputs, provider selection, presets, custom prompt templates, and TOML settings. Use when users ask for command construction, config updates (`translate config`/`translate presets`), provider setup, dry-run validation, or troubleshooting translation behavior.

skill-install — Terminal

Install via CLI (Recommended)

clawhub install openclaw/skills/skills/atacan/translate-cli
Or

What This Skill Does

The translate-cli skill provides comprehensive support for the translate command-line tool, an advanced utility designed to handle localization and translation tasks across various formats. Whether you are translating simple text snippets, entire documentation files, or complex .xcstrings catalogs, this skill helps you construct the precise command needed. It manages provider configuration (e.g., OpenAI, Anthropic, Ollama, DeepL), handles output redirection, manages preset prompt templates, and assists in troubleshooting configuration issues via the config.toml file. The skill ensures your commands follow the correct syntax, prioritizing flags before positional inputs for optimal CLI performance.

Installation

To install this skill into your OpenClaw agent, execute the following command in your terminal: clawhub install openclaw/skills/skills/atacan/translate-cli Once installed, you can query the agent about specific provider setups or command construction patterns.

Use Cases

This skill is ideal for developers and technical writers who need to automate localization. Use it to:

  • Automate the translation of README files or source documentation into multiple languages.
  • Manage complex localization catalogs like .xcstrings by batch processing files using glob patterns.
  • Experiment with different LLM providers like Ollama or Anthropic to compare translation nuance and cost.
  • Customize translation prompts using placeholders to ensure consistent tone and terminology across projects.
  • Validate translation workflows using the --dry-run flag before applying changes to your repository.
  • Configure global defaults for providers, streaming preferences, and concurrency settings to streamline repetitive tasks.

Example Prompts

  1. "Construct a command to translate all files in the current directory ending in .md into Spanish using the OpenAI provider, and ensure it runs in parallel."
  2. "I need to update my translate CLI config to use Anthropic as the default provider and set a custom prompt template for technical documentation. How do I do that?"
  3. "Can you explain why my translate command is failing and how I can use the --dry-run flag to debug the request before sending it to the API?"

Tips & Limitations

Always remember that the translate tool prioritizes flags before inputs. For example, translate --to fr input.txt is the correct structure. If you are using local LLMs via Ollama, ensure your server is running and the model is pulled locally before executing commands. When using custom prompt templates, utilize the placeholders defined in the documentation to ensure the target language and context are correctly injected. Note that API costs may apply depending on the provider you select; use --dry-run frequently to monitor output formatting without incurring usage fees.

Metadata

Author@atacan
Stars4473
Views0
Updated2026-05-01
View Author Profile
AI Skill Finder

Not sure this is the right skill?

Describe what you want to build — we'll match you to the best skill from 16,000+ options.

Find the right skill
Add to Configuration

Paste this into your clawhub.json to enable this plugin.

{
  "plugins": {
    "official-atacan-translate-cli": {
      "enabled": true,
      "auto_update": true
    }
  }
}

Tags(AI)

#translation#cli#localization#developer-tools#llm
Safety Score: 4/5

Flags: file-read, file-write, external-api