translate-skill

Name: translate-skill
Availability: InStock
Author: vinvcn

Translate technical documentation into Simplified Chinese while preserving code blocks and identifiers.

23|6|Updated May 9, 2026

Search Tags:#workflow #documentation #localization #translation #sync #i18n

Ready to run

npx skills add https://github.com/vinvcn/addyosmani-agent-skills-zh --skill translate-skill

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: translate-skill
Source: https://github.com/vinvcn/addyosmani-agent-skills-zh/tree/main/.skills/translate-skill
Command: npx skills add https://github.com/vinvcn/addyosmani-agent-skills-zh --skill translate-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured workflow for translating and refreshing technical documentation and agent-facing content while ensuring that behavior-critical identifiers remain intact.

Core Features & Use Cases

Content Localization: Translates natural-language prose into natural Simplified Chinese while protecting code, paths, and commands.
Repository Refresh: Provides a systematic approach to syncing upstream changes without overwriting localized repository metadata or installation instructions.
Use Case: When updating a localized repository from an upstream source, use this skill to identify changed files, translate new prose, and verify that all installation commands point to the correct localized repository path.

Quick Start

Use the translate-skill to refresh the current repository content by identifying new prose and applying the standard translation workflow.

Frequently Asked Questions about translate-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I translate technical documentation into Simplified Chinese without breaking code blocks?▼

To translate technical documentation into Simplified Chinese safely, you need a workflow that preserves behavior-critical identifiers. This skill localizes natural-language prose while ensuring code blocks, CLI commands, and frontmatter keys remain unchanged.

What is the best way to sync upstream documentation changes to a localized repository?▼

Syncing upstream documentation changes to a localized repository requires systematically identifying changed files and translating new prose. This skill refreshes content without overwriting localized repository metadata or specific installation instructions.

How does documentation localization handle frontmatter keys and CLI commands?▼

Documentation localization handles frontmatter keys and CLI commands by treating them as protected elements. The localization process strictly targets natural-language prose, ensuring all frontmatter keys and command-line instructions remain unchanged.

Can I use this workflow to update installation paths for a localized repository?▼

Yes, you can use this workflow to update installation paths for a localized repository. It verifies that all installation commands point to the correct localized repository path during the upstream content refresh process.

What should I do if an upstream repository refresh overwrites my localized metadata?▼

If an upstream repository refresh overwrites localized metadata, you need a systematic sync workflow. This skill prevents overwriting by preserving repository-specific installation paths and localized metadata while pulling upstream changes.