document-translation
Skill2 starsChanged 5 months agoNo licenceView on GitHub
Turn an approved English document or document set (Word, Excel, PowerPoint, PDF, or a mix) into format-identical, contextually accurate translated versions in one or more target languages. Built for the standard Cargill target set — Chinese (Simplified), Dutch, French, French-Canadian, German, Indonesian (Bahasa), Polish, Portuguese, Russian, Spanish, and Latin American Spanish — but handles any language the user names. Use this skill whenever the user asks to "translate this document," "create translated versions," "localize the interview guide," "produce the Chinese, German, or Spanish version," "we need this in 11 languages," "make language versions of the packet," or uploads an approved deliverable (interview guide, SME package, competency document, training material, policy, survey, scorecard) and asks for it in another language. Also trigger for translation QA requests — "check this translation," "back-translate this," "is this translation accurate" — and for setting up a reusable translation glossary or terminology list. The deliverable contract: one output file per language per source document, identical in format, layout, and branding to the English original, such that a native speaker reading the translated version comes away with the same understanding as an English reader of the original.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Boye-coder/skillstheir own version, first seen Mar 2, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Boye-coder/skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- coverage-auditSkill
- sme-validation-packageSkill
- structured-interview-generatorSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.