en-manual-wash

Replaces mistranslated terms in English docx manuals with standard OpenStack terminology.

Updated May 10, 2026
One-click install
npx skills add https://github.com/dadafinger/dadafinger-skills --skill en-manual-wash-dadafinger
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: en-manual-wash
Source: https://github.com/dadafinger/dadafinger-skills/tree/main/en-manual-wash
Command: npx skills add https://github.com/dadafinger/dadafinger-skills --skill en-manual-wash-dadafinger

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Machine-translated English manuals (e.g., from Google Translate) contain inconsistent or incorrect terminology that deviates from OpenStack standards. This Skill automates the review and replacement of those terms in .docx manuals, producing a cleaned document without touching the original file. ## Core Features & Use Cases - Terminology Replacement: Applies a curated REPLACEMENTS dictionary to swap mistranslated phrases (e.g., "Instance Type" → "Flavor", "Dynamic IP" → "Floating IP") with OpenStack standard terms. - Safe docx Processing: Unpacks the docx, edits only text inside <w:t> XML tags, and repacks it, preserving document structure and formatting. - Replacement Report: Outputs a per-term count of all replacements made during the wash. - Use Case: You receive a Google-translated English product manual for an OpenStack-based cloud platform. Run the wash script to generate a *_washed.docx aligned with OpenStack glossary terminology, plus a report of every correction. ## Quick Start Ask the AI to wash the attached English manual docx against OpenStack standard terminology and generate the cleaned _washed.docx file with a replacement report.

Frequently Asked Questions about en-manual-wash

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

FAQPage Schema
How do I fix Google Translate terminology in an English docx manual?▼

Run the wash script with the docx path: python scripts/wash.py --file "manual.docx". It unpacks the document, replaces mistranslated terms with OpenStack standard terminology, and saves a new file ending in _washed.docx alongside the original.

What tool standardizes OpenStack terms in translated documentation?▼

This Skill uses a Python script with a curated REPLACEMENTS dictionary mapping common machine-translation errors (like "Instance Type" or "Dynamic IP") to OpenStack standard terms ("Flavor", "Floating IP"). The dictionary is maintained in scripts/wash.py.

Does the washing process overwrite the original docx file?▼

No, the original file is never modified. The script always writes output to a new file with the _washed suffix in the same folder, and only text inside w:t XML tags is changed, leaving document structure intact.

How do I add new replacement terms to the dictionary?▼

Add new (old, new) tuples to the REPLACEMENTS list in scripts/wash.py. Place longer, more specific phrases before shorter ones so they match first. The list is kept in sync with the openstack-glossary-en translation dictionary.

Why are some terms not replaced in my manual?▼

Replacement only occurs when the exact string in the REPLACEMENTS list appears inside a w:t text node. Case variants or phrasing not present in the dictionary are skipped, so new translation variants must be added to the list manually.