agentleFS
danielrosehilldanielrosehill/Claude-Israel-Agent-Skills-Plugin/skills/jerusalem-municipality-report/SKILL.md

jerusalem-municipality-report

Skill2 starsChanged 24 days agoMITView on GitHub

Use when the user wants to file a "106" public-contact report with the Jerusalem Municipality (עיריית ירושלים, pniya la-106). Opens the official form at https://www.jerusalem.muni.il/he/contactus/106/ via Playwright, fills the applicant, contact, address, and description fields from user-supplied data, pauses for the user to solve the reCAPTCHA, then submits. Trigger phrases: "open a Jerusalem municipality report", "file a 106", "report something to iriya", "pniya la-iriya", "report a pothole / graffiti / broken streetlight to Jerusalem".

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. About 0 are common, 5 are distinctive, and 10 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 10

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    All labels are in Hebrew; the skill may fill Hebrew or English values (Hebrew preferred for addresses).

    line 16
  2. Very specific:

    Ask for any missing mandatory fields.

    line 62
  3. Very specific:

    Use the Playwright MCP tools from the plugin_playwright server.

    line 68
  4. Very specific:

    Navigate: Call browser_navigate with url: "https://www.jerusalem.muni.il/he/contactus/106/".

    line 88
  5. Very specific:

    Snapshot: Call browser_snapshot (no args).

    line 89
  6. Very specific:

    Fill in one batch: Call browser_fill_form with a fields array like:

    line 90
  7. Very specific:

    If browser_fill_form fails for the ID-type combobox (the form uses a custom widget, not a native <select>), fall back to browser_click on …

    line 107
  8. Very specific:

    Attachments (optional): If the user provided file paths, call browser_click on the צירוף קובץ button to open the file chooser, then …

    line 108
  9. Very specific:

    Verify: Call browser_snapshot again and confirm every required field is populated.

    line 109
  10. Distinctive:

    Before clicking submit, say in chat:

    line 113
  11. Very specific:

    Wait for the user's reply.

    line 117
  12. Distinctive:

    Do not fabricate personal details: Every field must come from the user directly — never guess an ID number, phone, or email.

    line 136
  13. Distinctive:

    Do not attempt to bypass the reCAPTCHA: Always hand it to the user.

    line 137
  14. Very specific:

    Respect Hebrew/RTL: When typing Hebrew values, paste them whole rather than character-by-character.

    line 138
  15. Distinctive:

    One submission per invocation: Do not loop or auto-file multiple reports.

    line 139

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Jerusalem Municipality Report (106)

Files a public-contact report ("פנייה ל-106") with the Jerusalem Municipality via the official online form. The form uses reCAPTCHA, so this skill uses a visible Playwright browser and hands the reCAPTCHA to the user — it does not try to solve it.

Form URL

https://www.jerusalem.muni.il/he/contactus/106/

Form fields (as of 2026-04-23)

All labels are in Hebrew; the skill may fill Hebrew or English values (Hebrew preferred for addresses).

פרטי הפונה — Applicant details

Label (HE)EnglishTypeRequired
שם פרטיFirst nametextyes
שם משפחהLast nametextyes
אמצעי זיהויID typeselect (בחר / תעודת זהות / דרכון)yes
מספר זיהויID numbertextyes

פרטי יצירת קשר — Contact details

Label (HE)EnglishTypeRequired
מספר טלפוןPhone numbertextyes
מספר טלפון נוסףAdditional phonetextno
דואר אלקטרוניEmailtextyes

כתובת האירוע — Event address

Label (HE)EnglishTypeRequired
יישובCity (usually ירושלים)textyes
רחובStreettextno
מספר ביתHouse numbertextno

תיאור הפנייה — Report description

Label (HE)EnglishTypeRequired
תוכן הפנייהReport body (character counter visible)textareayes
צירוף קובץFile attachment — up to 3 files, allowed types: png / doc / pdf / tif / jpg / gif, max 5 MB eachfileno

Submit

Button label: שליחה (Send), with sendIco.png icon.

Success indicator

On success the page shows: תודה רבה על פנייתך. פנייתך הועברה בהצלחה לעיריית ירושלים בתאריך DD.MM.YYYY. A reference number is emailed / SMSed later.

Procedure

1. Gather inputs from the user

Ask for any missing mandatory fields. Offer sensible defaults: city defaults to ירושלים, ID type defaults to תעודת זהות. Confirm the report body in the user's preferred language (Hebrew or English — the form accepts either, Hebrew gets faster triage).

Required before proceeding: first name, last name, ID type + number, phone, email, report body. Optional: additional phone, street, house number, attachments (list absolute paths).

2. Open the form via Playwright

Use the Playwright MCP tools from the plugin_playwright server. Do not use a headless browser — the user must see and solve the reCAPTCHA.

Exact tool names and validated call signatures (v1.0.0 of the official Playwright MCP):

