Menu
Translate Hebrew transaction descriptions to English for better readability and categorization. Use when user asks to translate, transliterate, or convert Hebrew merchant names to English in KolShek.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Deep-dive financial analysis — maps income and expenses, identifies savings opportunities, and creates a phased action plan with budget targets. Use when: analyze finances, financial checkup, deep dive, find savings, audit expenses, map income, understand where money goes, check financial health.
Analyze transactions and create auto-categorization rules for expenses and income. Use when user asks to categorize, label, classify, or tag transactions, set up spending categories, manage category rules, rename or merge categories, or reassign transactions in KolShek.
Create custom dashboard pages — compose widgets (charts, metrics, tables, progress bars) with composable query primitives to build any financial view. Use when: custom dashboard, create page, build view, budget tracker, spending analysis, merchant breakdown, savings tracker, custom report, financial dashboard, add page, new view, budget view, envelope budgeting.
Set up KolShek from scratch — connect bank accounts and credit cards, fetch transactions, translate Hebrew descriptions, and categorize spending. Use when user wants to initialize, set up, onboard, or get started with KolShek.
Monthly financial review — compares spending to previous month, checks budget targets, detects anomalies, and produces a progress report card. Use when: monthly review, month comparison, budget check, spending review, report card, how they did this month, progress check, monthly checkup.
Import transactions from any bank's CSV export (Chase, Bank of America, Wells Fargo, Amex, Capital One, etc.) by auto-mapping columns to KolShek format. Use when: upload CSV, import CSV, convert CSV, Chase CSV, bank CSV, foreign bank CSV, map CSV columns, reformat CSV for import.
Based on SOC occupation classification
| name | translate |
| description | Translate Hebrew transaction descriptions to English for better readability and categorization. Use when user asks to translate, transliterate, or convert Hebrew merchant names to English in KolShek. |
| compatibility | Requires KolShek CLI (kolshek) installed and configured with at least one provider. |
| metadata | {"author":"kolshek","version":"0.4.8"} |
| allowed-tools | Bash Read AskUserQuestion |
You are helping the user translate their Hebrew transaction descriptions to English.
Read references/cli-reference.md for the complete command reference, DB schema, exit codes, and SQL patterns.
Run startup checks:
kolshek providers list --json — if empty, guide user to kolshek providers add.kolshek transactions list --limit 1 --json — if empty, offer to fetch.kolshek query "SELECT MAX(completed_at) as last_sync FROM sync_log WHERE status = 'success'" --json — if over 24h old, suggest kolshek fetch.Check if translations have been seeded already:
kolshek translate rule list --json
If no rules exist, seed the built-in merchant dictionary first:
kolshek translate seed --json
Report how many rules were seeded.
Get all unique descriptions that don't have a matching translation rule:
kolshek query "SELECT DISTINCT description FROM transactions WHERE description IS NOT NULL ORDER BY description" --json
Cross-reference with existing rules from kolshek translate rule list --json. Identify descriptions not yet covered by any rule.
For each untranslated description, generate an English translation (you can read Hebrew). Group them into a table:
Here are the translations I've prepared:
Hebrew English שופרסל דיל Shufersal Deal (supermarket) קפה גרג Cafe Greg העברה בביט Bit Transfer משכורת Salary ... ... Look good? You can suggest changes, remove entries, or approve.
Let the user review — they can approve all, request changes to specific ones, or skip entries.
For each approved translation:
kolshek translate rule add "<english>" --match "<hebrew>" --json
For bulk operations, you can also use:
kolshek translate rule import rules.json --json
Then apply all rules:
kolshek translate apply --json
Report how many transactions were translated.
Translated N transactions. You now have Z translation rules. Add more anytime with
kolshek translate rule add "<english>" --match "<hebrew>".