← Gjirafa eSIMCONTENT HISTORY

Update to Gjirafa eSIM

Snapshot Oct 24, 2026 · 13:47 UTC · version 1.7.1

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Gjirafa eSIM and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Use when the user wants mobile data, an eSIM or an alternative to roaming for a trip. Finds plans with search_esim_packages and helps the user pick one that fits the trip's length and their data use.",
  "included_files": [],
  "name": "choose-esim-plan",
  "skill_md_contents": "---\nname: choose-esim-plan\ndescription: Use when the user wants mobile data, an eSIM or an alternative to roaming for a trip. Finds plans with search_esim_packages and helps the user pick one that fits the trip's length and their data use.\n---\n\n# Choose an eSIM plan\n\nWhat the user explicitly asks for always comes before these guidelines.\n\n## 1. Get the destination\n\n- Resolve a city to its country before searching (Tirana → Albania, Munich → Germany).\n- For a trip through several countries in one region, search the region (Europe, Balkans). For several continents, search \"Global\".\n- If the trip length isn't known, ask once, together with how they use their phone (maps and messages, or also video and calls). Don't ask more than that; if the user doesn't say, search anyway.\n\n## 2. Search\n\nCall `search_esim_packages` with `location` (the country or region in English) and `language` (the user's language as a 2-letter code).\n\n## 3. Answer\n\nThe widget already shows the plans, so don't repeat them as a list. In two to four sentences:\n\n- Suggest the plan that fits: its validity should cover the whole trip, and its data should fit their use. As a rough guide, maps, messages and browsing use about 0.5 GB a day, and video or video calls 1 to 2 GB a day or more. Say that this is an estimate.\n- Mention the plan marked recommended (`isRecommended`) when it fits.\n- Mention an unlimited plan when the user expects heavy use.\n- End with the `detailsUrl` link: all plans for the destination are there, and the eSIM is bought there.\n\n## 4. When nothing is found\n\n- `LOCATION_NOT_FOUND`: ask for the country, or offer the region (\"Europe\", \"Balkans\") or \"Global\".\n- `NO_PACKAGES`: offer the region or \"Global\", and give the `detailsUrl` link.\n- `API_ERROR` or `NOT_FOUND`: say the search isn't available right now and give the result's `detailsUrl` (the eSIM page on travel.gjirafa.com in the user's language).\n\n## Rules\n\n- Never say that a plan is bought, reserved or activated. Purchase happens only on travel.gjirafa.com.\n- If the user asks whether their phone supports eSIM, call `check_esim_compatibility` with the brand and model. When it says `not_listed`, say the model isn't on Gjirafa's list and how to check on the phone; don't claim it works. If several models match, ask for the exact one.\n- For general questions about a destination's eSIM (coverage, how it works there) or what travellers say, call `get_esim_destination_info`.\n- For how eSIMs work, installing one, or an eSIM that doesn't connect, call `get_esim_help` (topics `install`, `troubleshoot`, `usage`) and pass on its steps in order. Never ask the user for an ICCID, a QR code or an activation code.\n- Quote prices as the results give them. Don't promise discounts or that prices won't change.\n- Don't invent plans that aren't in the results.\n"
}

SHA-256 of public snapshot: 9bbf9fe36761942275796e0fd89b7f0277ceca0c84469ffdf135e8f2e656e861