ActionToolRequired parameters
Open URLmcp__plugin_playwright_playwright__browser_navigateurl (string)
Get element refsmcp__plugin_playwright_playwright__browser_snapshotnone (optional: depth, filename)
Batch-fill fieldsmcp__plugin_playwright_playwright__browser_fill_formfields[] — each {name, type, ref, value} where type ∈ textbox | checkbox | radio | combobox | slider
Type into one fieldmcp__plugin_playwright_playwright__browser_typeref, text (optional: element, slowly, submit)
Select dropdownmcp__plugin_playwright_playwright__browser_select_optionref, values[]
Upload filesmcp__plugin_playwright_playwright__browser_file_uploadpaths[] (absolute paths)
Clickmcp__plugin_playwright_playwright__browser_clickref (optional: element, button, doubleClick, modifiers[])
Wait for textmcp__plugin_playwright_playwright__browser_wait_forone of text, textGone, time
Screenshotmcp__plugin_playwright_playwright__browser_take_screenshottype ∈ png | jpeg (optional: element+ref together, filename, fullPage)

Note: ref tokens come from the current browser_snapshot output. They are not stable across navigations — always re-snapshot before a new batch of interactions. element is a human-readable description used for the permission prompt; it must be supplied whenever ref is (except for browser_click where only ref is required).

Procedure:

  1. Navigate. Call browser_navigate with url: "https://www.jerusalem.muni.il/he/contactus/106/".
  2. Snapshot. Call browser_snapshot (no args). Parse the returned accessibility tree to find refs for each form field by matching Hebrew labels (שם פרטי, שם משפחה, אמצעי זיהוי, מספר זיהוי, מספר טלפון, מספר טלפון נוסף, דואר אלקטרוני, יישוב, רחוב, מספר בית, תוכן הפנייה, שליחה).
  3. Fill in one batch. Call browser_fill_form with a fields array like:
    {
      "fields": [
        {"name": "First name",     "type": "textbox",  "ref": "<ref>", "value": "Daniel"},
        {"name": "Last name",      "type": "textbox",  "ref": "<ref>", "value": "Rosehill"},
        {"name": "ID type",        "type": "combobox", "ref": "<ref>", "value": "תעודת זהות"},
        {"name": "ID number",      "type": "textbox",  "ref": "<ref>", "value": "<id>"},
        {"name": "Phone",          "type": "textbox",  "ref": "<ref>", "value": "<phone>"},
        {"name": "Email",          "type": "textbox",  "ref": "<ref>", "value": "<email>"},
        {"name": "City",           "type": "textbox",  "ref": "<ref>", "value": "ירושלים"},
        {"name": "Street",         "type": "textbox",  "ref": "<ref>", "value": "<street>"},
        {"name": "House number",   "type": "textbox",  "ref": "<ref>", "value": "<num>"},
        {"name": "Report body",    "type": "textbox",  "ref": "<ref>", "value": "<body>"}
      ]
    }
    If browser_fill_form fails for the ID-type combobox (the form uses a custom widget, not a native <select>), fall back to browser_click on it, re-snapshot, then browser_click the תעודת זהות option. Attempt browser_select_option with values: ["תעודת זהות"] only if the snapshot shows a native combobox role.
  4. Attachments (optional). If the user provided file paths, call browser_click on the צירוף קובץ button to open the file chooser, then browser_file_upload with paths: ["/abs/path1", "/abs/path2", ...] (max 3 files; accepted types: png doc pdf tif jpg gif; each ≤ 5 MB). Validate sizes and extensions before calling.
  5. Verify. Call browser_snapshot again and confirm every required field is populated.

3. Hand the reCAPTCHA to the user

Before clicking submit, say in chat:

The form is filled. Please solve the reCAPTCHA in the browser window, then reply "continue" and I'll submit.

Wait for the user's reply. Do not click the reCAPTCHA checkbox or iframe yourself (browser_iframe_click is explicitly forbidden here) — Google penalises automated interaction and the submission will be rejected.

4. Submit

Once the user confirms:

  1. browser_click with ref: "<ref-of-שליחה>" (and element: "Send button (שליחה)" for the permission prompt).
  2. browser_wait_for with text: "תודה רבה על פנייתך" — the success banner. Fall back to text: "הועברה בהצלחה" if the first times out.
  3. browser_take_screenshot with type: "png", fullPage: true, and filename: "jerusalem-106-confirmation-YYYY-MM-DD.png" (use today's date). Save under the current working directory, or ~/Documents/ if not in a project.
  4. Report: success, the confirmation date shown on screen, and that the reference number will arrive by email/SMS.

5. If submission fails

  • reCAPTCHA rejected → ask the user to re-solve and click Submit again.
  • Field validation error (red text next to a field) → re-read the snapshot, identify the error, correct, resubmit.
  • Server error → capture a screenshot, report the error text verbatim, and let the user decide whether to retry or file via phone (106 from any Israeli phone).

Guardrails

  • Do not fabricate personal details. Every field must come from the user directly — never guess an ID number, phone, or email.
  • Do not attempt to bypass the reCAPTCHA. Always hand it to the user.
  • Respect Hebrew/RTL. When typing Hebrew values, paste them whole rather than character-by-character; browser_type handles this correctly.
  • One submission per invocation. Do not loop or auto-file multiple reports.
  • Re-verify the form structure each run. Municipal forms change without notice. Always re-read the snapshot rather than relying on cached selectors.

Out of scope

  • Payments, permits, parking-ticket appeals, building-permit submissions — these are separate online services on the Jerusalem Municipality portal, not the 106 form.
  • Status lookups — use https://www.jerusalem.muni.il/he/contactus/checkinquiry/ (separate skill candidate).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.