Agent skill

Blog Multilingual

by Infrasity-Labs in Infrasity-Labs/dev-gtm-claude-skills

One-command multilingual blog creation. An agent skill from Infrasity-Labs/dev-gtm-claude-skills.

MITAuto-check passedWriting & Content

Install Blog Multilingual

skills CLI
$ npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill blog-multilingual -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Infrasity-Labs/dev-gtm-claude-skills blog-multilingual --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Infrasity-Labs/dev-gtm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/blog-multilingual .claude/skills/blog-multilingual && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
blog-multilingual
GitHub stars
136
Used in
1 other repo
Token cost
~2.6k tokens
SKILL.md length
784 words
Files
1
Skills in repo
26
Repo updated
First seen
Licence
MIT

At a glance

One-command multilingual blog creation. An agent skill from Infrasity-Labs/dev-gtm-claude-skills.

  • Works in 6 steps: Configuration → Write Original Blog → Translate to All Target Languages → …
  • User says multilingual blog
  • SKILL.md covers Dependencies, Command Syntax, Workflow and Cross-References, plus 2 more sections
  • Reaches sitemaps.org and w3.org

What it does

Blog Multilingual is an agent skill from Infrasity-Labs/dev-gtm-claude-skills. One-command multilingual blog creation. Writes a blog post, translates it into user-specified languages, applies cultural adaptation, and emits hreflang tags, sitemap entries, and a CMS-ready language map. The complete write-to-publish pipeline for international content. Orchestrates blog-write, blog-translate, blog-localize, and (optionally) seo-hreflang. Use when user says "multilingual blog", "blog multilingual", "write in multiple languages", "international blog", "mehrsprachiger Blog", "blog multilingue"…

Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires claude-blog (blog-write). Optional integration with claude-seo (seo-hreflang) for richer hreflang validation.

It sits in Writing & Content, covering Technical SEO, Translation and Blog and article writing. The repository describes itself as: Open-source Claude skills for GEO, AI discoverability, and developer GTM workflows. Built for developer-focused companies that want their documentation to be found, parsed, and… The licence is MIT.

When your agent uses it

  • User says multilingual blog
  • Blog multilingual
  • Write in multiple languages
  • International blog

Example prompts

  • “multilingual blog”
  • “blog multilingual”
  • “write in multiple languages”
  • “/blog-multilingual”

Requirements

  • Compatibility (from SKILL.md): Requires claude-blog (blog-write). Optional integration with claude-seo (seo-hreflang) for richer hreflang validation.

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Configuration
  2. Write Original Blog
  3. Translate to All Target Languages
  4. Cultural Adaptation
  5. International SEO Generation
  6. Delivery Summary

What it can do on your machine

Read from SKILL.md and the folder at commit 02cfefb. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are json, html and xml).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • sitemaps.org
    • w3.org
    • schema.org

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires claude-blog (blog-write). Optional integration with claude-seo (seo-hreflang) for richer hreflang validation.

    From compatibility in the SKILL.md frontmatter.

Context cost

Blog Multilingual loads about 2.6k tokens when it runs. Until then it costs about 147 tokens; SKILL.md has 784 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~147
When it runs · the whole SKILL.md, loaded when a task matches
~2.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Infrasity-Labs/dev-gtm-claude-skills at commit 02cfefb, republished under its MIT licence (© Infrasity-Labs). 784 words, ~2,577 tokens.

