OpenParable
Skip to content
← Back to skills

Multilingual

Documents
multilingual

Multilingual is an Agent Skill for documents published in the yifanfeng97/Hyper-Extract repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Convert Hyper-Extract YAML templates to multi-language support. Use when user says: "add translation", "multilingual", "convert language", "support Chinese and English". Trigger: User wants to add Chinese/English/Japanese translation to their template. Skip: User wants to design a new template (use record-designer or graph-designer instead).

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/yifanfeng97/Hyper-Extract/blob/HEAD/hyperextract-skills/multilingual/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/multilingual, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Multilingual Converter

Translatable Fields

The following fields can be translated:

  • description
  • output.description
  • fields[].description
  • guideline.target
  • guideline.rules

Non-Translatable Fields

The following fields should NOT be translated:

  • name, type, tags
  • field names (name in fields)
  • identifiers
  • display

Conversion Modes

Mode 1: Single → Bilingual

# Before (single language)
language: zh
description: '财务报告摘要'

# After (bilingual)
language: [zh, en]  # YAML list format
description:
  zh: '财务报告摘要'
  en: 'Financial Report Summary'

Mode 2: Expand Existing Translation

# Before (has zh only)
description:
  zh: '财务报告摘要'

# After (add en)
description:
  zh: '财务报告摘要'
  en: 'Financial Report Summary'

Mode 3: Add New Language

# Before (zh + en)
# After (add ja)
description:
  zh: '财务报告摘要'
  en: 'Financial Report Summary'
  ja: '財務報告サマリー'

Translation Guidelines

Field Descriptions

OriginalEnglishNotes
公司名称Company nameDirect
营收金额Revenue amountDirect
关键词Keyword/TermChoose based on context

Target/Rules

target:
  zh: '你是一位财务分析师,请从财报中提取关键信息。'
  en: 'You are a financial analyst. Extract key information from financial reports.'

rules:
  zh:
    - '每个字段对应一个独立的信息项'
  en:
    - 'Each field corresponds to an independent information item'

Multi-language Consistency

When translating field values (like enum options), maintain language purity:

OriginalChinese TranslationEnglish Translation
类型:实体/抽象类型:实体/抽象Type: entity/abstract
重要性:高/中/低重要性:高/中/低Significance: high/medium/low

Do NOT translate inline: 类型:entity(实体) → wrong!

Translation Checklist

  • Preserve technical terms consistently
  • Maintain same meaning across languages
  • Keep field names in source language
  • Update language field to indicate multi-language (use list format)

Output Format

## Multilingual Conversion Result

language: [zh, en]  # YAML list format

# All translatable fields now have both zh and en

## Translation Mapping

| Field Path | Chinese | English |
|------------|---------|---------|
| description | ... | ... |
| output.description | ... | ... |
| fields[].description | ... | ... |
| guideline.target | ... | ... |
| guideline.rules | ... | ... |

Notes

  • Use professional domain terminology
  • Maintain consistent terminology across fields
  • Keep YAML structure clean and readable
  • Field names (name) should NOT be translated
  • Use YAML list format for language field: language: [zh, en]