Skills readme-i18n

📦

readme-i18n

Name: readme-i18n
Author: xixu-me

Content revision r1 Safe ⚙️ External commands🔑 Env variables

Localize README Files Safely

README translation often breaks links, badges, code examples, and anchors. This skill guides Claude, Codex, and Claude Code to create localized README variants while preserving repository mechanics.

Supports: Claude Codex Code(CC)

📊 75 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "readme-i18n" from https://skillstore.io/skills/xixu-me-readme-i18n.md and its manifest at https://skillstore.io/api/skills/xixu-me-readme-i18n/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/xixu-me-readme-i18n.md Signed manifest GET /api/skills/xixu-me-readme-i18n/manifest Signed lockfile GET /api/skills/xixu-me-readme-i18n/lockfile

Test it

Using "readme-i18n". A maintainer asks for Chinese and Spanish README variants.

Expected outcome:

Creates README.zh.md and README.es.md using the existing structure.
Adds one shared language selector to each README.
Notes preserved terms, links, badges, and assumptions.

Using "readme-i18n". A repository already has README.zh.md and needs a French variant.

Expected outcome:

Creates the French README using the established naming pattern.
Updates the existing selector instead of adding another block.
Checks same-file anchors after translated headings are written.

Using "readme-i18n". A source README changed after translations were published.

Expected outcome:

Compares the source with localized README files.
Updates changed prose without reformatting the full document.
Verifies code fence counts, links, and language selector consistency.

Security Audit

Safe

v5 • 7/8/2026 Open versioned report

All static findings are false positives caused by Markdown examples, inline-code literals, and local README quality checks. No executable command path, environment access, network access, prompt injection, or malicious intent was found in the reviewed files.

Files scanned

286

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (23)

🔑 Env variables (1)

SKILL.md:84

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/xixu-me-readme-i18n/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/xixu-me-readme-i18n/security.svg)](https://skillstore.io/skills/xixu-me-readme-i18n?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/xixu-me-readme-i18n?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/xixu-me-readme-i18n/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/xixu-me-readme-i18n.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

xixu-me. (2026). readme-i18n security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/xixu-me-readme-i18n/audits/5

BibTeX citation

@techreport{xixu-me-xixu-me-readme-i18n-2026,
  author = {xixu-me},
  title = {readme-i18n security audit report (audit version 5)},
  institution = {Skillstore},
  year = {2026},
  number = {5},
  url = {https://skillstore.io/skills/xixu-me-readme-i18n/audits/5},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "readme-i18n security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
  - name: "xixu-me"
date-released: "2026-07-08"
url: "https://skillstore.io/skills/xixu-me-readme-i18n/audits/5"
identifiers:
  - type: other
    value: "skillstore:xixu-me-readme-i18n:audit:5"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Publish Multilingual README Files

Create translated README variants that keep badges, links, code examples, and headings aligned with the source file.

Standardize Documentation Language Switchers

Add or update one language selector across README variants without duplicating selector blocks.

Update Existing Localized Documentation

Refresh localized README files after source changes while preserving prior naming patterns and unchanged technical tokens.

Try These Prompts

Translate One README

Translate README.md into Spanish. Create README.es.md. Preserve code blocks, badge URLs, commands, and file paths.

Add Language Selector

Create Chinese and Spanish README variants. Add one language selector near the top of each file.

Extend Existing Variants

README.zh.md already exists. Add README.fr.md, update the selector in place, and keep existing naming conventions.

Synchronize Changed Source

Compare README.md with existing localized README files. Update only changed prose, then verify anchors, selectors, and code fence counts.

Best Practices

Provide target languages and any glossary before localization starts.
Review translated headings and same-file anchors together.
Keep product names, package names, commands, and environment variables unchanged.

Avoid

Translating code fences, shell commands, URLs, or badge image sources.
Adding a second language selector instead of updating the existing one.
Changing section order without a repository reason.

Frequently Asked Questions

What files does this skill create?

It creates localized README sibling files, such as README.es.md, when the repository uses that pattern.

Can it update an existing language selector?

Yes. It updates an existing selector in place and avoids adding duplicate selector blocks.

Does it translate code examples?

No. It preserves code fences, inline code, commands, flags, file paths, and environment variable names.

How are same-file anchor links handled?

After headings are translated, same-file anchor links are rewritten to match the localized heading targets.

What happens if target languages are unclear?

The skill checks repository conventions first. If the languages remain unclear, it asks the user once.

Is this for full application localization?

No. It is focused on README and Markdown documentation localization workflows.

Developer Details

Author

xixu-me

License

MIT

Skillstore revision

Version notice

The author did not declare a version.

Repository

https://github.com/xixu-me/skills/tree/main/skills/readme-i18n/

Ref

64ca8af0f54a325752f08bd54e52151061ea659a

Maintenance freshness

7/20/2026

Usage

10 downloads · 89 views

File structure

📁 references/

📄 language-selector-reference.md

📄 preservation-checklist.md

📄 SKILL.md