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 citation capsules. 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", "traducir",
npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill blog-translate --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 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. ## 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). 2. Auto-detect source language. Order of preference: - Frontmatter `lang` field. - HTML `lang` attribute. - Content analysis (script, common stop words). 3. Parse target languages from `--to` as comma-separated ISO 639-1 codes (`de,fr,es,ja,pt-BR`). If `--to` is missing, ask the user once: "Which languages should I translate to? Provide ISO 639-1 codes (e.g., de, fr, es, ja, pt-BR)." 4. Validate every code. Reject invalid ones with a suggestion (`jp` becomes "Did you mean `ja` for Jap
- Key References
- Workflow
- Phase 1: Input Parsing
- Phase 2: Content Analysis
- Phase 3: Keyword Localization
- Phase 4: Translation
- Phase 5: Post-Processing
- Phase 6: Translation-Quality Guardrails
- Phase 7: Delivery
- Error Handling
- Cross-References
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 citation capsules. 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", "traducir",
How do I install it?
Run `npx skills add Infrasity-Labs/dev-gtm-claude-skills --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 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.