Turn Arabic Shift Handovers into Searchable Logs

Shift handovers happen in Arabic, verbally or on WhatsApp. Critical details about equipment issues, customer problems, and workarounds disappear when the next shift starts.

That is the gap this drop closes. It is a operations skill built for Kimi, 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 running shifts with Arabic-speaking teams

How it works

The skill file does five things, in this order.

1. Record the Arabic handover conversation. Use your phone to capture the 5-10 minute conversation between outgoing and incoming shift leads.

2. Get a bilingual transcript. Upload to Kimi and ask for Arabic transcription with English translation in parallel columns.

3. Extract recurring issues as structured data. Ask Kimi to identify equipment names, problem types, and temporary solutions mentioned across multiple handovers.

4. Build a searchable issue log. Paste outputs into a shared sheet where supervisors can search by machine name or problem in either language.

5. Train shift leads to record consistently. Show them the output once, then make recording the last task before they leave.

What comes back

A living database of operational issues that grows with every shift, searchable in Arabic and English

The mistake to avoid

Arabic technical terms often mix with English brand names and loan words. Tell Kimi to preserve original equipment names exactly as spoken, even if they are hybrid phrases. This keeps your log consistent with how your team actually talks.

Running it

Paste the prompt block into a new Kimi chat and attach your files in the same message. Kimi's long context means you should upload everything at once rather than in batches, splitting the input is what causes it to lose cross-references between documents.

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

I have recorded a shift handover conversation in Arabic. Please provide:

1. Full transcription in Arabic
2. English translation alongside the Arabic text in two-column format
3. A structured extraction table with these columns:
   - Equipment/Asset name (as spoken, preserve any English or hybrid terms)
   - Issue type (malfunction, shortage, customer complaint, etc.)
   - Temporary solution mentioned
   - Followup required (yes/no)
   - Timestamp or shift reference

4. A brief summary in both Arabic and English highlighting:
   - Any recurring problems mentioned in this or compared to previous handovers
   - Items that need management escalation
   - Knowledge that should become permanent procedure

Preserve technical terminology exactly as spoken. If the speaker says "{equipment_name}" in English within Arabic sentences, keep it in English. If they use a hybrid term, keep the hybrid.

Format the extraction table so I can copy it directly into Google Sheets.

If you identify patterns across multiple handovers I upload, flag them under "Recurring Issues" with frequency count.