How do I install the Edt MCP Project Translation skill?

Run npx skillmds@latest add ditrixnew/edt-mcp-project-translation 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 Edt MCP Project Translation 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 Edt MCP Project Translation?

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 Edt MCP Project Translation free to use?

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

Who published Edt MCP Project Translation?

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

Edt MCP Project Translation by ditrixnew

Name: Edt MCP Project Translation
Author: ditrixnew

File contents

EDT-MCP translation workflow

Purpose and trigger

Use this skill to inspect configured translation resources, generate strings, run translation, and verify localized metadata for an exact project.

Operating rule

Read and apply the common operating rules before this workflow.

Task boundary

Keep the exact project, declared language codes, existing storage/provider topology, and localized human-facing fields in scope. Never translate programmatic metadata names, FQNs, BSL identifiers, query fields, or 1C tokens.

Primary workflow

Resolve project identity/kind with list_projects, declared languages with get_configuration_properties, and configured translation routes with get_translation_project_info.
Confirm the intended languages, project support, storage/provider scope, and write or external-service authority using current help.
Call generate_translation_strings or translate_configuration only for the confirmed route and requested operation. Before readback or validation, wait under current help and a bounded caller-approved deadline until list_projects reports the exact project as ready; on expiry stop and report the operation as unsettled rather than treating its success status as model readiness.
Re-read representative localized metadata with get_metadata_details, inspect the repository diff when applicable, and run targeted validation.
Report only identities, counts, status, and affected samples that current tool output actually confirms; successful execution is not proof of translation quality or complete coverage.

Authority rule

Storage/dictionary writes, overwrite, external provider transmission, and any route affecting multiple storages or projects require authority for that exact scope.

Stop rule

Stop on unsupported project kind, undeclared language, ambiguous or incomplete storage topology, unreviewed overwrite/transmission, or a need to change programmatic identifiers.

Completion signal

Return the exact project/languages/route, confirmed operation result, verified localized samples and diff/validation evidence, and explicit quality or completeness gaps.

---name: edt-mcp-project-translationdescription: Inspect and run EDT translation workflows through EDT-MCP while preserving declared languages, dictionaries, storage, and programmatic metadata names.---# EDT-MCP translation workflow## Purpose and triggerUse this skill to inspect configured translation resources, generate strings,run translation, and verify localized metadata for an exact project.## Operating ruleRead and apply [the common operating rules](../COMMON.md) before this workflow.## Task boundaryKeep the exact project, declared language codes, existing storage/providertopology, and localized human-facing fields in scope. Never translateprogrammatic metadata names, FQNs, BSL identifiers, query fields, or 1C tokens.## Primary workflow1. Resolve project identity/kind with `list_projects`, declared languages with `get_configuration_properties`, and configured translation routes with `get_translation_project_info`.2. Confirm the intended languages, project support, storage/provider scope, and write or external-service authority using current help.3. Call `generate_translation_strings` or `translate_configuration` only for the confirmed route and requested operation. Before readback or validation, wait under current help and a bounded caller-approved deadline until `list_projects` reports the exact project as ready; on expiry stop and report the operation as unsettled rather than treating its success status as model readiness.4. Re-read representative localized metadata with `get_metadata_details`, inspect the repository diff when applicable, and run targeted validation.5. Report only identities, counts, status, and affected samples that current tool output actually confirms; successful execution is not proof of translation quality or complete coverage.## Authority ruleStorage/dictionary writes, overwrite, external provider transmission, and anyroute affecting multiple storages or projects require authority for that exactscope.## Stop ruleStop on unsupported project kind, undeclared language, ambiguous or incompletestorage topology, unreviewed overwrite/transmission, or a need to changeprogrammatic identifiers.## Completion signalReturn the exact project/languages/route, confirmed operation result, verifiedlocalized samples and diff/validation evidence, and explicit quality orcompleteness gaps.

Frequently asked questions

Edt MCP Project Translation