What do I need to use Localization Brief?

The product / content; What it is; Goal & depth; Known constraints.

Is Localization Brief free to use?

Yes — run it free in the browser playground (no API key needed for the sponsored trial, or bring any provider key), or install it into Claude Code, Cursor, ChatGPT and more via npx pm-claude-skills. MIT-licensed and open source.

Localization Brief

Q: How do I know the Localization Brief output is good?

The skill verifies itself against its own quality checks: Distinguishes translate vs. adapt vs. rebuild per element — not "translate everything"; Covers formats, imagery, payments, legal, and SEO — not just UI strings; Region (not just language) is specified where it changes things; Priorities are sequenced to the goal (market test vs. full launch).

🔵 Stable🕐 updated 2026-10-06 🔷 SkillSpec L3 pm-localization

Plan the localization of a product/content for a new market — beyond translating the words. Use when asked to localize a product, plan market entry localization, prepare a localization brief, or figure out what to adapt for a new region. Produces a brief — target locales, what to translate vs. adapt vs. rebuild (UI, content, formats, imagery, payments, legal), priorities, and the risks/cultural pitfalls.

▶ Run it free — no key needed 📝 Grade your existing draft ⬇ Add to Claude (works in Duet) 📱 Use as an app View SKILL.md ↗ What changed

🗣 Say this to your agent

“Localize a product.”“Plan market entry localization.”“Prepare a localization brief.”“Figure out what to adapt for a new region.”

What to give it

▸The product / content — and the target locale(s) (language + region — fr-FR vs fr-CA matters).

▸What it is — SaaS UI, marketing site, app, docs, campaign — sets what needs adapting.

▸Goal & depth — testing a market (light) vs. full local presence (deep).

▸Known constraints — budget, what's already internationalized (i18n-ready or not).

✅ The bar it holds itself to

Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.

✓Distinguishes translate vs. adapt vs. rebuild per element — not "translate everything"

✓Covers formats, imagery, payments, legal, and SEO — not just UI strings

✓Region (not just language) is specified where it changes things

✓Priorities are sequenced to the goal (market test vs. full launch)

✓Names the specific cultural/regulatory pitfalls for this market

✓Includes native + in-market review in the QA plan

⚠️ What it refuses to do

Do not equate localization with translation — payments, legal, formats, and imagery decide whether it feels native

Do not ignore region — fr-FR ≠ fr-CA, es-ES ≠ es-MX; the variant changes copy, formats, and norms

Do not localize SEO by translating keywords — research how locals actually search

Do not skip local payment methods — the best-localized UI converts nothing if they can't pay how they pay

Do not launch without in-market native review — machine/relay translation misses the embarrassing stuff

Install

npx pm-claude-skills add --agent claude   # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y -p pm-claude-skills pm-claude-skills-mcp

Related skills

🔌 Embed this skill

Drop this on your blog, docs, or site — it renders a "Run this skill" card:

<div data-pm-skill="localization-brief"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>

💬 Discussion

Localization Brief is one of 1326 open-source professional AI agent skills — all SkillSpec L3. Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog