Install
$ agentstack add skill-squadcodercom-squadcoder-hebrew-ml-datasets-navigator ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Hebrew ML Datasets Navigator
Problem
The Israeli ML community punches above its weight, but the datasets and models are scattered. ivrit.ai publishes world-class Hebrew speech corpora on one HuggingFace org, Dicta publishes Hebrew LLMs and BERT variants on another, the Israeli National NLP Program maintains benchmarks under HebArabNlpProject, and classic resources like AlephBERT live elsewhere. Licenses vary from fully commercial-friendly to research-only. Hebrew register coverage varies dramatically: some corpora are all modern standard, others are half religious texts, others are spoken colloquial. A researcher trying to pick the right combination for "fine-tune a Hebrew sentiment classifier on customer support chat for a commercial product" has to hunt across five orgs and read every dataset card to understand what they can actually use.
Instructions
Step 1: Identify the task
Different Hebrew ML tasks need different datasets. Match your task to a dataset family before searching.
| Task | Primary data type | Dataset families to check first | |------|-------------------|--------------------------------| | Speech-to-text (Hebrew ASR) | Audio + transcripts | ivrit.ai (crowd-transcribe, crowd-recital, audio-v2) | | Text-to-speech (Hebrew TTS) | Text + studio audio | Public-domain audio with permissive licenses (limited; often requires custom recording) | | Hebrew LLM pre-training | Large Hebrew text corpus | Dicta's corpora, allenai/MADLAD-400 Hebrew subset, oscar-corpus/OSCAR-2301 Hebrew, uonlp/CulturaX Hebrew slice, HuggingFaceFW/fineweb-2 heb_Hebr filter, mC4 (Hebrew quality is weak), Hebrew Wikipedia, Knesset Plenums | | Hebrew LLM instruction tuning | Prompt-response pairs in Hebrew | Dicta instruction datasets, translated Alpaca-style datasets, custom | | Reading comprehension / QA | Text + Q&A pairs | HeQ (Etelis/HeQ_v1 HF mirror, canonical at github.com/NNLP-IL/Hebrew-Question-Answering-Dataset); omrikeren/ParaShoot (~3K few-shot QA examples) | | Sentiment classification | Hebrew text + labels | HebrewSentiment (HebArabNlpProject/HebrewSentiment) | | Natural language inference | Hebrew premise-hypothesis pairs | HebNLI (HebArabNlpProject/HebNLI) | | Named entity recognition | Hebrew text + entity tags | Dicta NER datasets, historical NNLP-IL releases | | Morphological analysis | Hebrew text + morph tags | Dicta morph datasets | | Diacritization (nikud) | Unvocalized + vocalized Hebrew | Dicta nikud datasets | | Paraphrase detection | Hebrew text pairs | NNLP-IL Hebrew paraphrase dataset (9,750 pairs) | | Summarization | Hebrew article + summary | biunlp/HeSum (10K article-summary pairs from Hebrew news, BIU NLP), HebArabNlpProject/HebSummaries | | General knowledge benchmarking | MCQ + answers | HEBREW-MMLU (Hebrew-translated MMLU subset; verify the active HF mirror, multiple community translations exist) | | Hebrew-English translation | Parallel corpora | NeuLabs-TedTalks, OPUS Hebrew subsets | | Yiddish ASR | Yiddish audio + transcripts | ivrit.ai Yiddish models (yi-whisper) and crowd datasets | | Yiddish text | Yiddish corpora | ivrit.ai crowd-whatsapp-yi, crowd-recital-yi |
Step 2: Key organizations and what they publish
Bookmark and subscribe to updates from these organizations. They are the authoritative sources for Hebrew ML.
ivrit.ai (huggingface.co/ivrit-ai)
Non-profit focused on Hebrew speech resources. As of 2025-2026 they host the world's largest public Hebrew audio corpus (22,000+ hours) under permissive licenses that explicitly allow commercial training.
Key artifacts:
ivrit-ai/crowd-transcribe-v5, latest crowd-sourced Hebrew ASR datasetivrit-ai/crowd-recital, Hebrew audio with careful recitalivrit-ai/audio-v2andaudio-v2-opus, bulk Hebrew audio corpusivrit-ai/whisper-large-v3, Hebrew-tuned Whisper ASR (full precision)ivrit-ai/whisper-large-v3-ct2, CTranslate2-optimized for fast inferenceivrit-ai/whisper-large-v3-turbo-ct2, turbo variant, fastestivrit-ai/whisper-large-v3-ggml, GGML-quantized for CPU inferenceivrit-ai/pyannote-speaker-diarization-3.1, Hebrew-tuned speaker diarizationivrit-ai/yi-whisper-large-v3, Yiddish ASR- Knesset Plenums dataset , Hebrew parliamentary speeches (large-scale)
License posture: permissive, commercial use explicitly allowed. Always check the specific dataset card for attribution requirements.
Dicta: The Israel Center for Text Analysis (huggingface.co/dicta-il)
The leading Hebrew LLM and BERT organization in Israel. Publishes both base and instruction-tuned models plus BERT variants for downstream tasks.
Key artifacts (verified on huggingface.co/dicta-il):
dicta-il/DictaLM-3.0-24B-Base, flagship Hebrew base LLM (24B, Mistral-adapted)dicta-il/DictaLM-3.0-24B-Thinking, reasoning-tuned 24B variantdicta-il/DictaLM-3.0-Nemotron-12B-Instruct, instruction-tuned mid-size (12B, Nemotron base)dicta-il/DictaLM-3.0-1.7B-Thinking-GGUF, small reasoning model, runnable on consumer hardware- Quantized variants for production:
*-FP8,*-W4A16,*-GGUF(e.g.DictaLM-3.0-Nemotron-12B-Instruct-FP8,DictaLM-3.0-24B-Thinking-GGUF) dicta-il/dictalm2.0-instruct, previous generation, 7B Mistral-7B-based, instruct fine-tuned (Zephyr recipe). Alsodictalm2.0-instruct-GGUF,-AWQ,-GPTQdicta-il/dictabert, baseline Hebrew BERT (fill-mask)dicta-il/dictabert-seg, Hebrew word segmentationdicta-il/dictabert-morph, Hebrew morphological analysisdicta-il/dictabert-heq, fine-tuned for Hebrew reading comprehensiondicta-il/dictabert-sentiment, Hebrew sentiment classificationdicta-il/neodictabert-bilingual-embed, Hebrew-English sentence embeddings
License posture: check each model card individually. Many permit commercial use but with attribution. DictaLM 3.0 sizes derive from different base models (Mistral for the 24B, NVIDIA Nemotron for the 12B, smaller variants vary) which inherit their upstream licenses.
Israeli National NLP Program (huggingface.co/HebArabNlpProject)
National initiative for Hebrew and Arabic NLP infrastructure, sponsored by DDR&D IMOD and supported by Dicta and Webiks.
Key artifacts:
HebArabNlpProject/HebrewSentiment, labeled Hebrew sentiment samples across train/validation/test splits; check the dataset card for current license and exact sample counts before commercial useHebArabNlpProject/HebNLI, Hebrew natural language inference- Paraphrase datasets, NER datasets, and other Hebrew benchmarks
License posture: generally permissive with CC-BY-4.0 or similar. Most are commercial-friendly with attribution.
NNLP-IL on GitHub (github.com/NNLP-IL)
Resource curation and benchmark dataset hosting.
Key repositories:
NNLP-IL/Hebrew-Resources, comprehensive list of Hebrew NLP datasets, models, toolsNNLP-IL/Hebrew-Question-Answering-Dataset, HeQ source repoNNLP-IL/HebNLI, HebNLI source repoNNLP-IL/NNLP-IL, program meta-repository
Multilingual web-scale corpora with Hebrew slices
Use these for LLM pre-training when you need scale that no Hebrew-only corpus can provide. Always filter to the Hebrew-script subset and re-deduplicate against your domain data.
uonlp/CulturaX, 6.3T tokens across 167 languages, combining mC4 v3.1.0 with OSCAR releases through 2023-01. Heavy cleaning and deduplication. Pull the Hebrew subset by language code. Apache 2.0 (terms tied to the underlying mC4/OSCAR licenses; check before commercial training).HuggingFaceFW/fineweb-2, ~20TB across 1,868 language-script pairs. Hebrew available asheb_Hebr. Higher-quality filtering than CulturaX. Sourced from CommonCrawl 2013 to April 2024.allenai/MADLAD-400, document-level multilingual corpus across 419 languages. Two variants: noisy (LangID only) and clean (filtered). Hebrew is included; pull by language code.oscar-corpus/OSCAR-2301, CommonCrawl-derived multilingual corpus, Hebrew slice available. NoteOSCAR-2301is gated behind a HuggingFace agreement; request access on the dataset page before using.mC4(Hebrew slice) , not deprecated, but the Hebrew partition has been criticized for noisier text and weaker filtering than newer corpora. Prefer FineWeb-2 or CulturaX where you can.
Always re-tokenize and re-deduplicate when combining corpora; CulturaX already incorporates mC4 + OSCAR through 2023, so layering them on top creates substantial duplication.
Step 3: License compatibility by use case
Pick the most-permissive license that meets your commercial needs.
| Your product | Licenses you can use | Avoid | |--------------|----------------------|-------| | Commercial SaaS / product | CC-BY-4.0, MIT, Apache 2.0, ivrit.ai permissive license, Dicta commercial-friendly | CC-BY-NC, GPL (unless your product is GPL), any "research only" | | Research publication | Any license that permits distribution for research (most) | Datasets under NDA or closed-source | | Internal prototype (non-distributed) | Very permissive, research-allowed covers most needs | Check carefully if prototype becomes a product | | Government / defense | Depends on contract terms; may require sovereign-safe data | Data with uncertain provenance or scraped PII |
Always read the specific dataset card. Licenses change. HuggingFace dataset cards are the authoritative source for current licensing.
Step 4: Hebrew register and demographic coverage
A "Hebrew dataset" is not homogeneous. Before training on it, understand what kind of Hebrew is represented.
| Register | Typical sources | When it matters | |----------|-----------------|-----------------| | Modern standard written | Wikipedia, news sites, Geektime | General-purpose LLMs, search, summarization | | Spoken / colloquial | Podcasts, YouTube, WhatsApp corpora | Conversational AI, voice interfaces, customer support | | Academic / formal | Dicta academic corpora, legal texts | Legal, scientific, government applications | | Religious / classical | Tanakh, Talmud, rabbinic texts | Religious tools, historical text processing | | Knesset plenary speech | Parliamentary records (via ivrit.ai) | Political NLP, civic tech, sentiment on public discourse | | Mixed Hebrew-English | Tech discussions, code-switching corpora | Startup-facing products, developer tools |
A customer-support chatbot trained only on Wikipedia will feel robotic. A religious-text model trained only on spoken podcasts will miss the entire target domain. Match register to use case.
Step 5: Pair datasets with models
For many tasks, the best approach is to use a published model as a starting point and fine-tune on your task-specific data. Model-dataset pairings that work well:
| Task | Starting model | Fine-tune on | Notes | |------|----------------|--------------|-------| | Sentiment | dicta-il/dictabert | HebArabNlpProject/HebrewSentiment | Dicta published dictabert-sentiment using exactly this recipe | | QA / reading comprehension | dicta-il/dictabert | pig4431/HeQ_v1 | Dicta published dictabert-heq using exactly this recipe | | Hebrew ASR | ivrit-ai/whisper-large-v3 | Your domain-specific audio | Use the turbo-ct2 variant in production for latency | | Yiddish ASR | ivrit-ai/yi-whisper-large-v3 | Your Yiddish audio | Tight niche; limited data | | Hebrew LLM instruction-following | dicta-il/DictaLM-3.0-Nemotron-12B-Instruct | Your instruction pairs | Use LoRA to save compute | | Hebrew sentence embeddings | dicta-il/neodictabert-bilingual-embed | Your pairs | Strong Hebrew-English bilingual baseline |
Step 6: Verify before training
Before committing compute to fine-tuning:
- Confirm the dataset exists at the HuggingFace ID you are using
- Read the dataset card fully (especially license, limitations, known biases)
- Check the sample count and splits; verify the test split is held out
- For audio datasets, listen to a few samples and verify quality
- For text datasets, read a few samples and verify the register matches your target
- Check the license compatibility for your specific commercial use
- Identify attribution requirements and plan how to comply
Step 7: Missing benchmarks for Hebrew
The Hebrew NLP ecosystem has gaps. Note that the DictaLM 3.0 release (Feb 2026) shipped its own benchmark suite covering Translation, Summarization, Winograd-style schemas, Israeli Trivia, and Hebrew Diacritization, narrowing the gap for those tasks. The list below is what is still missing as of May 2026: if your task is in this list, expect to either build evaluation data yourself or pair the closest existing benchmark with domain-specific human evaluation.
- Hebrew safety / red-team evals , no public Hebrew counterpart to ToxicChat, HarmBench. Build internal red-team prompts.
- Hebrew code generation , no Hebrew-language docstring or comment benchmark. Use English HumanEval/MBPP and accept the language mismatch.
- Hebrew long-context evals , no Hebrew Needle-in-a-Haystack or LongBench. Construct internally from Hebrew Wikipedia or Knesset transcripts.
- Hebrew tool-use / function-calling , no public Hebrew benchmark. Translate BFCL prompts to Hebrew if needed.
- Hebrew preference / RLHF data , scarce. Most Hebrew-aligned preference signal is private (Dicta, AI21, Hebrew-Mistral teams).
- Spoken Hebrew dialogue evals , ivrit.ai covers ASR but there is no public dialogue-quality benchmark. Build internal eval from real conversations.
- Hebrew multimodal (vision-language) , almost nothing public. Document understanding for Hebrew documents is largely covered only by commercial OCR + translation pipelines.
Known to exist but limited:
- HEBREW-MMLU , Hebrew-translated MMLU referenced by the Open Hebrew LLM Leaderboard ecosystem; multiple community translations exist with different qualities. Verify the active mirror before publishing comparable numbers.
openai/MMMLUcovers 14 languages but Hebrew is not in that official set. - Hebrew Winograd , community port of Winograd Schema Challenge, fewer than 300 items. High variance in single-run evals.
Step 8: Academic Hebrew NLP resources
Beyond ivrit.ai, Dicta, and the Israeli National NLP Program, several university labs release Hebrew NLP work that is worth tracking:
- BIU NLP Lab (Bar-Ilan University) , group behind HeSum (
biunlp/HeSum), original AlephBERT, and many Hebrew tagging benchmarks. Papers and resources atnlp.biu.ac.il. - Open University of Israel , Hebrew corpora and historical text resources (e.g. Knesset corpora prior to ivrit.ai's release).
- Technion / NLPH Lab , Hebrew NLP papers, Hebrew tokenization and morphology research.
- Hebrew University of Jerusalem (HUJI) , Open University collaborations on Hebrew syntax, morphology, and historical Hebrew. The original Winograd-HE port (vshwartz) traces back here.
- Reichman University / IDC NLP , occasional Hebrew benchmark releases tied to industry collaborations.
Tracking strategy: subscribe to the NNLP-IL/Hebrew-Resources repo for community curation; for primary releases follow the labs' own pages and the authors on Hugging Face.
Examples
Example 1: Training a Hebrew customer support sentiment model
User says: "We need to classify sentiment in Hebrew customer support messages for a commercial SaaS product."
Actions:
- Task: sentiment classification on conversational Hebrew
- Check
HebArabNlpProject/HebrewSentiment, Hebrew sentiment samples across train/validation/test, includes some spoken register. Verify the current license posture on the dataset card before relying on it for commercial use. - Check
dicta-il/dictabert-sentimentas a ready baseline before fine-tuning anything - Start with the Dicta sentiment model and evaluate on a held-out set of real customer support chats
- If the baseline is insufficient, fine-tune
dicta-il/dictaberton
…
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: squadcodercom
- Source: squadcodercom/squadcoder
- License: MIT
- Homepage: https://squadcoder.com
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.