fiber-availability-check
Skill2 starsChanged 24 days agoMITView on GitHub
Check whether fiber-optic internet is deployed at an Israeli street address, across multiple providers (Bezeq Bfiber and HOT Fiber today). Use when the user asks "is there fiber at my address", "can I get Bfiber", "does HOT fiber reach [street]", "fiber availability in [city]", "are there sivim opti'im [סיבים אופטיים] at this address", or is comparing ISP coverage before ordering. Supports a reference test address (בן יהודה 1, ירושלים) and reads defaults from a local preferences file so the user can check their own address with no arguments.
- Reads credentials
In this repository20 other files it gives its agents.
- add-skill-to-pluginSkill
- ben-gurion-flight-boardSkill
- discover-israel-skillsSkill
- drug-co-il-lookupSkill
- environment-checkSkill
- home-front-command-guidelinesSkill
- install-israel-pluginsSkill
- israel-conferencesSkill
- israel-drugs-registry-lookupSkill
- israel-news-rssSkill
- jerusalem-council-meetingsSkill
- jerusalem-municipality-reportSkill
- kol-zchut-lookupSkill
- list-skillsSkill
- maccabi-medicine-lookupSkill
- medicine-availability-checkSkill
- miklatim-lookupSkill
- nsc-travel-threatSkill
- salary-conversionSkill
- update-plugin-readmeSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
Call with --show-unsupported to include these notes in the output.
- Very specific: line 24
Use city=ירושלים, street=בן יהודה, house=1 to smoke-test the pipeline.
- Distinctive: line 100
No secrets required. Both supported endpoints are public.
- Distinctive: line 102
If a future provider requires a phone/email for a lead-style submit step, the prefs file already has those slots — the skill will pick them …
- Very specific: line 103
If either provider's response shape changes (e.g.
≈ “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.
Files
Israel Fiber Availability Check
Multi-provider address-level fiber availability lookup for Israel. Plain-HTTP (no browser), device-agnostic.
Providers
| Provider | Status | Method |
| Bezeq (Bfiber) | Supported | Public JSON API on bezeq.co.il |
| HOT (HOT Fiber) | Supported | Public JSON API on hot.net.il |
| Partner | Not supported | No public address check — their form is lead-capture only (name + phone). |
| Cellcom | Not supported | React SPA behind Imperva/Incapsula; would need headless-browser escalation. |
| IBC / Unlimited | Not supported | Brand sites parked / offline at time of authoring. |
Call with --show-unsupported to include these notes in the output.
Reference test address
Use city=ירושלים, street=בן יהודה, house=1 to smoke-test the pipeline. As of authoring, Bezeq reports available and HOT reports unavailable at this address — a healthy signal that both backends are reachable and the normalizer is working.
Local preferences (user details never in the repo)
User-specific defaults live outside the plugin repo. Two options, in precedence order (last wins):
- YAML (recommended) —
~/.config/israel-agent-skills/preferences.yaml:default_city: ירושלים default_street: בן יהודה default_house: "1" default_entrance: "" # optional phone: "+9725xxxxxxxx" # reserved for future providers that need a lead step email: "you@example.com" - .env-style —
~/.config/israel-agent-skills/fiber.env:IL_FIBER_CITY=ירושלים IL_FIBER_STREET=בן יהודה IL_FIBER_HOUSE=1 IL_FIBER_PHONE=+9725xxxxxxxx IL_FIBER_EMAIL=you@example.com - Process env vars of the same names (highest precedence, overrides files).
With any of these set, the user can run the skill with zero arguments and get a check for their own address. CLI flags always win over preferences.
Permissions: the prefs directory is user-scoped. If you ever add secrets (API tokens), put them under ~/.config/israel-agent-skills/secrets/ with chmod 600 and do not co-mingle with the plain preferences file.
Usage
# Check all supported providers for the test address
python3 scripts/check_fiber.py --city "ירושלים" --street "בן יהודה" --house 1
# Use defaults from ~/.config/israel-agent-skills/preferences.yaml (no args)
python3 scripts/check_fiber.py
# One provider only
python3 scripts/check_fiber.py --provider bezeq
python3 scripts/check_fiber.py --provider hot
# Include the notes about unsupported providers
python3 scripts/check_fiber.py --show-unsupported
# JSON in, JSON out
echo '{"city":"ירושלים","street":"בן יהודה","house":1,"providers":["bezeq","hot"]}' \
| python3 scripts/check_fiber.py --stdinOutput schema
{
"query": {"city": "...", "street": "...", "house": "1", "entrance": ""},
"results": {
"bezeq": {
"provider": "bezeq",
"status": "available | coming_soon | unavailable | address_not_found | unknown | error",
"status_code": 1,
"summary": "human-readable one-liner",
"error": null,
"raw": { ... provider response ... }
},
"hot": { ... same shape ... }
},
"unsupported": {},
"fetched_at": "2026-04-23T21:06:22+03:00",
"test_address_note": "..."
}Statuses are normalized across providers so callers can compare coverage without provider-specific glue.
Notes
- No secrets required. Both supported endpoints are public.
- City and street names should be in Hebrew for best matching. Both Bezeq and HOT share the same
cityId=3000for Jerusalem, which is why the same preference file works across providers. - If a future provider requires a phone/email for a lead-style submit step, the prefs file already has those slots — the skill will pick them up without a code change to the CLI surface.
- If either provider's response shape changes (e.g. another layer of JSON wrapping, new status code), failures show as
status: "error"with the exception string so it's obvious what broke.
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
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.

