Write Locale Translations logo

Write Locale Translations

OrganizationPopular
videojs
write-locale-translations

Translate or audit the values in a Video.js locale pack. Use when a key needs values, en.ts copy changes underneath a pack, or one pack needs an audit.

Overview

Publishervideojs
Repositoryv10
Skill namewrite-locale-translations
Stars
1K
Forks
93
Bundled files
2
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by videojs on GitHub. Read the source before you install it.

Installation

Install the Write Locale Translations AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/videojs/v10/tree/main/.agents/skills/write-locale-translations
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/videojs/v10.git /tmp/v10
mkdir -p .claude/skills
cp -r /tmp/v10/.agents/skills/write-locale-translations .claude/skills/write-locale-translations
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Write Locale Translations in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Write Locale Translations on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Write Locale Translations is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Translate locale values

Produce translated values for one locale pack in packages/core/src/core/i18n/locales/ that are backed by a citable source and free of the known pitfalls. Every value reaches the DOM as an aria-label, so a wrong word class is announced by a screen reader rather than merely displayed.

Triggers

  • A new key needs values in a pack.
  • locales/en.ts reworded a value, so the pack still translates the old English.
  • One pack needs an audit of the values it already carries.

packages/core/src/core/i18n/README.md covers the mechanics: where a pack lives, how to register a tag, what to regenerate. This workflow covers the translation judgment behind the values, so reach for the README to add or wire up a locale and reach for this to decide what a value should say. It does not cover authoring the English source copy, RTL layout work, or the generated mirrors under packages/html, packages/react, and packages/cdn.

Workflow

  1. Identify which values are stale by diffing the pack against current en.ts key by key; a value whose English source has not changed stays as it is.
  2. Research each value against localized first-party UI for the same control, with one citation per value. Read references/evidence-sources.md when choosing and citing. Never translate unsourced, and never derive one pack from a related one; zh-TW is not converted zh-CN.
  3. Check the wording against references/language-pitfalls.md, then edit values only, preserving the key set, key order, and the full {placeholder} multiset.
  4. Verify by re-deriving each value from en.ts and its old value, re-fetching every citation, and running a codepoint scan for homoglyphs, stray scripts, NBSP, and double spaces. cspell ignores non-English packs, so that scan is the only mechanical guard on the text itself. A translated value is research-backed rather than native-authored, so a native-speaker check is worth requesting.

Example

Input: When #1822 reworded errors.aborted in en.ts, es.ts was left translating the old English.

Output: A value-only edit to es.ts, carrying the source the new wording rests on.

ts
// was: 'Ha anulado la reproducción del vídeo.' (translated the pre-#1822 "You aborted the media playback")
aborted: 'Has detenido la reproducción del contenido multimedia antes de que terminara.',
// source: YouTube es-ES player, "Has detenido la reproducción"

Validation

bash
pnpm -F @videojs/core run generate:locales     # validates every pack carries every en.ts key
pnpm lint:fix:file packages/core/src/core/i18n/locales/<tag>.ts
CI=1 pnpm -F @videojs/core exec vp test run src/core/i18n
git diff --check

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Write Locale Translations AI skill do?

Translate or audit the values in a Video.js locale pack. Use when a key needs values, en.ts copy changes underneath a pack, or one pack needs an audit.

Why use Write Locale Translations on TypingMind?

Because you install it once and use it with any model. Write Locale Translations is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Write Locale Translations in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/videojs/v10/tree/main/.agents/skills/write-locale-translations. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Write Locale Translations?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Write Locale Translations?

As many as you like. As long as a model supports skills, you can use Write Locale Translations with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Write Locale Translations AI skill free?

It is published on GitHub by videojs. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