localise — Claude Code skill: what it does, how to install
Adapts finished English deliverables into Romanian, French, Spanish, or Russian with glossary checks, back-translation QA, and deck reviews.
npx skills add gasserane/personal-skills --skill localise -a claude-codeWhat localise does
This skill converts finished English reference files into derived deliverables for four target languages: Romanian, French, Spanish, and Russian. It runs in four modes: translating a source file, building a parallel companion document, auditing an existing draft, or processing exported slide decks where text sits rasterized inside .docx images. For image decks, the helper script scripts/extract_deck.py parses the layout before generating anchored comments and a corrections sheet.
The pipeline checks domain glossaries, flags sensitive wording, and runs back-translation to spot meaning drift. Romanian has the most vetted glossary, while French, Spanish, and Russian operate as working draft lists refined during execution. Documents export to Word format through ane_package.reporting.word_export alongside a structured quality assurance memo.
Sensitive Russian vocabulary around reproductive rights or gender identity carries strict legal exposure. Distributing Russian outputs inside restricted jurisdictions without dedicated legal and safeguarding sign-off will create direct compliance liabilities. The tool produces review drafts and cannot replace native speaker verification.
What it helps with
- translate an English source into target languages with controlled terminology
- spot semantic drift using systematic back-translation passes
- audit target-language drafts step by step without silent rewriting
- extract and review slide text embedded inside Word export images
Example prompts for the agent
- Localise report.md into French with a terminology compliance note
- Review my draft translation in draft_ru.docx against source.md
- Extract deck_export.docx using scripts/extract_deck.py to check slide image strings
How to install localise
1Skills CLI (Vercel)
npx skills add gasserane/personal-skills --skill localise -a claude-code2Manually: put the files in place
~/.claude/skills/localise/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/localise/
1Skills CLI (Vercel)
npx skills add gasserane/personal-skills --skill localise -a codex2Manually: put the files in place
.agents/skills/localise/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add gasserane/personal-skills --skill localise -a cursor2Manually: put the files in place
.cursor/skills/localise/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install gasserane/personal-skills localise2Manually: put the files in place
.github/skills/localise/SKILL.md1Skills CLI (Vercel)
npx skills add gasserane/personal-skills --skill localise -a gemini-cli2Platform CLI
gemini skills install https://github.com/gasserane/personal-skills --path skills/localiseManually: put the files in place
.devin/skills/localise/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add gasserane/personal-skills --skill localise -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about localise
How to install localise in Claude Code?
Run npx skills add gasserane/personal-skills --skill localise -a claude-code. The skill file lands in ~/.claude/skills/localise/SKILL.md.
Does localise generate content without an English source?
No. It treats English as canonical source text and only adapts existing documents or reviews drafts.
What happens when reviewing image-based slide exports?
Mode 4 checks rasterized slide decks exported to .docx via python scripts/extract_deck.py extract DECK.docx --out-dir slides/. It leaves the original untouched, adding anchored Word comments and an external correction sheet.
