translate

To translate Markdown documentation and comments between Dutch and English, run the translate command on a local skill directory to convert human-readable files while preserving frontmatter name, description, and source code unchanged. Outputs are written to a language-suffixed parallel directory.

Yes, you can translate skill files without altering frontmatter or source code. The process converts Markdown bodies, section headers, comments, usage strings, and examples while explicitly leaving frontmatter name and description fields along with executable source files unchanged.

When localizing a skill directory, binary files are detected and copied unchanged to the target language-suffixed directory. The process reports any skipped binaries and refuses to overwrite existing target locations to prevent data loss.

The best way to convert Claude skill content for English-speaking users is to apply the translate command to an exported skill path. This sanitizes and translates documentation, examples, and help text into a new parallel directory without overwriting existing targets.

The translation process writes to a language-suffixed parallel directory to ensure the original source files remain untouched. This prevents overwriting existing target locations and allows you to maintain both Dutch and English versions of the skill side by side.

You do not need to manually validate input paths before translating skill documentation. The process automatically validates input paths, detects text versus binary files, and copies binaries unchanged to ensure safe and consistent language transformation.