
Vscode Ext Localization
- 8.8k installs
- 37.1k repo stars
- Updated July 28, 2026
- github/awesome-copilot
vscode-ext-localization is an agent skill that Guidelines for proper localization of VS Code extensions, following VS Code extension development guidelines, libraries and good practices.
About
Guidelines for proper localization of VS Code extensions following VS Code extension development guidelines libraries and good practices name vscode-ext-localization description Guidelines for proper localization of VS Code extensions following VS Code extension development guidelines libraries and good practices VS Code extension localization This skill helps you localize every aspect of VS Code extensions When to use this skill Use this skill when you need to Localize new or existing contributed configurations settings commands menus views or walkthroughs Localize new or existing messages or other string resources contained in extension source code that are displayed to the end user Instructions VS Code localization is composed by three different approaches depending on the resource that is being localized When a new localizable resource is created or updated the corresponding localization for all currently available languages must be created updated Configurations like Settings Commands Menus Views ViewsWelcome Walkthrough Titles and Descriptions defined in package json An exclusive package nls LANGID json file like package nls pt-br json of Brazilian Portuguese pt-br localizat.
- VS Code extension localization
- Localize new or existing contributed configurations (settings), commands, menus, views or walkthroughs
- Localize new or existing messages or other string resources contained in extension source code that are displayed to the
- Configurations like Settings, Commands, Menus, Views, ViewsWelcome, Walkthrough Titles and Descriptions, defined in `pac
- Walkthrough content (defined in its own `Markdown` files)
Vscode Ext Localization by the numbers
- 8,822 all-time installs (skills.sh)
- +21 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #103 of 4,386 Backend & APIs skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
vscode-ext-localization capabilities & compatibility
- Capabilities
- vs code extension localization · localize new or existing contributed configurati · localize new or existing messages or other strin · configurations like settings, commands, menus, v · walkthrough content (defined in its own `markdow
- Use cases
- documentation
What vscode-ext-localization says it does
When a new localizable resource is created or updated, the corresponding localization for all currently available languages must be created/updated.
Walkthrough content (defined in its own `Markdown` files) -> An exclusive `Markdown` file like `walkthrough/someStep.pt-br.md` for Brazilian Portuguese localization 3.
Messages and string located in extension source code (JavaScript or TypeScript files) -> An exclusive `bundle.l10n.pt-br.json` for Brazilian Portuguese localization
npx skills add https://github.com/github/awesome-copilot --skill vscode-ext-localizationAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 8.8k |
|---|---|
| repo stars | ★ 37.1k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 28, 2026 |
| Repository | github/awesome-copilot ↗ |
What problem does vscode-ext-localization solve for developers using this skill?
Guidelines for proper localization of VS Code extensions, following VS Code extension development guidelines, libraries and good practices
Who is it for?
Developers who need vscode-ext-localization patterns described in the cached skill documentation.
Skip if: Skip when docs are empty or the task is outside the skill's documented scope.
When should I use this skill?
Guidelines for proper localization of VS Code extensions, following VS Code extension development guidelines, libraries and good practices
What you get
Actionable workflows and conventions from SKILL.md for vscode-ext-localization.
- Localized nls files
- Translated package.json contributions
By the numbers
- Covers three VS Code localization approaches depending on resource type
Files
VS Code extension localization
This skill helps you localize every aspect of VS Code extensions
When to use this skill
Use this skill when you need to:
- Localize new or existing contributed configurations (settings), commands, menus, views or walkthroughs
- Localize new or existing messages or other string resources contained in extension source code that are displayed to the end user
Instructions
VS Code localization is composed by three different approaches, depending on the resource that is being localized. When a new localizable resource is created or updated, the corresponding localization for all currently available languages must be created/updated.
1. Configurations like Settings, Commands, Menus, Views, ViewsWelcome, Walkthrough Titles and Descriptions, defined in package.json -> An exclusive package.nls.LANGID.json file, like package.nls.pt-br.json of Brazilian Portuguese (pt-br) localization 2. Walkthrough content (defined in its own Markdown files) -> An exclusive Markdown file like walkthrough/someStep.pt-br.md for Brazilian Portuguese localization 3. Messages and string located in extension source code (JavaScript or TypeScript files) -> An exclusive bundle.l10n.pt-br.json for Brazilian Portuguese localization
Related skills
How it compares
Use vscode-ext-localization over generic i18n skills when working specifically with VS Code extension package.json contributions and nls file structure.
FAQ
What does vscode-ext-localization do?
Guidelines for proper localization of VS Code extensions, following VS Code extension development guidelines, libraries and good practices
When should I use vscode-ext-localization?
Guidelines for proper localization of VS Code extensions, following VS Code extension development guidelines, libraries and good practices
Is vscode-ext-localization safe to install?
Review the Security Audits panel on this page before installing in production.