One-click install
npx skills add https://github.com/shenxingy/Clade --skill blog-localize-shenxingy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blog-localize
Source: https://github.com/shenxingy/Clade/tree/main/configs/skills/blog-localize
Command: npx skills add https://github.com/shenxingy/Clade --skill blog-localize-shenxingy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Translated blog posts often feel “foreign,” with mismatched examples, CTAs, legal references, tone, and formality that reduce trust and engagement in the target market.

Core Features & Use Cases

  • Cultural deep-adaptation layer: Converts translated content into locally authored-feeling copy by replacing brand examples, idioms, CTAs, and cultural references.
  • Locale- and market-aware adjustments: Calibrates tone and address form (e.g., Sie/du, tu/vous, formal/informal) to match the target audience.
  • Regulatory and legal localization: Swaps foreign compliance references with local equivalents (e.g., CCPA → DSGVO, RGPD, LGPD).
  • Statistics localization: Finds and localizes statistics sources when possible, otherwise preserves attribution with geographic-scope notes.
  • Built-in locale profiles + custom template: Supports markets like DACH, Francophone, Hispanic, and Japanese, plus a custom-locale workflow when no direct profile exists.

Quick Start

Use blog-localize on your already-translated blog file by running: blog-localize <file> --locale <locale-code>.

Frequently Asked Questions about blog-localize

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I localize a translated blog post to sound culturally native?

Blog localization deeply adapts translated content by swapping brand examples, rewriting CTAs, removing idioms, and calibrating tone to match target market cultural norms. This process ensures your content reads as locally authored copy rather than a direct translation.

What is the best way to adapt legal references and compliance terms in multilingual content?

Adapting legal references in multilingual content requires swapping foreign compliance mentions with local regulatory equivalents, such as changing CCPA to DSGVO or LGPD. This ensures your blog content meets regional regulatory expectations and maintains local trust.

How do I calibrate tone and formality levels for different target market blogs?

Calibrating tone and formality for target market blogs involves parsing locale codes and loading specific cultural profiles to adjust address forms like Sie/du or tu/vous. This ensures the localized output matches the audience's expected formality level.

Can I localize statistics sources for markets without a predefined cultural profile?

You can localize statistics sources for custom markets using a custom-locale workflow when no direct cultural profile exists. The system attempts to find local statistical sources, otherwise it preserves original attribution with geographic-scope notes.

Does blog localization work on files that have already been translated?

Blog localization is designed specifically for post-translation workflows, meaning it processes files that have already been translated. It takes the translated text and applies deep cultural adaptation, including idiom removal and CTA rewriting, to produce a localized output.