Download SKILL.mdSave it as .claude/skills/blog-multilingual/SKILL.md (or your agent's skills folder).
name
blog-multilingual
description
One-command multilingual blog creation. Writes a blog post, translates it into user-specified languages, applies cultural adaptation, and emits hreflang tags, sitemap entries, and a CMS-ready language map. The complete write-to-publish pipeline for international content. Orchestrates blog-write, blog-translate, blog-localize, and (optionally) seo-hreflang. Use when user says "multilingual blog", "blog multilingual", "write in multiple languages", "international blog", "mehrsprachiger Blog", "blog multilingue", "blog multilingue", "create blog in German and French".
compatibility
Requires claude-blog (blog-write). Optional integration with claude-seo (seo-hreflang) for richer hreflang validation.
user-invokable
true
argument-hint
<topic> --languages <comma-separated-codes>

Blog Multilingual, One-Command International Publishing

The flagship multilingual orchestrator. Combines blog writing, translation, cultural adaptation, and full international SEO into a single command. Produces publication-ready blog posts in every target language with hreflang tags, localized JSON-LD schema, and CMS-integration metadata.

Dependencies

Invoked internally by this orchestrator:

ComponentSourceRequired
blog-writeclaude-blog (this plugin)Yes
blog-translateclaude-blog (this plugin)Yes
blog-localizeclaude-blog (this plugin)Yes (when --localize is on, default)
seo-hreflangclaude-seo (sibling plugin)No, falls back to a self-contained generator

If seo-hreflang is not installed, the orchestrator emits hreflang tags using its own minimal generator (Phase 5 below) and notes the limitation in the delivery summary. Hreflang validation in that case is structural only, not the deeper validation seo-hreflang provides.

Command Syntax

/blog multilingual <topic> --languages <lang1,lang2,...> [--source <lang>] [--no-localize] [--format <md|mdx|html>]
ArgumentRequiredDefaultDescription
<topic>Yes,Blog topic or working title
--languagesYes,Comma-separated ISO 639-1 codes (e.g. de,fr,es,ja,pt-BR)
--sourceNoenSource language to write the original in
--no-localizeNooffSkip cultural adaptation (translation only)
--formatNoautoOutput format: md, mdx, or html

If --languages is missing, ask the user once before running anything: "Which languages should the blog be published in? Provide ISO 639-1 codes separated by commas (e.g., de,fr,es,ja,pt-BR). The post will be written in <source> first, then translated."

Workflow

Phase 1: Configuration
  1. Parse arguments. Extract topic, target languages, source, format.
  2. Validate each language code against ISO 639-1 (region suffixes like pt-BR, es-MX, zh-TW are also accepted).
  3. Detect output format from the project (frontmatter convention, file extensions, framework hints) or use --format.
  4. Resolve source language. If a target language equals --source, drop it from the translation list with a notice.
  5. Create the output directory inside the current working directory:
    multilingual/
      {source-lang}/
      {lang-1}/
      {lang-2}/
      ...
    Output MUST stay inside the project root. Never write outside the cwd.

Progress: Phase 1: Configuration complete, [N] languages selected ([codes])

Phase 2: Write Original Blog

Invoke the blog-write sub-skill (route through /blog write so all existing rules apply: template auto-selection, sourced statistics, citation capsules, FAQ schema, internal-link zones, charts, image embedding). Pass the topic and any blog-write parameters surfaced by the user.

Save the original to multilingual/{source-lang}/{slug}.{ext}.

Progress: Phase 2: Original written, multilingual/{source-lang}/{slug}.{ext}

Phase 3: Translate to All Target Languages

For each target language, invoke blog-translate:

  • Input: the original blog post produced in Phase 2.
  • Target: the specific language code.
  • Run targets in parallel where the runtime supports it (one Task per language) to reduce wall-clock time.

Save translations to multilingual/{lang}/{localized-slug}.{ext}.

Progress: Phase 3: Translating to [lang] ([X]/[N]) per language, then Phase 3: All translations complete.

Phase 4: Cultural Adaptation

If --no-localize is NOT set, invoke blog-localize for every translated post:

  • Input: the translated blog post.
  • Locale: the target language or region code.
  • Run in parallel.

Update files in place. The localizer swaps brand examples, adapts CTAs, substitutes legal references, and adjusts formality. See ../blog-localize/SKILL.md for the full adaptation pass.

Progress: Phase 4: Cultural adaptation complete for [N] languages.

Show full SKILL.md (303 more words)Show less
Phase 5: International SEO Generation

Generate three artifacts plus localized schema. If the seo-hreflang skill from claude-seo is installed, delegate validation to it. Otherwise use the self-contained generator below.

5a. Hreflang Tags (HTML)

Copy-paste ready tags for <head>:

html
<!-- Hreflang tags. Paste into <head> of each language version. -->
<link rel="alternate" hreflang="{source}" href="{source-url}" />
<link rel="alternate" hreflang="{lang-1}" href="{lang-1-url}" />
<link rel="alternate" hreflang="{lang-2}" href="{lang-2-url}" />
<link rel="alternate" hreflang="x-default" href="{source-url}" />

Rules (mirrored from seo-hreflang):

  • Every page references all alternates including itself (self-referencing).
  • x-default points to the source-language version.
  • All URLs use the same protocol (HTTPS) and trailing-slash convention.
  • Bidirectional: every relationship is reciprocal.

Save to multilingual/hreflang-tags.html.

5b. Hreflang Sitemap Fragment
xml
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
        xmlns:xhtml="http://www.w3.org/1999/xhtml">
  <url>
    <loc>{source-url}</loc>
    <xhtml:link rel="alternate" hreflang="{source}" href="{source-url}" />
    <xhtml:link rel="alternate" hreflang="{lang-1}" href="{lang-1-url}" />
    <xhtml:link rel="alternate" hreflang="x-default" href="{source-url}" />
  </url>
  <!-- Repeat one <url> block per language version -->
</urlset>

Save to multilingual/hreflang-sitemap.xml.

5c. Hreflang Map (JSON)

Machine-readable mapping for CMS integration:

json
{
  "sourceSlug": "how-to-avoid-ai-slop",
  "sourceLanguage": "en",
  "generatedDate": "YYYY-MM-DD",
  "versions": [
    {
      "lang": "en",
      "slug": "how-to-avoid-ai-slop",
      "file": "en/how-to-avoid-ai-slop.md",
      "title": "How to Avoid AI Slop in 2026",
      "description": "..."
    },
    {
      "lang": "de",
      "slug": "wie-man-ki-slop-vermeidet",
      "file": "de/wie-man-ki-slop-vermeidet.md",
      "title": "KI-Slop vermeiden in 2026",
      "description": "..."
    }
  ],
  "hreflang": {
    "method": "html",
    "x-default": "en"
  }
}

Save to multilingual/hreflang-map.json.

5d. Localized Schema (Optional)

If the user asks, or if a frontmatter schema: true flag is present, attach or update JSON-LD on every language version with inLanguage and translationOfWork fields:

json
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "[Localized title]",
  "description": "[Localized description]",
  "inLanguage": "[lang-code]",
  "isPartOf": { "@type": "Blog", "inLanguage": "[lang-code]" },
  "translationOfWork": {
    "@type": "BlogPosting",
    "inLanguage": "[source-lang]",
    "url": "[source-url]"
  }
}

