Hebrew Ocr Forms
Verified91/100Process and extract data from scanned Israeli government forms using OCR. Supports Tabu (land registry), Tax Authority forms, Bituach Leumi documents, and other official Israeli paperwork. Use when user asks to OCR Hebrew documents, extract data from Israeli forms, "lesarek tofes", parse Tabu extract, read scanned tax form, or process Israeli government documents. Includes Hebrew OCR configuration, field extraction patterns, and RTL text handling. Do NOT use for handwritten Hebrew recognition (requires specialized models) or non-Israeli form processing.
Trust score 91/100 (Verified) · 292+ installs · 2 GitHub contributors · MIT license
Israeli government forms still arrive in large volumes as scans and unstructured PDFs, with handwriting, stamps, and dense Hebrew text. Standard OCR tools struggle with Hebrew due to script direction, similar-looking characters, and low-quality scans. The result is hours of manual data entry and frequent errors.
skills-ilHow to use this skill
Not sure how? Read the guide- 1. Click "Download ZIP" to download the skill files.
- 2. Open Claude Desktop and go to Customize > Skills.
- 3. Click "+" and select "Upload a skill", then upload the ZIP file.
- 4. Start a new conversation. The skill will activate automatically when relevant.
Developers? Install via command line (CLI)
npx skills-il add skills-il/localization@v1.4.0-hebrew-ocr-forms --skill hebrew-ocr-forms -a claude-codeWhen to Apply
- Extracting data from scanned Israeli forms (Tabu extract, Tofes 106, ishur nikui)
- Batch-processing PDFs or images of Hebrew government documents, including multi-page PDFs
- Detecting TIN, Israeli ID (teudat zehut), or gush/chelka from printed text
- Choosing a Hebrew OCR engine (local Tesseract vs a cloud Vision API vs Claude Vision)
- Validating extracted fields (Israeli ID check digit, date format)
Try These Prompts
How do I scan an income tax form 106 and extract its data: salary, withheld tax, and deductions, into a JSON structure?
How do I parse a scanned Nesach Tabu into an Excel spreadsheet? I need one row per owner with their share, plus the mortgages, liens, and cautions.
How do I validate that a scanned government document (such as an ID card or business license) is authentic and that the extracted data is accurate?
Frequently Asked Questions
Changelog
Added Nesach Tabu to spreadsheet: one row per owner with share, and per mortgage, lien, order, and caution, ready for Excel.
Jul 6, 2026
Corrected the fabricated claim that AWS Textract supports Hebrew (it does not, Latin-script only), downgraded the overstated Azure Hebrew rating, added Google Cloud Vision's 'iw' language code for Hebrew, and bumped the Claude model id to opus-4-8.
Jun 16, 2026
Updated the Claude Vision model, wired the previously dead contrast-enhance flag, and added final-form letter, nikud, digit-order and multi-page PDF handling.
May 14, 2026
Related Skills
Author: skills-ilGenerate professional Hebrew documents (PDF, DOCX/Word, and PPTX) with correct right-to-left layout, mixed Hebrew-and-English bidi handling, and proper Hebrew typography. Use whenever the output is a Hebrew or mixed Hebrew/English Word document, Hebrew PDF, or Hebrew PowerPoint, including phrasings like "Hebrew Word document", "Word document in Hebrew", "מסמך Word בעברית", "create a .docx in Hebrew", "lehafik heshbonit", and "litstor hozeh", or Israeli templates such as Heshbonit Mas (tax invoice), Hozeh (contract), Hatza'at Mechir (proposal), or Protokol (meeting minutes). ALSO use this for the symptom where a Hebrew document looks correct on screen or in Claude but comes out scrambled, reversed, or broken after export to Word, with English words, numbers, or punctuation landing on the wrong side, phrased as "Hebrew text reversed in Word", "my Hebrew Word file is broken", "fix Hebrew formatting in Word", or "the docx came out messed up"; the fix is regenerating the .docx with paragraph-level RTL/bidi, NOT a web/CSS RTL change. Prefer this over the generic docx or pdf skills ONLY when the document is Hebrew or right-to-left, because those do not set RTL/bidi and produce scrambled Hebrew with English words and punctuation in the wrong place; for English-only documents use the generic skill. Covers reportlab, WeasyPrint, python-docx, and pptxgenjs. Do NOT use for OCR or reading existing documents (use hebrew-ocr-forms instead).
Author: skills-ilWrite and edit professional content in Hebrew including marketing copy, UX text, articles, emails, and social media posts. Use when user asks to write in Hebrew, "ktov b'ivrit", create Hebrew marketing content, edit Hebrew text, write Hebrew UX copy, or optimize Hebrew content for SEO. Covers grammar rules, register from formal to dugri, mixed Hebrew/English, gendered language, nikud and numerals, and Hebrew SEO best practices. Do NOT use for Hebrew NLP/ML tasks (use hebrew-nlp-toolkit) or translation (use a translation skill).
Author: skills-ilImplement right-to-left (RTL) layouts for Hebrew web applications. Use when user asks about RTL layout, Hebrew text direction, bidirectional (bidi) text, Hebrew CSS, "right to left", or needs to build a Hebrew web UI. Covers CSS logical properties, the :dir() pseudo-class, Tailwind RTL, React/Next.js RTL setup, icon mirroring, Hebrew typography, and font selection. Do NOT use for Arabic RTL (similar but different typography) unless user explicitly asks for shared RTL patterns, or for native mobile RTL (React Native I18nManager, SwiftUI, Android) which is out of scope.
Use at your own risk. Terms of Use · Security
Want to build your own skill? Try the Skill Creator · Submit a Skill