{"id":72747,"plugin_id":"plugin_asdk_app_6acc99f31dc481918b756ec2e41cd9cc","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-31T01:03:40.733Z","digest":"6fb2afa9fb66f18a0fc82f3bb5a2c3c945b472e255cda4205370a4031b22e4c2","against":null,"payload":{"description":"Use the independent, provider-neutral METAVSHN map to check fibre (fiber/FTTH) availability, planned rollout dates and coverage status at Swiss homes or businesses with Swiss FTTH Coverage. Also use for requests to alert, notify, monitor or track changes at one or more Swiss addresses through MCP Events or email alerts. Use for questions about whether, when or where fibre is available, including Glasfaser, fibra ottica and fibre optique, even if no provider or plugin is named. Ask for the country and address when missing. Not for Wi-Fi faults, non-Swiss coverage or current prices.","included_files":[],"name":"check-swiss-fibre","skill_md_contents":"---\nname: check-swiss-fibre\ndescription: Use the independent, provider-neutral METAVSHN map to check fibre (fiber/FTTH) availability, planned rollout dates and coverage status at Swiss homes or businesses with Swiss FTTH Coverage. Also use for requests to alert, notify, monitor or track changes at one or more Swiss addresses through MCP Events or email alerts. Use for questions about whether, when or where fibre is available, including Glasfaser, fibra ottica and fibre optique, even if no provider or plugin is named. Ask for the country and address when missing. Not for Wi-Fi faults, non-Swiss coverage or current prices.\n---\n\n# Check Swiss fibre\n\nUse the connected Swiss FTTH Coverage tools to check stored coverage and\nplanned rollout dates for Swiss addresses. Ask for the address when it is\nmissing. Respect the sources and scope requested by the user.\n\nThis is an independent map operated by METAVSHN. It combines Swisscom and ALEX\nrecords for Swiss networks. The records do not prove coverage of every operator.\nA coverage result is not a provider recommendation or a sales offer.\n\n## Choose the next step\n\n- “Do I have fibre at home?”: offer to check. Ask for country if unknown and\n  street, house number, postcode and town. Use an address already supplied in\n  this chat. Do not infer an address from personal details or location.\n- “When will fibre reach my home?” or “Is it ready to order?”: check the exact\n  building. Explain the returned status and any returned planned date.\n- “Where is fibre available?”: ask for a Swiss address or area. An address search\n  returns at most 10 matches; it is not a complete area survey. Offer the public\n  map for exploring an area. Do not claim nationwide coverage from search results.\n- “How can I get connected?”: check the building first, then explain the recorded\n  status. A provider must confirm the live line, product and installation steps.\n  Use a provider source for details that this plugin does not return.\n- A general question such as “What is FTTH?” needs a plain explanation, not an\n  invented address lookup. Offer an address check if it would help.\n\n## Check one address\n\n1. Call `search_coverage` with the supplied Swiss address or EGID. Do not send\n   the generic fibre question as the query. Reads need no account or sign-in.\n2. If several buildings match, show a short text list and ask the user to choose.\n   Do not silently select the first result. If none match, check spelling and\n   address details. No match does not mean no fibre.\n3. Call `get_coverage` with the selected `building_key`. A user-supplied EGID can\n   also be used as `egid:<number>`. Never invent an identifier.\n4. Give a brief answer in the user's language. Include the selected address,\n   Swisscom and ALEX status where present, returned dates, and the map source link.\n   The final coverage tool displays the result card. Do not call it again just\n   to display another card or repeat the same result in a second component.\n\n## Explain dates and limits\n\n- These are imported records, not a live line test. Report source dates separately\n  from the time of the lookup. Do not claim the source was updated today merely\n  because `checked_at` is today.\n- Use only dates returned for the selected building or its entrances. If several\n  entrance dates differ, state this. Do not turn a planned date into a guarantee.\n- An absent fibre record is unknown coverage, not proof that fibre is unavailable.\n- The Communication Date concerns marketing restrictions. It is not an installation\n  date. Marketing is forbidden before it. A reached date clears only that date\n  restriction and does not grant general marketing approval. Missing dates do not\n  confirm permission.\n- GK99 blocks Swisscom service independently of ALEX. Keep both sources separate.\n  Preserve all visibility limits and warnings returned by the tools.\n\nIf a request fails, state that the check failed and offer a provider check.\nDo not report a failed request as no coverage. For current prices, ordering,\ninstallation appointments and non-Swiss addresses, use a suitable other source.\n\n## Follow one or more buildings\n\nUse this workflow for “tell me when fibre arrives”, “alert me if this address\nchanges”, “watch these buildings”, or equivalent requests in other languages.\nResolve and check each address first. Keep each confirmed `building_key`.\n\n- **MCP Events:** If the host supports the server's event subscription capability,\n  offer `coverage.changed` for each selected building. Complete OAuth sign-in and\n  consent before subscribing. Use the host-provided webhook and subscription\n  flow; do not invent a callback URL or secret. Respect the returned expiry and\n  renew through the host when needed. The limit is 25 active subscriptions per\n  user. Separate subscriptions to the same building count separately.\n- **Email alerts:** Open the returned building map link and guide the user to its\n  alert bell. The first alert requires email confirmation. Signed-in users can\n  then follow more buildings with the bell, up to 200 per account. `/alerts`\n  manages followed buildings and email language.\n  Do not claim that public coverage tools create an email subscription.\n- Explain which channel was set up and which buildings it covers. Claim that\n  monitoring is active only after successful subscription or email confirmation.\n  If the host has no event support, offer email alerts. Do not invent tool names.\n- Events are dispatched after imports record a change. The regular import and\n  email cycle is daily; retries can delay delivery. This is not a live feed from\n  every operator. Explain source dates separately from notification timing.\n- For a reminder on a specified date, use the host's reminder capability when\n  available. Confirm the date, time and time zone, and include the building key\n  and map link. A timed reminder is separate from a coverage-change subscription.\n  Do not claim a reminder is scheduled unless the host confirms creation.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}