Use the existing /blog schema sub-skill if richer schema (FAQ, Person, Breadcrumb) is wanted on each version.

Phase 6: Delivery Summary
## Multilingual blog complete: [Title]

### Original
- Language: [source]
- File: multilingual/{source}/{slug}.{ext}

### Translations
| Language | File | Localized | Keywords adapted |
|----------|------|-----------|------------------|
| de | multilingual/de/{slug}.md | yes | [N] |
| fr | multilingual/fr/{slug}.md | yes | [N] |
| es | multilingual/es/{slug}.md | yes | [N] |

### International SEO assets
- multilingual/hreflang-tags.html
- multilingual/hreflang-sitemap.xml
- multilingual/hreflang-map.json
- Localized schema embedded per version (if requested)

### Total
- [N] posts in [N] languages
- [N] SEO assets generated

### Next steps
- Replace `{url}` placeholders in hreflang tags with your real URLs.
- Merge `hreflang-sitemap.xml` into your existing sitemap.
- Run `/blog locale-audit multilingual/` to verify completeness.
- Resolve `[INTERNAL-LINK]` placeholders with locale-specific URLs.
- If claude-seo is installed, run `/seo hreflang multilingual/` for
  deeper validation.

Cross-References

WhenRun
To regenerate or reword the source/blog write <topic>
To translate one existing file only/blog translate <file> --to <codes>
To deepen cultural fit on one file/blog localize <file> --locale <code>
To audit a multilingual directory/blog locale-audit <directory>
For deeper hreflang validation/seo hreflang <directory> (claude-seo, optional)

