Israeli AI Compliance Kit
Trusted89/100Guide Israeli ML teams through the AI governance and compliance stack: Ministry of Innovation December 2023 AI policy principles, Privacy Protection Law (PPL) and Amendment 13 applied to ML training data, sector-specific rules (Bank of Israel Directive 364, Ministry of Health AMAR medical-device AI), and EU AI Act exposure for Israeli exporters. Generates model cards, data statements, and DPIA templates tailored to Israeli context. Use when preparing AI governance docs, answering an enterprise customer's AI risk review, classifying a system under the EU AI Act, or building an internal responsible-AI checklist. Prevents costly compliance gaps when shipping AI to regulated markets. Do NOT use for general PPL policy (use israeli-privacy-shield), web app security (use israeli-appsec-scanner), or SOC/threat triage (use israeli-cybersecurity-ops).
Trust score 89/100 (Trusted) · 4+ installs · 2 GitHub contributors · MIT license
Israeli ML teams shipping AI products face a fragmented compliance landscape: voluntary principles from the Ministry of Innovation, the Privacy Protection Law with Amendment 13 in force since August 14, 2025, sector regulators each drafting their own AI guidance, and the EU AI Act rolling out in staggered phases through 2027 that reach anyone selling into Europe. Most teams discover these requirements mid-procurement when an enterprise customer demands a model card, data statement, and DPIA. There is no unified checklist or template set tailored to the Israeli regulatory context.
npx skills-il add skills-il/security-compliance --skill israeli-ai-compliance-kit -a claude-codeInstall on Claude.ai, Claude Desktop, ChatGPT, Manus, or other platforms
- 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.
When to Apply
- When an enterprise customer requests AI risk review documents (model card, data statement, DPIA)
- When classifying a system under the EU AI Act before entering the EU market
- When building a financial ML system that must align with BoI Directive 364
- When preparing medical-device AI for Ministry of Health AMAR review
- When building an internal AI governance checklist aligned to MoI ethical principles
Try These Prompts
An enterprise customer asked for a model card for our Hebrew summarization API. Draft one with Israeli-context fields (PPL registration, Amendment 13 DPO, MoI 2023 principles alignment, sector regulator applicability).
I want to sell a credit-scoring model to a German bank. Walk me through the EU AI Act decision tree and tell me if it is high-risk and what my obligations are as an Israeli provider.
We are building a customer support chatbot that processes Hebrew conversations. Draft a DPIA aligned to PPL and Amendment 13 which takes effect August 2025.
A banking customer asked us to comply with Directive 361. Explain that 361 was consolidated into Directive 364 and help me draft a clean reply with the right reference.
Frequently Asked Questions
Related Skills
Comprehensive guide for working with Pikud HaOref (Israel Home Front Command) alert APIs - the official and community endpoints that publish real-time rocket alerts, earthquake warnings, and other civil defense notifications across Israel. Use this skill whenever someone wants to build an integration with Pikud HaOref alerts, fetch live or historical alert data, set up monitoring or dashboards for Israeli emergency alerts, write code that consumes oref.org.il endpoints, deploy an alert service, or understand the available API landscape. Also trigger when someone mentions "red alert API", "tzeva adom", "oref alerts", "rocket alert Israel", "Home Front Command API", or any Hebrew references like "פיקוד העורף" or "צבע אדום". Even if the user just says "I want to get alerts from Israel" or "build something with Israeli civil defense data", this skill is the right starting point. Do NOT use for US weather alerts (NWS/FEMA), UK emergency alerts, generic webhook/push notification frameworks, or non-Israeli civil defense systems.
Israeli Privacy Protection Law compliance guidance including Amendment 13 (effective August 14, 2025), database registration, consent requirements, data security, cross-border transfers, breach notification, privacy protection officer appointment, and AI governance. Use when user asks about Israeli privacy law, "haganat pratiut", "tikun 13", data protection in Israel, GDPR compliance for Israeli companies, privacy policy requirements, or database registration. Covers the Privacy Protection Law 1981, Amendment 13, and 2017 Security Regulations. Do NOT use for EU GDPR-only questions without Israeli context.
Coordinate Israeli-built cybersecurity tools for security operations including threat triage, vulnerability management, compliance checking, and incident response. Use when user mentions security operations, "SOC", vulnerability scanning, threat triage, compliance assessment, or asks to coordinate Wiz, Snyk, Check Point, CyberArk, SentinelOne, Armis, Torq, or Pentera tools. Embeds Israeli security best practices including INCD guidelines and Israeli Privacy Protection Law compliance. Do NOT use for offensive security testing or creating exploits.
Use at your own risk. Terms of Use · Security
Want to build your own skill? Try the Skill Creator · Submit a Skill