Bilingual Meeting Minutes in One Pass
Generate Arabic and English meeting records simultaneously without double work
Your meetings mix Arabic and English but your minutes need to serve Arabic-speaking stakeholders and English-speaking teams separately. Writing two versions takes double the time and creates inconsistencies between what each language version says.
That is the gap this drop closes. It is a operations 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
Operations managers and executive assistants in UAE businesses that work in both Arabic and English
How it works
The skill file does five things, in this order.
1. Feed raw notes in the language spoken. Copy your rough notes exactly as captured, whether Arabic, English, or mixed code-switching.
2. Request parallel structure output. Ask Claude to produce matching sections in both languages with identical headings and numbering.
3. Specify formal Arabic register. State that Arabic output should use Modern Standard Arabic suitable for corporate governance, not casual dialect.
4. Declare terminology preferences. Provide any specific Arabic terms your organization uses for recurring concepts like quarterly review or project milestone.
5. Review for cultural appropriateness. Check that action assignments and deadlines read naturally in both languages and respect how each culture phrases commitments.
What comes back
Two formatted versions ready to distribute, one to Arabic stakeholders and one to English teams, with guaranteed content parity
The mistake to avoid
Arabic corporate writing tends toward longer, more formal phrases than English equivalents. If your Arabic version runs much longer, ask Claude to tighten it to match English brevity while keeping formality intact.
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 drafting bilingual meeting minutes for a UAE business context.
Meeting details:
Date: {date}
Attendees: {names_and_roles}
Raw notes: {mixed_language_notes}
Produce two parallel versions with identical structure:
1. English version using concise business language
2. Arabic version in Modern Standard Arabic appropriate for corporate governance
For both versions include:
- Executive summary (2-3 sentences)
- Key decisions made (numbered list)
- Action items with owner names and due dates (table format)
- Open questions requiring follow-up
Terminology requirements:
Use these specific Arabic terms: {custom_terminology_if_any}
Format each version with:
- Matching section headings in both languages
- Identical numbering systems
- Same level of detail and specificity
- Consistent date formats (English: DD/MM/YYYY, Arabic: ٢٠٢٤/٠٣/١٥)
Ensure the Arabic version maintains professional formality while matching the brevity of the English version where culturally appropriate.