translations skillA
translations is agent-read markdown (skill) from mendixlabs/mxcli: Translate a Mendix app's user-visible strings with MDL — DESCRIBE TRANSLATIONS to export one file per language, CREATE [OR MODIFY|REPLACE] TRANSLATIONS to write them back. Use when localising an app, filling in a language with an LLM, or auditing which strings are still untranslated. Covers why a translation can be stored and still never appear..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Translations Every user-visible string of a Mendix app — page titles, widget captions, button labels, validation messages, enum captions, menu items — is a `Texts$Text` with one translation per language. MDL treats them in bulk: one file per language. ## The loop ```bash # 1. export: an untranslated string comes back with an EMPTY target mxcli -p app.mpr -c "describe translations for de_DE" > de_DE.mdl # 2. fill in the right-hand sides (by hand, or hand the file to an LLM) # 3. write them back mxcli exec de_DE.mdl -p app.mpr ``` That is the whole design: `DESCRIBE` emits the `CREATE` form, so the export format and the import format are the same file, and the empty targets are the prompt. ## Statements ```sql describe translations [in <Module>] for <lang>; create translations [in <Module>] for <lang> ( 'src' as 'target', ... ); create or modify translations [in <Module>] for <lang> ( 'src' as 'target', ... ); create or replace translations [in <Module>] for <lang> ( 'src' as 'target', ... ); ``` Entries use `as`, not a colon: a translation maps a user-provided name to another name. | verb | meaning | |------|---------| …
Read the whole file at its exact version.
How to install
mdr add mendixlabs/mxcli/translations@git:20260826.91a3dc8mdr add mendixlabs/mxcli/translations@sha256:e18df9be39b28435Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_2rk2ntb4tfbbtrvu)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260826.91a3dc8 latest | 2026-08-26 | 91a3dc8 | 5,393 B | A | view · diff |
| git:20260825.86be70d | 2026-08-25 | 86be70d | 4,992 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5393 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
mendixlabs/mxcli · 124 stars · license Apache-2.0 · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2rk2ntb4tfbbtrvu GET https://markdownregistry.com/api/v1/resolve?ref=mendixlabs/mxcli/translations GET https://markdownregistry.com/api/v1/blob/e18df9be39b28435b3e6619b3a7729928c2688ce71827d72a8b7c47469bb92d1
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.