multilingual

Translate Hyper-Extract YAML templates into bilingual language maps for Chinese, English, and Japanese.

3.3k|386|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/yifanfeng97/Hyper-Extract --skill multilingual
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multilingual
Source: https://github.com/yifanfeng97/Hyper-Extract/tree/main/hyperextract-skills/multilingual
Command: npx skills add https://github.com/yifanfeng97/Hyper-Extract --skill multilingual

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert Hyper-Extract YAML templates into multi-language support to enable bilingual configurations across teams and products.

Core Features & Use Cases

  • Supports translating core fields: description, output.description, fields[].description, guideline.target, and guideline.rules.
  • Preserves non-translatable identifiers such as name, type, tags, and field names to maintain consistency across languages.
  • Provides a structured workflow to generate language maps (e.g., zh/en) and apply translations to existing templates for localization, documentation, and UX improvements.
  • Use Case: A team wants to publish a bilingual knowledge template that can be consumed by both Chinese and English readers without editing the template manually.

Quick Start

Run the multilingual converter on a YAML template to produce a bilingual mapping for zh and en.

Frequently Asked Questions about multilingual

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

FAQPage Schema
How do I add multilingual translation support to a YAML template?

To add multilingual translation support to a YAML template, run the converter to generate a bilingual mapping for languages like zh and en. It translates core fields while preserving non-translatable identifiers to maintain consistency.

What fields are preserved when localizing YAML templates for different languages?

When localizing YAML templates, non-translatable identifiers such as name, type, tags, and field names are preserved. The translation schema only targets descriptions, guidelines, and output descriptions to maintain structural consistency.

Can I generate bilingual configurations for Chinese and English readers automatically?

Yes, you can generate bilingual configurations for Chinese and English readers automatically. The converter applies a translation schema to existing templates, outputting a ready-to-use language map without manual editing.

Does the YAML translation process support Japanese alongside Chinese and English?

The YAML translation process supports Japanese alongside Chinese and English. It applies a structured workflow to translate descriptions, fields, and guidelines across all three languages within the template.

What is the best way to maintain consistency across multilingual YAML configurations?

The best way to maintain consistency across multilingual YAML configurations is to enforce a translation schema that preserves non-translatable fields and maintains language keys. This ensures identifiers stay uniform across all language outputs.