blog-localize
Cultural adaptation for translated content. Run AFTER blog-translate completes. Adjusts brand examples, CTAs, legal references, and formality for the target market (German, French, Japanese, Spanish, etc.). Deep cultural adaptation of translated blog posts. Goes beyond translation to swap brand examples, adapt CTAs, substitute legal references, localize statistic sources where possible, and adjust formality (Sie/du, tu/vous, formal/informal). Built-in profiles for DACH, Francophone, Hispanic, and Japanese markets, plus a custom-locale template. Makes content feel locally authored, not translat
npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill blog-localize --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Blog Localize, Cultural Deep-Adaptation Takes a translated blog post and performs cultural adaptation so the result feels like it was written for the target market, not translated into it. This is the layer above `blog-translate`: it replaces examples, adjusts tone, swaps references, and localizes the entire reading experience. ## Key References - `../blog-translate/references/cultural-adaptation.md`, the shared cultural profiles file with substitution tables for DACH, Francophone, Hispanic, Japanese, and a custom template. Do not duplicate this file. ## When to Use - Right after `blog-translate` produces a base translation. - When existing translated content reads like "translated from English". - When targeting a specific market, not just a language. - When content needs local statistics, examples, and brand references. ## Workflow ### Phase 1: Locale Understanding 1. Parse the locale code. Accept full codes (`de-DE`, `fr-CA`, `es-MX`, `pt-BR`, `zh-TW`) or plain language codes (`de`, `fr`). 2. Load the cultural profile from `../blog-translate/references/cultural-adaptation.md`. - If the locale has a profile, use it. - If not, follow the "Custom-locale template" section in that
- Key References
- When to Use
- Workflow
- Phase 1: Locale Understanding
- Phase 2: Cultural Audit
- Phase 3: Adaptation
- Phase 4: Quality Verification
- Phase 5: Save and Report
- Error Handling
- Cross-References
What does the blog-localize skill do?
Cultural adaptation for translated content. Run AFTER blog-translate completes. Adjusts brand examples, CTAs, legal references, and formality for the target market (German, French, Japanese, Spanish, etc.). Deep cultural adaptation of translated blog posts. Goes beyond translation to swap brand examples, adapt CTAs, substitute legal references, localize statistic sources where possible, and adjust formality (Sie/du, tu/vous, formal/informal). Built-in profiles for DACH, Francophone, Hispanic, and Japanese markets, plus a custom-locale template. Makes content feel locally authored, not translat
How do I install it?
Run `npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill blog-localize --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 Infrasity-Labs/dev-gtm-claude-skills, a repository with 97 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.