multi-lang-readme

Name: multi-lang-readme
Author: yangsonhung

github.com/yangsonhungDocuments1860 installsUpdated 12w ago

About multi-lang-readme

A skill for translating existing README files into bilingual or multilingual versions, intended for teams maintaining project documentation. It preserves Markdown structure, links, and code blocks, and adds language-switch navigation; it is not intended for translating other document types.

Key features

01Translate READMEs into multiple target languages
02Preserve Markdown structure, links, and code blocks
03Name translated files with language suffixes
04Add or update language-switch links
05Check filenames, link paths, and formatting

Use cases

01Create an English and Chinese README set
02Translate a README into Japanese or another supported language
03Add reciprocal navigation across translated READMEs

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/yangsonhung/awesome-agent-skills --skill multi-lang-readme

After installing, type/multi-lang-readmein Claude Code to confirm it loaded.

Details

From the project README

Multi-Lang README

Overview

Create multilingual README files by translating an existing README while preserving Markdown structure, links, code blocks, and language-switch navigation. The workflow supports bilingual and multilingual README sets without rewriting unrelated project documentation.

When to Use

Use this skill when the user asks for:

Bilingual README creation (for example English + Chinese)
Multilingual README generation
Translating an existing README into one or more target languages
Standardized language-switch links across README files

Do not use

Do not use this skill for:

Translating arbitrary non-README documents
Rewriting product requirements or legal documents
Content generation tasks unrelated to README translation

Instructions

Locate the source README file to translate (ask user if ambiguous).
Confirm target language(s) and desired canonical README language.
Translate content while preserving markdown, links, and code blocks.
Write translated files using language suffix conventions.
Add or update language-switch links at the top of each README.
Verify filenames, link paths, and formatting before final output.

Supported Languages

Code	Language
en	English
de	German
ja	Japanese
ko	Korean
zh-CN	Chinese

Workflow

Step 1: Detect README

Find the source README:

Check root directory for README.md
If multiple README files exist, ask which file should be translated

Step 2: Read README Content

Read full markdown content, including:

Title
Badges
All sections (Features, Installation, Usage, Contributing, License, etc.)
Code blocks
Links

Step 3: Confirm Target Language

Ask user which language(s) to translate to. Default assumptions:

README.md should always be in English as the canonical version
If current README is in Chinese (or any non-English), translate it to English first
After English version is established, add other language versions as requested

If user says "create bilingual README" without specifying:

Translate existing README to English first (replace or create README.md)
Then add Chinese version (README.zh-CN.md)

Step 4: Translate with AI

Translate with these rules:

Preserve markdown formatting
Keep code blocks unchanged
Translate section titles to target language
Keep internal links (relative paths) as-is
For external links, use target language anchor text if appropriate

Step 5: Create Translated README

Important: keep README.md as canonical English unless the user explicitly asks for another convention.

English: README.md (create or replace with English version)
German: README.de.md
Japanese: README.ja.md
Korean: README.ko.md
Chinese: README.zh-CN.md

If the original README is non-English and user agrees, replace it with English README.md.

Step 6: Add Language Switcher

Update original README to include language switcher at the top:

**English** | [中文](README.zh-CN.md) | [Deutsch](README.de.md) | [日本語](README.ja.md) | [한국어](README.ko.md)

Add below the title or badges, before the main content.

Step 7: Update Translated README

Add reciprocal link in the translated README:

**[Original](README.md)** | [中文](README.zh-CN.md)

Language Code Reference

en    → no suffix (README.md)
de    → README.de.md
ja    → README.ja.md
ko    → README.ko.md
zh-CN → README.zh-CN.md

Common Triggers

"create bilingual README"
"create English and Chinese README"
"translate README to Japanese"
"add German version of README"
"add README.zh-CN.md"

Comments

Markdown supported

Details

Author: yangsonhung
Repository: yangsonhung/awesome-agent-skills
Category: Documents
Installs: 60
GitHub stars: 18

Report

More skills

All skills

handoff

github.com/mattpocock

1.1M

Compact the current conversation into a handoff document for another agent to pick up

lark-doc

open.feishu.cn

823.9k

Operate on Feishu cloud documents (Docx / Wiki): read, create, and edit documents; insert or download image attachments; and work with mind notes. Use when the user provides a document URL/token (including /docx/ or /wiki/ on doubao.com); route by URL path/token rather than domain. `/page/<token>` is a Miaoda app, not a Feishu cloud document. Route embedded document resources according to the unified rules in the reading reference. Use lark-drive for standalone comment operations; use docs +fetch to read comments alongside the main text. Operations on spreadsheet or Base internal data are outside this skill.

lark-drive

open.feishu.cn

823.2k

Feishu cloud storage (Drive): manage Drive files and folders, including uploads/downloads, folder creation, copying/moving/deleting, viewing metadata, checking permission settings, comments/permissions/subscriptions, titles, versions, Feishu document security labels (secure labels), and local file imports. Use when users need to organize Drive folders, handle cloud storage resource URLs/tokens, identify link types/actual tokens/titles, or import Word/Markdown/Excel/CSV/PPTX/.base as docx/sheet/bitable/slides. Route doubao.com cloud storage URLs/tokens by resource path and token too; do not fall back to WebFetch. Not responsible for: editing document content (use lark-doc), spreadsheet/Base table data operations (use lark-sheets/lark-base), knowledge space node/member management (use lark-wiki), or native Markdown file read/write/patch/diff (use lark-markdown).

lark-sheets

open.feishu.cn

821.8k

Feishu Spreadsheets: create and operate spreadsheets. Supports worksheets and row/column structures (add/delete/merge/size/hide/freeze/group), cell read/write (values/formulas/styles/comments/cell images), range copy/move/sort/fill, find and replace, bulk updates, and creating and maintaining objects such as charts, pivot tables, conditional formatting, filters and filter views, dropdown lists, sparklines, and floating images. Also supports formula validation, restoring historical versions, and importing/exporting local Excel/CSV files and Feishu spreadsheets. Use when users need to create or edit spreadsheets, summarize and visualize data, format spreadsheets, calculate formulas (including migrating Excel formulas), or build financial models (DCF, three statements, budgets, Sensitivity, etc.). For multidimensional tables (Base/bitable), use lark-base. If users want to search for spreadsheet files in cloud storage (Drive/cloud storage) by name or keyword, use lark-drive's drive +search to locate resources first. When users provide a doubao.com /sheets/ URL/token, use this skill directly; do not fall back to WebFetch because the domain is not Feishu. Routing is based on the URL path pattern and token, not the domain.