Agent skill · Security

i18n-readiness-review

Review a product/codebase for internationalization readiness before you localize. Use when asked if a product is ready to localize, to review i18n readiness, find hard-coded strings/locale bugs, or prep for going multilingual. Produces a readiness audit — externalized strings, locale-aware formatting, layout/expansion, encoding/RTL, and a prioritised list of i18n fixes to make before translation starts.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill i18n-readiness-review --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/i18n-readiness-review/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# i18n Readiness Review Skill Localizing a product that isn't *internationalized* fails expensively — translators hit hard-coded strings, layouts break on longer languages, dates show in the wrong format, and RTL shatters the UI. i18n is the engineering groundwork; localization is the content. This skill audits whether the product is ready, so you fix the foundations *before* paying to translate into the cracks. ## Required Inputs Ask for these only if they aren't already provided: - **The product** — web/app/codebase, stack/framework (i18n tooling differs). - **Target languages** — especially if any need RTL (Arabic/Hebrew), CJK (Chinese/Japanese/Korean), or are long (German/Finnish). - **What you can share** — code snippets, UI screenshots, or a description of how strings/formatting are handled today. ## Output Format ### i18n Readiness: [product] A readiness audit across the dimensions that break localization, each with status (🟢 ready / 🟡 partial / 🔴 blocker) and the fix: | Dimension | Check | Status | Fix | |---|---|---|---| | **String externalization** | no user-facing text hard-coded; all in resource files / i18n keys | | move strings to a catalog; no concatenated sentenc

What's inside
Steps it walks through
  1. Required Inputs
  2. Output Format
  3. i18n Readiness: [product]
  4. Quality Checks
  5. Anti-Patterns
  6. Based On
More from pm-claude-skills
All skills →
About this skill
What does the i18n-readiness-review skill do?

Review a product/codebase for internationalization readiness before you localize. Use when asked if a product is ready to localize, to review i18n readiness, find hard-coded strings/locale bugs, or prep for going multilingual. Produces a readiness audit — externalized strings, locale-aware formatting, layout/expansion, encoding/RTL, and a prioritised list of i18n fixes to make before translation starts.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill i18n-readiness-review --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going