Agent skill · Content & Marketing

blog-localize

Deep cultural adaptation of translated blog posts. Run after blog-translate completes. 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. Use when user says "localize blog", "blog localize", "cultural adaptation", "adapt for Germany", "lokalisieren", "localiser", "adaptar".

AgriciDanielgithub.com/AgriciDanielGitHub ↗
claude-codeMIT
Install
npx skills add AgriciDaniel/claude-blog --skill blog-localize --agent claude-code

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

Facts
Files in the skill folder: 1
SKILL.md size: 9 KB
Bundled scripts: none
Version: 2.1.1
Declared author: AgriciDaniel
Requires: Standalone within claude-blog. Invoked by blog-multilingual.
Path: skills/blog-localize/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,566
Language: Python

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

From the SKILL.md

# 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. > Adapted from `claude-blog-multilingual` by Chris Mueller (Pro Hub Challenge, > March 2026). Original: https://github.com/Chriss54/multilingual-int ## 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 with the shared multilingual locale rules used by `blog-translate`, `blog-multilingual`, and `blog-locale-audit`: ISO 639-1 language in lowercas

What's inside
Steps it walks through
  1. Key References
  2. When to Use
  3. Workflow
  4. Phase 1: Locale Understanding
  5. Phase 2: Cultural Audit
  6. Phase 3: Adaptation
  7. Phase 4: Quality Verification
  8. Phase 5: Save and Report
  9. Error Handling
  10. Cross-References
More from claude-blog
All skills →
About this skill
What does the blog-localize skill do?

Deep cultural adaptation of translated blog posts. Run after blog-translate completes. 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. Use when user says "localize blog", "blog localize", "cultural adaptation", "adapt for Germany", "lokalisieren", "localiser", "adaptar".

How do I install it?

Run `npx skills add AgriciDaniel/claude-blog --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 AgriciDaniel/claude-blog, a repository with 1,566 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