"What is your name? This will be displayed as the skill creator on the Skills IL directory. Your GitHub username is fine too."

creator_name

"What is your email address? This is required so we can notify you when your skill is published, featured, or if we need to contact you about updates. It will not be displayed publicly."

creator_email

• creator_name

  is required. Default to the GitHub username if the user prefers not to provide their full name.

• creator_email

  is required and must be a valid email address. Do NOT proceed without it.
• Store both values -- they will be used in the

  metadata.author

  field and when submitting to the directory.
• If the user declines to provide an email, explain that it is mandatory for the submission process and they will not receive notifications about their skill without it.

• Trigger: What the user would say (in English AND Hebrew transliteration)
• Steps: What multi-step workflow this requires
• Tools: Which tools are needed (built-in or MCP)
• Result: What success looks like

Use Case: Validate Israeli e-invoice
Trigger: User says "validate hashbonit electronit" or "check SHAAM allocation"
Steps:
1. Parse invoice fields
2. Validate allocation number format
3. Check against SHAAM rules
Result: Invoice validated with pass/fail report

• Legal thresholds and limits (e.g., small claims court limit, tax brackets, age limits)
• Government processes and forms (e.g., filing procedures, required documents)
• Institutional names and contact details (e.g., phone numbers, websites, addresses)
• Pricing and fees (e.g., copayments, filing fees, service costs)
• Recent law changes that may have taken effect this year

• Search official Israeli government sources (gov.il, Knesset, Bituach Leumi)
• Check current-year dates in your searches (laws and thresholds change annually)
• Cross-reference at least 2 sources for critical facts like monetary limits or legal requirements
• Note the verification date so the skill can be updated when facts change

python scripts/scaffold-skill.py --name <skill-name> --category <category-repo>

<skill-name>/
├── SKILL.md          # Template with frontmatter skeleton
├── SKILL_HE.md       # Hebrew companion stub
├── scripts/          # For helper scripts
└── references/       # For reference documentation

• Folder name is kebab-case
• No spaces, underscores, or capitals
• Name does not contain "claude" or "anthropic"
• No README.md inside the skill folder (skill folders must not contain README.md)
• The repo-level README.md (at the root of the category repo) must be written in English. This is required because the repo is public on GitHub and the README serves as the entry point for international developers and AI agents. Hebrew content belongs in SKILL_HE.md files inside skill folders, not in the repo README.

metadata

metadata.json

---
name: <skill-name>
description: >-
  [What it does -- one sentence]. Use when user asks to [triggers in English],
  "[Hebrew transliteration 1]", "[Hebrew transliteration 2]", or [more triggers].
  [Key capabilities]. Do NOT use for [anti-triggers] (use [alternative-skill] instead).
license: MIT
allowed-tools: '<tools if needed>'      # optional, only when scripts call CLI tools
compatibility: >-                         # optional
  [Network/system requirements]. Works with Claude Code, Claude.ai, Cursor.
---

metadata:

version:

tags:

display_name:

display_description:

author:

category:

supported_agents:

{
  "author": "<creator_name from Step 2>",
  "version": "1.0.0",
  "category": "<category-repo>",
  "tags": {
    "he": ["<tag1-he>", "<tag2-he>", "ישראל"],
    "en": ["<tag1>", "<tag2>", "israel"]
  },
  "display_name": {
    "he": "<Hebrew display name>",
    "en": "<English Display Name>"
  },
  "display_description": {
    "he": "<Hebrew description>",
    "en": "<English description, mirrors the main description field>"
  },
  "supported_agents": [
    "claude-code",
    "cursor",
    "github-copilot",
    "windsurf",
    "opencode",
    "codex",
    "gemini-cli"
  ]
}

compatibility

antigravity

• No em dashes (U+2014) or en dashes (U+2013) anywhere in SKILL.md, SKILL_HE.md, metadata.json, references, or scripts. Replace with commas, parentheses, periods, or "to" for ranges. Use the regular ASCII hyphen-minus instead.
• All 12 category repos use

  master

  , not

  main

  , as the default branch.

• github_url

  format must include the full path to the skill folder, not just the repo root:

  https://github.com/skills-il/<repo>/tree/master/<slug>

  .

"Please provide Hebrew translations for each tag. Tags must have matching

he

and

en

arrays (same length). For example, if your English tags are

[invoicing, tax, israel]

, the Hebrew tags should be

[invoices, taxes, israel]

. What are the Hebrew equivalents for your tags?"

