by @skills-il
Write 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, formal vs informal register, gendered language handling, and Hebrew SEO best practices. Do NOT use for Hebrew NLP/ML tasks (use hebrew-nlp-toolkit) or translation (use a translation skill).
npx skills-il add skills-il/localization --skill hebrew-content-writer| Content Type | Register | Audience | Key Characteristics |
|---|---|---|---|
| Legal / Government | Formal (gvoha) | Officials, lawyers | Passive voice, complex sentences, traditional gendering |
| Business / Corporate | Business | Professionals | Clear, professional, moderate formality |
| Marketing / Ads | Business-Casual | General public | Persuasive, benefit-focused, concise |
| UX / Interface | Direct | End users | Imperative mood, ultra-short, action-oriented |
| Social Media | Informal | Young adults | Casual, slang-friendly, emoji-compatible |
| Blog / Article | Business | Readers | Informative, SEO-aware, structured |
Spelling Standard -- Use Ktiv Maleh (Full Spelling): Modern Hebrew content uses ktiv maleh (plene spelling) with vav and yod for vowels:
Smichut (Construct State) Rules:
Direct Object Marker (et):
Subject-Verb Agreement:
Option A -- Traditional (default for formal/legal): Use masculine plural for mixed groups. Standard in government, legal, academic writing.
Option B -- Slash Notation (for business/marketing):
משתמשים/ות יקרים/ות (dear users, m/f)Option C -- Gender-Neutral Rewording (recommended for UX/tech):
| Instead of | Use |
|---|---|
| המשתמש צריך ללחוץ (the user needs to click, m.) | יש ללחוץ על (click on) |
| אתה יכול לבחור (you can choose, m.) | ניתן לבחור (it is possible to choose) |
| הלקוחות שלנו מרוצים (our customers are satisfied, m.) | שביעות רצון הלקוחות שלנו (the satisfaction of our customers) |
Ask the user which approach they prefer if not specified.
| Mistake | Wrong | Correct | Rule |
|---|---|---|---|
| Smichut with ha- on first noun | הבית הספר | בית הספר | Only second noun gets ha- |
| Missing et | ראיתי הכלב | ראיתי את הכלב | Definite direct object needs et |
| Wrong gender agreement | הילדה הלך | הילדה הלכה | Verb must match subject gender |
| Mixed ktiv | תוכנה/תכנה in same text | Pick one consistently | Use ktiv maleh throughout |
| Incorrect vav ha-hipukh | ואז הוא הולך | ואז הוא הלך | Vav ha-hipukh is biblical, not modern |
| Colloquial in formal text | נגיד ש... | לדוגמה... | Match register to context |
Keyword Strategy:
On-Page SEO for Hebrew:
Content Structure:
User says: "Write a Hebrew marketing email for a SaaS product launch" Result: Write business-register Hebrew email with compelling subject line, benefit-focused body, clear CTA. Apply SEO principles if it will be a web version. Use gender-inclusive language.
User says: "Write Hebrew error messages for a login form" Result: Write short, clear, action-oriented Hebrew text in imperative mood. Use neutral/inclusive phrasing. Examples: "הסיסמה שגויה. יש לנסות שנית" (The password is incorrect. Please try again).
User says: "Write a Hebrew blog post about cloud security for Israeli businesses" Result: Research Hebrew keywords, write structured article with proper H2/H3 hierarchy, include meta description, use ktiv maleh throughout, business register.
User says: "Make this Hebrew text gender-inclusive" Result: Identify gendered forms, apply Option C rewording where possible, use slash notation where rewording is awkward, maintain readability and register.
references/hebrew-grammar-quick-ref.md — Concise Hebrew grammar reference covering all 7 binyanim (verb patterns) with usage guidance by register, ktiv maleh vs. ktiv chaser spelling examples, common smichut (construct state) forms, and four gender-inclusive writing patterns with before/after examples. Consult when writing or editing Hebrew content and need to verify grammar rules, choose the correct register, or apply gender-neutral phrasing.Cause: Inconsistent tone throughout the content Solution: Identify the target register at the start and apply it consistently. Common issue when multiple writers contribute or when translating from English.
Cause: Direct translation of English keywords to Hebrew Solution: Use Google Keyword Planner with Israel region. Hebrew search patterns differ from English -- Israelis may search differently than direct translations suggest.
Supported Agents
Trust Score
This skill can access environment variables which may contain secrets.
by @skills-il
Schedule meetings, deployments, and events respecting Shabbat, Israeli holidays (chagim), and Hebrew calendar constraints. Use when user asks to schedule around Shabbat, "zmanim", check Israeli holidays, plan around chagim, set Israeli business hours, or needs Hebrew calendar-aware scheduling logic. Includes halachic times (zmanim) via HebCal API, full Israeli holiday calendar, and Israeli business hour conventions. Do NOT use for religious halachic rulings (consult a rabbi) or diaspora 2-day holiday scheduling.
by @skills-il
Implement right-to-left (RTL) layouts for Hebrew web and mobile applications. Use when user asks about RTL layout, Hebrew text direction, bidirectional (bidi) text, Hebrew CSS, "right to left", or needs to build Hebrew UI. Covers CSS logical properties, Tailwind RTL, React/Vue RTL, Hebrew typography, and font selection. Do NOT use for Arabic RTL (similar but different typography) unless user explicitly asks for shared RTL patterns.
by @skills-il
Process 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.