agentleFS
danielrosehilldanielrosehill/Claude-Israel-Agent-Skills-Plugin/skills/israel-conferences/SKILL.md

israel-conferences

Skill2 starsChanged 25 days agoMITView on GitHub

Use when the user wants to find upcoming conferences, professional events, summits, expos, or industry meetups happening in Israel — by topic (tech, AI, biomed, finance, marketing, HR, cyber, startup), by city (Tel Aviv, Jerusalem, Haifa), by date window, or in general ("what conferences are coming up in Israel", "any AI events in Tel Aviv next month", "כנסים בישראל", "אירועים מקצועיים", "tech conferences Israel"). Checks a curated whitelist of Israeli event aggregators FIRST (events.co.il, conferenceindex.org, IVC, ICX, dev.events) before falling back to general web search.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Only after these have been consulted should an open web search be used (and only to fill in gaps — e.g.

    line 21
  2. Very specific:

    Call WebFetch on each whitelist URL in order, asking the model to extract events matching the user's filters (topic, city, date window).

    line 29
  3. Very specific:

    If the user asked for a topic poorly covered by the whitelist (e.g.

    line 31
  4. Distinctive:

    When the user's request is broad ("conferences in Israel"), ask or assume:

    line 56
  5. Distinctive:

    Do not persist or cache results — event listings change daily.

    line 78

≈ “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

Israel Conferences — Upcoming Events Lookup

Find upcoming conferences and professional events in Israel. The skill enforces a priority order: hit the curated whitelist of Israel-focused event aggregators before doing any open web search, so results are anchored in known-good sources rather than ad-spam.

Priority whitelist (check first, in order)

#URLCoverageLanguageNotes
1https://events.co.il/General — business, marketing, HR, tech, professionalHebrewLargest Israeli professional event listing site
2https://events.co.il/events?locale=heSame as #1 — direct events feedHebrewUse this URL if the homepage is too marketing-heavy
3https://conferenceindex.org/conferences/israelAcademic / scientific conferences in IsraelEnglishGlobal academic index, Israel filter
4https://www.ivc-online.com/EventsVC, startup, investment, hi-techEnglishIVC Research Center events feed
5https://www.icx.co.il/לוח-הכנסים-המקצועייםProfessional conferences (medical, legal, accounting, engineering)Hebrew"לוח הכנסים המקצועיים" — Israel's professional conference board
6https://dev.events/AS/IL/techDeveloper / tech conferencesEnglishClean structured listing, easiest to parse

Only after these have been consulted should an open web search be used (and only to fill in gaps — e.g. a niche topic the aggregators miss).

How to use

1. Quick lookup — agent-driven (preferred)

For most user queries, the right pattern is:

  1. Call WebFetch on each whitelist URL in order, asking the model to extract events matching the user's filters (topic, city, date window). Stop early if you have enough relevant results.
  2. Merge results, dedupe by event name + date, sort by start date ascending.
  3. If the user asked for a topic poorly covered by the whitelist (e.g. very niche), supplement with WebSearch for "upcoming [topic] conference Israel 2026".
  4. Return a tight list: name, date(s), city/venue, organiser, link.

2. Bulk fetch — helper script

python3 scripts/fetch_conferences.py                 # fetch all whitelist URLs, print raw text
python3 scripts/fetch_conferences.py --source dev    # only dev.events
python3 scripts/fetch_conferences.py --list-sources  # show source keys
python3 scripts/fetch_conferences.py --json          # JSON envelope per source

The script is a thin fetch+strip helper — it does not try to parse every aggregator's bespoke HTML. It returns cleaned text/HTML per source, ready to hand to the LLM for extraction. This avoids brittle scrapers breaking when sites redesign.

Source keys

  • events → events.co.il homepage
  • events-feed → events.co.il direct events feed
  • conferenceindex → conferenceindex.org Israel page
  • ivc → ivc-online.com events
  • icx → icx.co.il professional conferences board
  • dev → dev.events Israel/tech

Filters to surface to the user

When the user's request is broad ("conferences in Israel"), ask or assume:

  • Topic — tech / AI / biomed / fintech / marketing / HR / legal / medical / academic / startup
  • City — Tel Aviv, Jerusalem, Haifa, Herzliya, online
  • Date window — next 30 / 60 / 90 days; specific month
  • Language — sessions in English vs. Hebrew (matters for foreign attendees)

When to use

  • "What conferences are coming up in Israel?"
  • "Any AI events in Tel Aviv next month?"
  • "Find me biomed conferences in Israel in Q3."
  • "כנסי הייטק בישראל"
  • "Tech meetups Israel May 2026"
  • "Are there any marketing summits in Tel Aviv soon?"

Notes

  • events.co.il and icx.co.il are Hebrew-first — translate event titles to English in the final summary unless the user asked in Hebrew.
  • conferenceindex.org is global; many of its "Israel" listings are call-for-papers far in advance — flag dates clearly.
  • ivc-online.com skews to paid VC events — useful for startup/investor scene, less so for general professional development.
  • Some sites (icx.co.il in particular) gate full event detail behind a click-through; the listing page still gives name + date + city, which is usually enough.
  • Do not persist or cache results — event listings change daily.

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.