Error Handling

ScenarioAction
blog-write missingError: "This skill requires blog-write. Reinstall claude-blog."
One translation failsComplete the rest, report partial results, suggest a retry command
Source language equals a targetSkip that target, log a notice
More than 10 target languagesWarn about wall-clock time, proceed if confirmed
seo-hreflang not installedUse the self-contained generator, note it in the summary

Commands Recap

CommandPurpose
/blog multilingual <topic> --languages de,fr,esWrite source, translate, localize, emit hreflang assets
/blog translate <file> --to de,fr,esTranslate one file into target languages
/blog localize <file> --locale de-DECultural deep-adaptation of one translated file
/blog locale-audit <directory>Multilingual QA across a directory

© Infrasity-Labs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/blog-multilingual of Infrasity-Labs/dev-gtm-claude-skills.

Open the folder on GitHubat commit 02cfefb

Used in 1 other repository

We found 4 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in Infrasity-Labs/dev-gtm-claude-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Blog Multilingual next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Blog Multilingual compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Blog Multilingual this skillInfrasity-Labs/dev-gtm-claude-skills1361 repos~2.6kAutomated safety check: PassMIT
Blog Locale AuditAgriciDaniel/claude-blog2.3k1 repos~2.1kAutomated safety check: PassMIT
SEOgridaco/grida2.7k—~2.1kAutomated safety check: PassApache-2.0
Create Release Blogweb-infra-dev/rstest505—~4.7kAutomated safety check: PassMIT
Blog Post ProcessorJustin3go/justin3go.com172—~1.5kAutomated safety check: PassCustom licence
Humanizer Zhai-zixun/humanizer-zh179—~1.2kAutomated safety check: PassMIT

Similar skills

  • Blog Locale Audit

    AgriciDaniel/claude-blog

    Audit a directory of multilingual blog content for completeness, consistency, hreflang correctness, meta-tag parity, and freshness.

    2.3k GitHub starsUsed in 1 repo~2.1k tokens
    Writing & ContentAuto-check passed
  • SEO

    gridaco/grida

    SEO best practices for the Grida project across Next.js pages, blog posts, and documentation.

    2.7k GitHub stars~2.1k tokensUpdated yesterday
    Marketing & SEOAuto-check passed
  • Create Release Blog

    web-infra-dev/rstest

    Generate a narrative version release blog post from commits within a tag range.

    505 GitHub stars~4.7k tokensUpdated yesterday
    Writing & ContentAuto-check passed
  • Blog Post Processor

    Justin3go/justin3go.com

    Process Chinese blog posts for the justin3go.com VitePress blog: rename to English slug, add frontmatter and AI summary, and translate to English.

    172 GitHub stars~1.5k tokensUpdated 19 days ago
    Writing & ContentAuto-check passed
  • Humanizer Zh

    ai-zixun/humanizer-zh

    Remove signs of AI-generated, translated, or overly mechanical Chinese prose.

    179 GitHub stars~1.2k tokensUpdated 4 mo ago
    Writing & ContentAuto-check passed
  • Blog

    Chorus-AIDLC/Chorus

    Write release blog posts for Chorus — problem-first narrative, bilingual (zh/en), following the project's editorial style.

    1.2k GitHub stars~1.2k tokensUpdated yesterday
    Writing & ContentAuto-check passed

More from Infrasity-Labs/dev-gtm-claude-skills

