add-skill-to-plugin

Add a Skill to Israel-Agent-Skills-Plugin

Meta-skill that converts Daniel's rough notes into a properly structured skill file inside this repo and activates it locally.

When to invoke

Daniel pastes free-form notes describing something he wants Claude to be able to do in the context of Israel / Hebrew / regional workflows — e.g. "check if a medicine is on Maccabi", "file a 106 report with Jerusalem municipality", "look up bus times on Egged". The notes will typically include:

• A rough task description
• One or more URLs (landing page + example detail pages)
• Hebrew field labels copy-pasted from the site
• Hints about what the user actually cares about in the output
• Occasionally gotchas (captcha, autocomplete, RTL layout, login required)

Do not wait for a clean spec — these notes are the input.

Repo conventions (match these)

Plugin root: /home/daniel/repos/github/my-repos/Israel-Agent-Skills-Plugin/

Layout:

.claude-plugin/plugin.json
skills/
  <skill-name>/
    SKILL.md

• Skill directory name: kebab-case, descriptive, prefixed with the service or domain when useful (e.g. jerusalem-municipality-report, maccabi-medicine-lookup). Not Train-Case — skill dirs are lowercase-kebab even though the repo name is Train-Case.
• One SKILL.md per skill. Additional assets (reference data, schemas) can live alongside but keep the directory lean.
• Frontmatter is YAML with two fields:
  • name: must match the directory name exactly.
  • description: a long, information-dense paragraph. This is what Claude sees when deciding whether to trigger the skill, so it must:
    • State when to use the skill ("Use when the user wants to…").
    • Mention the concrete site / API / artefact involved, including Hebrew names where relevant (e.g. עיריית ירושלים, סל הבריאות).
    • End with a list of explicit trigger phrases the user is likely to say, in both English and Hebrew-transliterated forms where natural.
• Body follows a loose but consistent structure — look at skills/jerusalem-municipality-report/SKILL.md and skills/maccabi-medicine-lookup/SKILL.md as canonical examples. Typical sections:
  • One-sentence restatement of what the skill does.
  • Entry point URL / API endpoint.
  • How to search / navigate (including UI quirks: autocomplete, reCAPTCHA, RTL, cookie banners).
  • What to extract (tables of Hebrew label ↔ English ↔ type ↔ required).
  • Output format (show an example block).
  • Playwright / tooling notes.
  • Out of scope.
• Never invent facts. If the raw notes don't cover something (e.g. selector IDs, exact price-field label), say so in the SKILL.md rather than guessing.