How do I install the Frappe Translations Writer skill?

Run npx skillmds@latest add kehwar/frappe-translations-writer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Frappe Translations Writer safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Frappe Translations Writer?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Frappe Translations Writer free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Frappe Translations Writer?

kehwar (@kehwar) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Frappe Translations Writer by kehwar

Name: Frappe Translations Writer
Author: kehwar

Frappe Translations Writer

Helper utilities for finding, validating, and managing translations in Frappe apps. Includes commands for finding untranslated strings and translation file locations. Use when working with PO/POT files, finding untranslated strings, or validating translation completeness.

kehwar Updated Sep 17, 2026

File contents

Translation Helper

File paths

File	Path
POT template	`apps/<app>/<app>/locale/main.pot`
PO translations	`apps/<app>/<app>/locale/<locale>.po`
MO compiled	`sites/assets/locale/<locale>/LC_MESSAGES/<app>.mo`

Workflow

PYTHON=/workspace/development/frappe-bench/env/bin/python
SCRIPTS=<skill_dir>/scripts
PO=apps/<app>/<app>/locale/es_PE.po

cd /workspace/development/frappe-bench

# 1. Extract strings from code → update POT
bench generate-pot-file --app <app>

# 2. Merge new strings into PO
bench update-po-files --app <app> --locale es_PE

# 3. Query strings → save to <po_dir>/drafts/es_PE.review.po
$PYTHON $SCRIPTS/po_query.py --po $PO --out es_PE.review.po
#   Filter by module:   add --path "<module>/**" --out es_PE.module.po
#   Only untranslated:  add --untranslated --out es_PE.untranslated.po
#   Only fuzzy:         add --fuzzy --out es_PE.fuzzy.po

# 4. Edit the partial PO — fill in msgstr values

# 5. Merge partial PO back into the full file
$PYTHON $SCRIPTS/po_merge.py --main $PO --patch locale/drafts/es_PE.review.po --dry-run
$PYTHON $SCRIPTS/po_merge.py --main $PO --patch locale/drafts/es_PE.review.po

# 6. Compile PO → MO binary
bench compile-po-to-mo --app <app> --locale es_PE

# 7. Clear cache
bench clear-cache

--site is only required when --app is omitted.

Command options

Command	Key options
`generate-pot-file`	`--app`
`update-po-files`	`--app`, `--locale`
`compile-po-to-mo`	`--app`, `--locale`, `--force`
`po_query.py`	`--path GLOB` (repeatable), `--format po\|tsv\|json`, `--out` (relative → `<po_dir>/drafts/`, absolute → as-is, omit → stdout); filters: `--untranslated`, `--fuzzy` (omit both = all entries)
`po_merge.py`	`--dry-run`, `--clear-fuzzy`, `--out`

See scripts/po_query.py and scripts/po_merge.py for full usage.

Key rules

Locale format: es_PE (underscore), not es-PE
Always regenerate POT before updating PO when code has changed
Context syntax: _("text", context="Name") in Python, __("text", { context: "Name" }) in JS

Common issues

See REFERENCE.md for validation commands, fuzzy entries, and migration from CSV.

---name: frappe-translations-writerdescription: Helper utilities for finding, validating, and managing translations in Frappe apps. Includes commands for finding untranslated strings and translation file locations. Use when working with PO/POT files, finding untranslated strings, or validating translation completeness.---# Translation Helper## File paths| File | Path ||---|---|| POT template | `apps/<app>/<app>/locale/main.pot` || PO translations | `apps/<app>/<app>/locale/<locale>.po` || MO compiled | `sites/assets/locale/<locale>/LC_MESSAGES/<app>.mo` |## Workflow```bashPYTHON=/workspace/development/frappe-bench/env/bin/pythonSCRIPTS=<skill_dir>/scriptsPO=apps/<app>/<app>/locale/es_PE.po``````bashcd /workspace/development/frappe-bench# 1. Extract strings from code → update POTbench generate-pot-file --app <app># 2. Merge new strings into PObench update-po-files --app <app> --locale es_PE# 3. Query strings → save to <po_dir>/drafts/es_PE.review.po$PYTHON $SCRIPTS/po_query.py --po $PO --out es_PE.review.po# Filter by module: add --path "<module>/**" --out es_PE.module.po# Only untranslated: add --untranslated --out es_PE.untranslated.po# Only fuzzy: add --fuzzy --out es_PE.fuzzy.po# 4. Edit the partial PO — fill in msgstr values# 5. Merge partial PO back into the full file$PYTHON $SCRIPTS/po_merge.py --main $PO --patch locale/drafts/es_PE.review.po --dry-run$PYTHON $SCRIPTS/po_merge.py --main $PO --patch locale/drafts/es_PE.review.po# 6. Compile PO → MO binarybench compile-po-to-mo --app <app> --locale es_PE# 7. Clear cachebench clear-cache```> `--site` is only required when `--app` is omitted.## Command options| Command | Key options ||---|---|| `generate-pot-file` | `--app` || `update-po-files` | `--app`, `--locale` || `compile-po-to-mo` | `--app`, `--locale`, `--force` || `po_query.py` | `--path GLOB` (repeatable), `--format po\|tsv\|json`, `--out` (relative → `<po_dir>/drafts/`, absolute → as-is, omit → stdout); filters: `--untranslated`, `--fuzzy` (omit both = all entries) || `po_merge.py` | `--dry-run`, `--clear-fuzzy`, `--out` |See [scripts/po_query.py](scripts/po_query.py) and [scripts/po_merge.py](scripts/po_merge.py) for full usage.## Key rules- Locale format: `es_PE` (underscore), not `es-PE`- Always regenerate POT before updating PO when code has changed- Context syntax: `_("text", context="Name")` in Python, `__("text", { context: "Name" })` in JS## Common issuesSee [REFERENCE.md](REFERENCE.md) for validation commands, fuzzy entries, and migration from CSV.

Frequently asked questions