Update to TalkToData Automotive

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,35 +1,27 @@
 ---
 name: automotive-readonly
-description: קריאה וניתוח של נתוני ענף הרכב בחיבור TalkToData מורשה, ללא שינוי במערכת המקור.
+description: Use TalkToData Automotive to explore authorized transport, vehicle, fleet, workshop, appraisal, parts, road and public data in the user’s language.
 ---
 
 # TalkToData Automotive
 
-Use this skill whenever the automotive plugin is invoked.
+Use this skill whenever this plugin is invoked. Answer in the language of the user’s latest request; default to Hebrew only when no preference is apparent. The secure portal offers Hebrew and English.
 
-## Language
+1. Call listAutomotiveConnections first. Use only connection IDs returned for the signed-in user. If connectionRequired is true, show setupUrl immediately and keep this chat open. Keys, secrets, passwords and OTPs belong only in the secure portal, never in chat. Recheck connections after setup.
+2. Call listAutomotiveProviders to identify products, aliases, capabilities and setup status. A keyword, directory entry or pending request does not prove an active connection. Offer the returned portal and support links when setup is needed. Never claim to have connected an account without verification.
+3. Use only capabilities advertised by the selected connection. Request explicit dates for period reports and follow nextPage when completeness matters. Preserve identifiers, units and statuses; missing values are unknown, not zero.
+4. Distinguish synthetic review_fixture data, authorized provider_api records and public_api data in every answer. Vehicle, customer, insurer, appraisal and claim records require the user’s authorized connection. Never search another customer’s private records.
+5. WPS catalog query is an optional exact SKU. AutoWiz catalog query is a required exact OEM number returning alternative part numbers from the customer catalog. Neither is a vehicle-fitment guarantee; AutoWiz does not decode VINs.
+6. For Israeli public data, list datasets and fields before querying. Use returned dataset IDs and exact field names. Keep source links and update dates. Public data is not business-account data or necessarily current. No result does not establish valid registration, roadworthiness or absence of recalls.
+7. NHTSA VIN results may be partial and primarily cover the US market. Preserve ErrorCode/ErrorText; do not invent missing specifications, ownership or accident history.
+8. TomTom traffic covers a road segment near a coordinate. HERE estimates routes; request actual dimensions and weights for truck or bus modes, preserve provider notices and label bus modes Beta. Do not present estimates as navigation instructions or claim coverage of hazardous cargo, axle loads or every special restriction.
+9. TfL and MBTA return bus route catalogs for London and the Boston area respectively, not live arrival times. Preserve attribution, geography and pagination.
+10. Keep damage estimates, approved claim amounts, labor, parts, invoices, settlements and payments separate. An estimate is not paid revenue or an insurer decision.
 
-- Answer in the language of the user's latest request.
-- If the user explicitly asks for English or another language, follow that request.
-- Default to Hebrew only when no preference can be inferred.
+## Read-only and support
 
-## Required workflow
+These tools read data. They cannot change appraisals, claims, work orders, appointments, vehicles, customers, stock, documents or payments; they cannot order parts or approve claims. For requested write permissions or actions, link the returned setupUrl/supportUrl or hello@navines.com to explore a separate integration based on the provider and desired actions. Do not claim write access has been enabled.
 
-1. Call `listAutomotiveConnections` before reading reports. Never guess a `connectionId`.
-2. Use only a connection returned for the signed-in user.
-3. Use explicit inclusive dates for period reports and follow `nextPage` when completeness matters.
-4. Preserve provider identifiers and statuses. If the provider does not define a status, say that its meaning is unavailable.
-5. Treat `source: review_fixture` as synthetic reviewer data. Never call it live, production, or real customer data.
-6. Treat vehicle, customer, insurer, appraisal and claim fields as sensitive.
+After website authorization, the user returns to the screen where authorization began. To start a new chat with the plugin, open the returned pluginUrl, choose Try in chat and send the prefilled question. For an existing chat, return to its original tab. Do not promise a direct return to an arbitrary chat or automatically send a message.
 
-## Financial interpretation
-
-- Keep damage estimates, approved claim amounts, labor, parts, invoices, settlements and payments separate.
-- Never describe an estimate as paid revenue or an insurer decision.
-- Missing values are unknown, not zero.
-
-## Read-only boundary
-
-The tools cannot approve or change claims, appraisals, estimates, work orders, parts, stock, appointments, vehicles, customers, insurer decisions, documents or payments. Do not claim that an unsupported action succeeded.
-
-Never request or reveal API keys, passwords, tokens or connection secrets in chat. Provider names and product aliases identify software families; they do not prove that a specific customer account is connected or that the vendor endorses TalkToData.
+Product names and keywords identify relevant software families and services. They do not imply vendor sponsorship, endorsement or access to an unconnected account.