All 26 skills in this repo
  • Brief Outline Generator

    Infrasity-Labs/dev-gtm-claude-skills

    Generates a fully structured SEO content outline (not a finished brief) and exports it as a formatted .docx Word document.

    136 GitHub stars~4k tokensUpdated 3 mo ago
    Auto-check passed
  • Content Brief

    Infrasity-Labs/dev-gtm-claude-skills

    Generates a fully structured SEO content brief for a target keyword and optionally pushes it to a Notion database.

    136 GitHub stars~2.8k tokensUpdated 3 mo ago
    Auto-check passed
  • API Docs Quality Report

    Infrasity-Labs/dev-gtm-claude-skills

    Audits any API documentation site by crawling every endpoint page and scoring each one across 5 checks: description quality, OpenAPI spec presence, body param descriptions, response codes, and…

    136 GitHub stars~2.5k tokensUpdated 3 mo ago
    Auto-check passed
  • Docs Auditor

    Infrasity-Labs/dev-gtm-claude-skills

    Audits any developer documentation site across 33 checks in 7 categories and produces a scored report (out of 100) with Pass / Warn / Fail status per check.

    136 GitHub stars~3k tokensUpdated 3 mo ago
    Auto-check passed
  • Growth Report

    Infrasity-Labs/dev-gtm-claude-skills

    Generates a 3-month SEO performance HTML report for any domain using DataForSEO data.

    136 GitHub stars~4k tokensUpdated 3 mo ago
    Auto-check passed
  • Inbox

    Infrasity-Labs/dev-gtm-claude-skills

    Email triage system that handles both one-time setup and recurring triage in a single skill.

    136 GitHub stars~4.8k tokensUpdated 3 mo ago
    Auto-check passed

Questions about Blog Multilingual

What does Blog Multilingual do?

One-command multilingual blog creation. An agent skill from Infrasity-Labs/dev-gtm-claude-skills. Blog Multilingual is an agent skill from Infrasity-Labs/dev-gtm-claude-skills. One-command multilingual blog creation.

When should I use Blog Multilingual?

Blog Multilingual fits situations like: user says multilingual blog; blog multilingual; write in multiple languages; international blog.

How do I install Blog Multilingual in Claude Code?

Run `npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill blog-multilingual -a claude-code`. Or copy the skill folder (.claude/skills/blog-multilingual in Infrasity-Labs/dev-gtm-claude-skills) into .claude/skills/blog-multilingual in your project. Claude Code loads it when a task matches its description.

How do I install Blog Multilingual in Codex?

Run `npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill blog-multilingual -a codex`. Or copy the skill folder (.claude/skills/blog-multilingual in Infrasity-Labs/dev-gtm-claude-skills) into .agents/skills/blog-multilingual in your project. Codex loads it when a task matches its description.

Can I use Blog Multilingual in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill blog-multilingual -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/blog-multilingual, .gemini/skills/blog-multilingual, .github/skills/blog-multilingual and .opencode/skills/blog-multilingual in your project.

What does Blog Multilingual need to run?

SKILL.md names no scripts, command-line tools or credentials: Blog Multilingual is instructions for the agent only. Compatibility (from SKILL.md): Requires claude-blog (blog-write). Optional integration with claude-seo (seo-hreflang) for richer hreflang validation..

Does Blog Multilingual access the network?

SKILL.md names 3 domains. In commands or code: sitemaps.org, w3.org and schema.org; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Blog Multilingual safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Blog Multilingual use?

Blog Multilingual is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Blog Multilingual use?

About 2.6k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Blog Multilingual?

Skills that share tags, products or a category with Blog Multilingual: Blog Locale Audit (AgriciDaniel/claude-blog, 2.3k stars), SEO (gridaco/grida, 2.7k stars), Create Release Blog (web-infra-dev/rstest, 505 stars) and Blog Post Processor (Justin3go/justin3go.com, 172 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Blog Multilingual?

Infrasity-Labs (a GitHub user) maintains it in Infrasity-Labs/dev-gtm-claude-skills, which has 136 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on June 28, 2026.

Source: Infrasity-Labs/dev-gtm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.