• Both

  he

  and

  en

  arrays are required -- no tag may be left untranslated
• Arrays must be the same length (each English tag has exactly one Hebrew counterpart)
• No empty strings allowed in either array
• Technical terms that have no Hebrew equivalent can stay in English in both arrays (e.g.,

  API

  ,

  MCP

  )

• Must follow pattern:

  [What it does] + [When to use it] + [Key capabilities] + [Do NOT use for X]

• Under 1024 characters total
• No XML angle brackets (< >) anywhere in frontmatter
• Include trigger phrases users would actually say
• Include Hebrew transliterations in quotes (e.g., "tlush maskoret")
• End with

  Do NOT use for

  boundary + cross-reference to related skills

• No tools needed: omit the field
• Python scripts:

  'Bash(python:*)'

• Python + web:

  'Bash(python:*) WebFetch'

• Multiple CLI tools:

  'Bash(python:*) Bash(curl:*) WebFetch'

• pip installs:

  'Bash(python:*) Bash(pip:*)'

1. ... Result: ...

• scripts/<name>.py

  -- <What it does, how to run>. Run:

  python scripts/<name>.py --help

• references/<name>.md

  -- <What it contains>. Consult when <specific situation>.

• SKILL.md frontmatter uses YAML with specific nested structure (metadata.tags.he/en arrays). Agents may flatten the tags into a single array instead of using the bilingual he/en structure.
• Hebrew content in SKILL_HE.md must never appear inside code blocks (```) because code blocks do not support RTL rendering. Use plain text or bullet lists for Hebrew content.
• The skill description field has a dual purpose: it serves as both the YAML frontmatter description and the trigger text for agent matching. Agents may write a generic description that fails to trigger on relevant user queries.
• Skills must validate with the skills-il schema (name, description, license, metadata with version/category/tags). Agents may omit required fields like supported_agents or display_name.

references/

hospital-directory.md

crisis-hotlines-directory.md

fair-rental-law-summary.md

ivf-process-detailed.md

hebrew-rental-glossary.md

contract-checklist.md

evidence-guide.md

universities-comparison.md

city-rental-guide.md

demand-letter-template.md

• Be under 3,000 words
• Use markdown with clear headers and tables
• Include Hebrew terms in parentheses
• Be linked from SKILL.md with "Consult when..." guidance

scripts/

sekher-calculator.py

filing-fee-calculator.py

fertility-coverage-checker.py

therapy-cost-estimator.py

rental-budget-calculator.py

rent-index-calculator.py

• Use

  #!/usr/bin/env python3

  shebang
• Include argparse with

  --help

• Have a clear docstring explaining usage
• Use stdlib only (no external dependencies)
• Include input validation with clear error messages
• Print results in clean, formatted output

## Bundled Resources

## Troubleshooting

## משאבים מצורפים

• Translate the body instructions to Hebrew
• Keep code blocks, field names, and API references in English
• Use Hebrew-native terminology (not transliterations)
• Maintain the same step numbering and section structure

grep -rEoh 'https?://[^ )>"'\'']+' <skill-name>/ | sort -u > /tmp/<skill-name>-urls.txt
cat /tmp/<skill-name>-urls.txt

while IFS= read -r url; do
  status=$(curl -sL -o /dev/null -w '%{http_code}' --max-time 10 "$url" 2>/dev/null)
  [ "$status" != "200" ] && echo "[$status] $url"
done < /tmp/<skill-name>-urls.txt

• .gov.il

  URLs (Israeli government sites restructure frequently)
• Israeli startup domains (

  .co.il

  ) that may have gone offline
• Reference Links table entries (Step 8.5) -- these are the most visible links to users

./scripts/validate-skill.sh <skill-name>/SKILL.md

SKILL.md

---

name

description

<>

<>

• Domain facts verified against official sources (Step 4)
• All URLs return HTTP 200 (Step 9.5)
• Description includes WHAT and WHEN
• Instructions are specific and actionable
• Examples cover 2+ real scenarios
• Troubleshooting covers likely errors
• Reference Links section with 3-6 verified official source URLs
• Hebrew companion exists and section structure matches SKILL.md 1:1 (including

  ## קישורי עזר

  )
• At least 2 reference files in

  references/

  with "Consult when..." guidance
• At least 1 helper script in

  scripts/

  with argparse and

  --help

• No security issues (secrets, injection vectors)

• supported_agents

  list is accurate (all compatible agents included)

• metadata.version

  is set (e.g., 1.0.0)

• metadata.tags

  has both

  he

  and

  en

  arrays of equal length with no empty strings

• creator_name

  and

  creator_email

  collected from user (Step 2)
• Repo-level README.md is written in English (not Hebrew)

1. Choose submission type: "Existing Repository" (if you pushed your skill to a GitHub repo) or "Proposal" (if you want the skills-il team to create the repo)
2. Fill in the form with: your GitHub repo URL, creator name, and creator email (from Step 2)
3. The form will fetch your SKILL.md and run a live GitHub Verification scorecard. You'll see pass/fail for each of the 5 Critical signals. If any fail, fix them per Step 10.5 and re-submit.
4. The skills-il team will review your submission, run security analysis, and publish it if it passes

1. Category: government-services
2. Creator info: Ask for name and email
3. Use cases: search by case number, search by judge name, search by topic (Hebrew legal terms)
4. Fact-check: Verify court system structure, Nevo access methods, citation formats via official sources
5. Scaffold:

   python scripts/scaffold-skill.py --name israeli-court-decisions --category government-services

6. Frontmatter: name=israeli-court-decisions, author=creator_name, triggers include "psakei din", "beit mishpat", "nevo"
7. Instructions: Steps for search types, result parsing, citation format
8. References:

   references/court-hierarchy.md

   (court levels),

   references/citation-format.md

   (Israeli legal citation rules)
9. Hebrew: SKILL_HE.md with native legal terminology
10. Validate:

    ./scripts/validate-skill.sh israeli-court-decisions/SKILL.md

11. Submit via the submission page

1. Category: developer-tools (or government-services for address lookup APIs)
2. Creator info: Ask for name and email
3. Use cases: format for postal mail, validate mikud, normalize city names
4. Fact-check: Verify mikud format rules, Israel Post API availability, city name mappings
5. Scaffold:

   python scripts/scaffold-skill.py --name israeli-address-formatter --category developer-tools

6. Frontmatter: triggers include "format ktovet", "mikud", "address normalization"
7. Instructions: Format rules, mikud lookup, bilingual city names
8. References:

   references/mikud-format.md

   ; Scripts:

   scripts/mikud-validator.py

9. Hebrew: SKILL_HE.md
10. Validate: passes all checks
11. Submit via the submission page

1. Category: tax-and-finance
2. Creator info: Ask for name and email
3. Use cases: categorize transactions, detect recurring charges, monthly summary
4. Fact-check: Verify Israeli bank API patterns, transaction category standards
5. Scaffold:

   python scripts/scaffold-skill.py --name israeli-bank-analyzer --category tax-and-finance

6. metadata.json: include the relevant Recommended MCP Servers section in SKILL.md (and

   ## שרתי MCP מומלצים

   in SKILL_HE.md) pointing to

   israeli-bank-mcp

   . Description triggers include "nituch tenuot bank"
7. Instructions: MCP tool calls for fetching transactions, categorization logic, summary generation
8. References:

   references/bank-api-reference.md

   ; Scripts:

   scripts/transaction-categorizer.py

9. Hebrew: SKILL_HE.md with banking terminology
10. Validate: passes all checks
11. Submit via the submission page

• scripts/scaffold-skill.py

  -- Creates the complete folder structure for a new skills-il skill: SKILL.md template with frontmatter skeleton, SKILL_HE.md stub, scripts/ and references/ directories. Validates name format and prevents overwrites. Run:

  python scripts/scaffold-skill.py --help

• references/skill-spec.md

  -- Complete skills-il SKILL.md specification including all frontmatter fields (required and optional), description-writing formula with good/bad examples, the 5 skill patterns from Anthropic's guide, quality checklist, and validation rules. Consult when writing frontmatter or instructions and you need detailed guidance beyond the steps above.

• SKILL.md frontmatter uses YAML with specific nested structure (metadata.tags.he/en arrays). Agents may flatten the tags into a single array instead of using the bilingual he/en structure.
• Hebrew content in SKILL_HE.md must never appear inside code blocks (```) because code blocks do not support RTL rendering. Use plain text or bullet lists for Hebrew content.
• The skill description field has a dual purpose: it serves as both the YAML frontmatter description and the trigger text for agent matching. Agents may write a generic description that fails to trigger on relevant user queries.
• Skills must validate with the skills-il schema (name, description, license, metadata with version/category/tags). Agents may omit required fields like supported_agents or display_name.