Agent skill · Code Review & Quality

blog-translate

Translate existing blog posts into one or more target languages with SEO-optimized localization. Produces native-quality translations that preserve markdown structure, frontmatter, schema JSON-LD, image and chart embeds, and evidence-backed explanations. Localizes keywords, meta tags, numbers, dates, currencies, and quote styles per locale. Flags machine-translation artifacts for review. Run BEFORE blog-localize: this handles language conversion; localize handles cultural adaptation after translation completes. Use when user says "translate blog", "blog translate", "uebersetzen", "traduire", "

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

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

Facts
Files in the skill folder: 3
SKILL.md size: 8 KB
Bundled scripts: none
Version: 2.1.1
Declared author: AgriciDaniel
Requires: Standalone within claude-blog. Invoked by blog-multilingual.
Path: skills/blog-translate/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 Translate, SEO-Optimized Blog Translation Translates an existing blog post into one or more target languages. Unlike generic translation, this skill produces SEO-optimized, publication-ready content with localized keywords, meta tags, and culturally correct formatting. > Adapted from `claude-blog-multilingual` by Chris Mueller (Pro Hub Challenge, > March 2026). Original: https://github.com/Chriss54/multilingual-int ## Key References Load on demand: - `references/translation-rules.md`, format preservation, number/date/currency formats per locale, quote handling, quality criteria. - `references/cultural-adaptation.md`, cultural profiles per locale (DACH, Francophone, Hispanic, Japanese, custom). This file is shared with `blog-localize` (do not duplicate). ## Workflow ### Phase 1: Input Parsing 1. Read the source file (markdown, MDX, or HTML) only after resolving it against the project root/current working directory. Reject symlinked paths, traversal outside the root, files over 10 MB, and binary files. 2. Auto-detect source language. Order of preference: - Frontmatter `lang` field. - HTML `lang` attribute. - Content analysis (script, common stop words). 3. Parse target languag

What's inside
Steps it walks through
  1. Key References
  2. Workflow
  3. Phase 1: Input Parsing
  4. Phase 2: Content Analysis
  5. Phase 3: Keyword Localization
  6. Phase 4: Translation
  7. Phase 5: Post-Processing
  8. Phase 6: Translation-Quality Guardrails
  9. Phase 7: Delivery
  10. Error Handling
  11. Cross-References
Ships with 2 files
  • references/cultural-adaptation.md
  • references/translation-rules.md
More from claude-blog
All skills →
About this skill
What does the blog-translate skill do?

Translate existing blog posts into one or more target languages with SEO-optimized localization. Produces native-quality translations that preserve markdown structure, frontmatter, schema JSON-LD, image and chart embeds, and evidence-backed explanations. Localizes keywords, meta tags, numbers, dates, currencies, and quote styles per locale. Flags machine-translation artifacts for review. Run BEFORE blog-localize: this handles language conversion; localize handles cultural adaptation after translation completes. Use when user says "translate blog", "blog translate", "uebersetzen", "traduire", "

How do I install it?

Run `npx skills add AgriciDaniel/claude-blog --skill blog-translate --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