The Bilingual Finance Memo
Write the same board memo in Arabic and English without losing precision
You write a clear financial summary in English, then the Arabic version sounds wooden or vague. Numbers, technical terms and causality chains break down in direct translation.
That is the gap this drop closes. It is a finance & admin skill built for Claude, and it takes about ten minutes to set up the first time. After that it runs in under a minute.
Who should use it
Finance managers in UAE companies with Arabic-speaking boards or stakeholders
How it works
The skill file does five things, in this order.
1. Write the English first with Arabic in mind. Keep sentence structure simple and avoid idioms that have no Arabic equivalent.
2. Mark the technical terms that stay English. EBITDA, KPIs and brand names often read better untranslated, even in Arabic text.
3. Ask Claude for Arabic that preserves tone. Request formal but readable Arabic, not a word-for-word conversion.
4. Check that cause-effect flows match. The same financial logic must be clear in both versions, not just the same words.
5. Test the Arabic on a non-finance reader. If they understand the English but not the Arabic, the translation failed.
What comes back
A financial memo that reads naturally in both languages and carries the same meaning to different audiences
The mistake to avoid
Do not translate the English memo after you finish it. Write both versions in parallel, adjusting the English when Arabic demands clearer phrasing. This produces two originals, not an original and a copy.
Running it
Save this as SKILL.md inside a folder named after the skill, then drop the folder into your Claude Code skills directory or upload it to a Claude Project. Claude reads the frontmatter to decide when the skill applies, so keep the description line intact. For a one-off run, paste the prompt block directly.
Where this fits
On its own, one skill saves an hour a week. The compounding happens when three or four of them run in sequence on the same input, the same transcript that produces a scope of work also produces the follow-up email and the project brief. That is the point at which it stops being a prompt and starts being an internal tool. If you want that wired into the systems your team already uses, that is the work 67 Digital does.
In the file
You are helping me write a financial board memo in both English and Arabic for a UAE company.
Context:
- Company: {company_name}
- Reporting period: {period}
- Key financial movement: {main_financial_point}
- Audience: {board_composition}
First, write a concise English summary (150 words maximum) that explains:
1. What changed financially
2. Why it changed
3. What this means going forward
Use simple sentence structure. Avoid idioms. Keep technical terms in English where standard (EBITDA, CAPEX, etc.).
Then provide an Arabic version that:
- Preserves the same logical flow and tone
- Keeps technical terms in English where they are clearer
- Uses formal but accessible Modern Standard Arabic
- Matches the meaning, not the word order, of the English
Finally, list any terms where you chose to keep English in the Arabic text and briefly explain why.
Format:
[English version]
[Arabic version]
[Terminology notes]