agentleFS
gaznilgaznil/seo-skills-by-gaznil/skills/blog-localize/SKILL.md

blog-localize

Skill0 starsChanged 3 months agoMITView on GitHub

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 translated. Use when user says "localize blog", "blog localize", "cultural adaptation", "adapt for Germany", "adapt for France", "lokalisieren", "localiser", "adaptar".

2 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

18 rules. About 0 are common, 17 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈17

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When existing translated content reads like "translated from English".

    line 45
  2. Distinctive:

    When targeting a specific market, not just a language.

    line 46
  3. Distinctive:

    When content needs local statistics, examples, and brand references.

    line 47
  4. Distinctive:

    If the locale has a profile, use it.

    line 57
  5. Distinctive:

    If not, follow the "Custom-locale template" section in that reference to build a minimal profile inline.

    line 58
  6. Distinctive:

    Read the translated post and identify adaptation targets.

    line 60
  7. Distinctive:

    Use WebSearch to find local case studies, brands, or scenarios.

    line 87
  8. Distinctive:

    If no local equivalent exists, keep the original but add local context ("In the German market, the equivalent dynamic is X").

    line 89
  9. Very specific:

    Search for equivalent local statistics ([topic] statistik [country] 2025 2026).

    line 94
  10. Distinctive:

    If local data exists, swap the source and the figure together.

    line 96
  11. Distinctive:

    If not, keep the original stat but mark its geographic scope ("In the US, ...").

    line 98
  12. Distinctive:

    Never strip source attribution.

    line 100
  13. Distinctive:

    Use culturally appropriate action verbs.

    line 108
  14. Distinctive:

    Ensure consistent formal or informal address throughout the entire document.

    line 115
  15. Distinctive:

    Add local compliance notes where they help the reader.

    line 123
  16. Distinctive:

    Remove irrelevant foreign regulatory references.

    line 124
  17. Distinctive:

    All critical adaptation targets addressed.

    line 140
  18. Distinctive:

    No remaining foreign-origin markers.

    line 142

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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. 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 reference to build a minimal profile inline.
  3. Read the translated post and identify adaptation targets.

Phase 2: Cultural Audit

Scan for elements that signal foreign origin:

ElementWhat to look for
Brand examplesUS or UK brands with no relevance locally
Statistics sourcesUS-only studies and surveys
CTAsAmerican-style aggressive calls-to-action
IdiomsLiterally translated English expressions
Legal referencesForeign laws (CCPA, FTC) where local law applies (DSGVO, RGPD)
Cultural referencesForeign holidays, events, customs
Currency and pricingUSD without conversion or context
ToneToo casual or too formal for the target market
Address formInconsistent Sie/du, tu/vous, formal/informal

Output an audit report listing every target with severity (critical, recommended, optional).

Phase 3: Adaptation

3a. Example Substitution

Swap foreign examples for local equivalents:

  • Use WebSearch to find local case studies, brands, or scenarios.
  • Replace inline, preserving the same argument and structure.
  • If no local equivalent exists, keep the original but add local context ("In the German market, the equivalent dynamic is X").

3b. Statistics Localization

  • Search for equivalent local statistics ([topic] statistik [country] 2025 2026).
  • If local data exists, swap the source and the figure together. Keep one named source per claim.
  • If not, keep the original stat but mark its geographic scope ("In the US, ...").
  • Never strip source attribution.

3c. CTA Adaptation

Rewrite calls-to-action per the cultural profile:

  • Adjust aggressiveness level (DACH and JA prefer informational, US prefers imperative).
  • Use culturally appropriate action verbs.
  • Adapt urgency framing.

3d. Tone Calibration

  • Match formality per profile (DACH defaults to Sie for B2B, du for B2C lifestyle; FR defaults to vous; JA shifts register sharply by audience).
  • Ensure consistent formal or informal address throughout the entire document.
  • Match local content-style conventions.

3e. Legal and Regulatory Context

  • Replace references to foreign laws with local equivalents (CCPA becomes DSGVO in DE, RGPD in FR, LGPD in BR).
  • Add local compliance notes where they help the reader.
  • Remove irrelevant foreign regulatory references.

3f. Brand Example Swaps (Quick Map)

Profiles in ../blog-translate/references/cultural-adaptation.md provide substitution tables. Common examples:

Source (US)DACHFRES (Spain)LATAMJA
WalmartMediaMarktCarrefourEl Corte InglesWalmart MXAeon
TargetSaturnAuchanHipercorLiverpoolIto-Yokado
FTCBundeskartellamtDGCCRFCNMCProfeco (MX)JFTC
CCPADSGVORGPDRGPDLGPD (BR)APPI

Phase 4: Quality Verification

  • All critical adaptation targets addressed.
  • Tone is consistent throughout.
  • No remaining foreign-origin markers.
  • Statistics have valid sources (original or localized).
  • CTAs match cultural expectations.
  • Formal or informal address is consistent end to end.
  • Content still supports the same argument as the original.
  • SEO elements remain optimized (keywords, meta, headings).
  • Word count is within the expected ratio for the language pair.

Phase 5: Save and Report

  1. Save the localized version. Default: overwrite the translated file. Optional: save as {slug}-localized.{ext} if the user wants to keep the pre-localization version.
  2. Present the summary:

    ## Localization complete: [Title]
    
    ### Target locale: [locale-code] ([locale-name])
    
    ### Adaptations made
    | Type | Count | Examples |
    |------|-------|----------|
    | Brand examples | [N] | Walmart -> MediaMarkt |
    | Statistics | [N] | US survey -> DACH survey |
    | CTAs | [N] | "Buy now" -> "Jetzt entdecken" |
    | Tone adjustments | [N] | Casual -> Sie |
    | Legal references | [N] | CCPA -> DSGVO |
    | Cultural references | [N] | Thanksgiving -> Weihnachtsgeschaeft |
    
    ### Cultural fit score
    - Naturalness: [1-10]
    - Market relevance: [1-10]
    - Tone match: [1-10]
    - Overall: [N]/30
    
    ### Remaining recommendations
    - [Optional adaptations not applied]

Error Handling

ScenarioAction
No cultural profile for the localeBuild a minimal profile from the custom-locale template, proceed
File is not in the expected languageWarn the user, offer to translate first
No local statistics availableKeep the original stat with a geographic-scope note
Locale code ambiguous (e.g., pt)Ask: "Did you mean pt-BR (Brazil) or pt-PT (Portugal)?"

Cross-References

  • Pre-step (translation): /blog translate <file> --to <code>
  • QA across language versions: /blog locale-audit <directory>
  • One-command pipeline: /blog multilingual <topic> --languages <codes>

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.