openmates 0.21.0-alpha.7 → 0.21.0-alpha.9

package/dist/{chunk-3PJYPJJQ.js → chunk-6FM33AJ3.js}

@@ -19614,7 +19614,7 @@ Note: The 'id' field is auto-generated if not provided.
               "relevance_criteria": {
                 "type": "string",
                 "maxLength": 1e3,
-                "description": "Optional concise natural-language event-selection purpose used for relevance ranking. Include it whenever the user states a material goal such as networking, promoting a product, finding potential users, or future speaking opportunities; omit it for a plain event search and never invent preferences. When present, the skill ranks a bounded pool of up to 40 candidates (or the larger requested count) and still returns only count events.\n"
+                "description": "Optional concise natural-language event-ranking goal, separate from the event query. Set it whenever the user states a purpose, intended audience, networking goal, desired activity, or preference such as promoting a product or finding a future speaking opportunity. Omit only for a neutral event search fully expressed by query and structured fields; never invent preferences. When present, up to 40 candidates (or the larger requested count) are ranked and only count are returned.\n"
               },
               "provider": {
                 "type": "string",
@@ -19899,7 +19899,7 @@ Note: The 'id' field is auto-generated if not provided.
     "app_namespace_py": "fitness",
     "skill_method_py": "search_locations",
     "description_key": "fitness.search_locations.description",
-    "description": "Search Urban Sports Club public fitness locations. Use this when the user asks for gyms, studios, pools, or Urban Sports locations near a city, address, or radius. Do not use it for class availability; use fitness.search_classes for dated class searches. When the user states a material purpose or preference that should change venue ordering, include a concise, faithful relevance_criteria value. Keep city, radius, plan, and category constraints structured. A plain venue search may omit it; never",
+    "description": "Search Urban Sports Club public fitness locations. Use this when the user asks for gyms, studios, pools, or Urban Sports locations near a city, address, or radius. Do not use it for class availability; use fitness.search_classes for dated class searches. Keep query focused on the activity or venue type. Whenever the user states a fitness purpose, intended activity, accessibility need, desired quality, or preference that should change venue ordering, put it in relevance_criteria even if related w",
     "schema": {
       "type": "object",
       "properties": {
@@ -19941,7 +19941,7 @@ Note: The 'id' field is auto-generated if not provided.
               "relevance_criteria": {
                 "type": "string",
                 "maxLength": 1e3,
-                "description": "Optional natural-language activity goal used only to rank matching fitness locations. Omit for distance-first provider ordering; structured city, radius, plan, and category filters remain authoritative."
+                "description": 'Optional concise natural-language venue-ranking goal, separate from the activity query. Set it whenever the user states a fitness purpose, intended activity, accessibility need, desired quality, or preference that should change ordering. Example: "Broad yoga variety with explicit central-Berlin evidence." Omit only for a neutral search fully expressed by query and structured fields.\n'
               }
             }
           },
@@ -19958,7 +19958,7 @@ Note: The 'id' field is auto-generated if not provided.
     "app_namespace_py": "fitness",
     "skill_method_py": "search_classes",
     "description_key": "fitness.search_classes.description",
-    "description": "Search available Urban Sports Club public fitness classes. Use this when the user asks for dated fitness classes, course availability, free spots, on-site classes, online classes, or plan-filtered Urban Sports classes. Omit plan unless the user explicitly asks for Essential, Classic, Premium, or Max. When the user states a material purpose or preference that should change class ordering, include a concise, faithful relevance_criteria value. Keep date, location, radius, plan, attendance mode, min",
+    "description": "Search available Urban Sports Club public fitness classes. Use this when the user asks for dated fitness classes, course availability, free spots, on-site classes, online classes, or plan-filtered Urban Sports classes. Omit plan unless the user explicitly asks for Essential, Classic, Premium, or Max. Keep query focused on the activity. Whenever the user states a fitness purpose, intended activity, audience level, desired quality, or preference that should change class ordering, put it in relevan",
     "schema": {
       "type": "object",
       "properties": {
@@ -20018,7 +20018,7 @@ Note: The 'id' field is auto-generated if not provided.
               "relevance_criteria": {
                 "type": "string",
                 "maxLength": 1e3,
-                "description": "Optional natural-language activity goal used only to rank matching fitness classes. Omit for chronological provider ordering; structured date, location, radius, plan, attendance, spots, category, and venue filters remain authoritative."
+                "description": 'Optional concise natural-language class-ranking goal, separate from the activity query. Set it whenever the user states a fitness purpose, intended activity, audience level, desired quality, or preference that should change ordering. Example: "Evening on-site yoga classes with explicit remaining spots." Omit only for a neutral search fully expressed by query and structured fields.\n'
               }
             }
           },
@@ -20142,7 +20142,7 @@ Note: The 'id' field is auto-generated if not provided.
     "app_namespace_py": "home",
     "skill_method_py": "search",
     "description_key": "app_skills.home.search.description",
-    "description": "Search for apartments, houses, and WG rooms in German cities. Searches ImmoScout24, Kleinanzeigen, and WG-Gesucht simultaneously. Returns listings with prices, sizes, rooms, addresses, and direct links. Costs 10 credits per search. Use when user asks about finding housing in Germany. When the user states a material preference not fully captured by the structured price, room, size, property-type, or sort fields, include a concise, faithful relevance_criteria value without waiting for the user to",
+    "description": "Search for apartments, houses, and WG rooms in German cities. Searches ImmoScout24, Kleinanzeigen, and WG-Gesucht simultaneously. Returns listings with prices, sizes, rooms, addresses, and direct links. Costs 10 credits per search. Use when user asks about finding housing in Germany. Keep query focused on the location. Whenever the user states an intended use, household need, desired quality, or preference not fully captured by price, room, size, property-type, or sort fields, put it in relevanc",
     "schema": {
       "type": "object",
       "properties": {
@@ -20213,7 +20213,7 @@ Note: The 'id' field is auto-generated if not provided.
               "relevance_criteria": {
                 "type": "string",
                 "maxLength": 1e3,
-                "description": "Optional concise natural-language housing preference for relevance ranking. Include it when the user states a material preference not fully represented by structured filters; omit it for a plain search. Rank only explicit listing facts and never infer unstated amenities, commute, lease, accessibility, or neighborhood qualities. The internal candidate pool is bounded and only max_results listings are returned.\n"
+                "description": 'Optional concise natural-language housing-ranking goal, separate from the location query. Set it whenever the user states an intended use, household need, desired quality, or preference not represented by structured filters. Example: "Prioritize explicit balcony and quiet-setting evidence." Omit only for a neutral search fully expressed by query and structured fields. Rank only explicit listing facts and never infer unstated qualities. Only max_results listings are returned.\n'
               },
               "max_results": {
                 "type": "integer",
@@ -20668,7 +20668,7 @@ Each object must contain 'prompt' (description of the image).
     "app_namespace_py": "maps",
     "skill_method_py": "search",
     "description_key": "maps.search.description",
-    "description": "Search for places, businesses, restaurants, directions, and locations. When the user's request states a material purpose or preference that should change which matching places rank first, include a concise, faithful relevance_criteria value without waiting for the user to name the field. Keep location, place type, rating, open-now, price, and required amenity constraints in their structured fields. A plain place search may omit relevance_criteria; never invent quietness, ambience, accessibility,",
+    "description": 'Search for places, businesses, restaurants, directions, and locations. Keep query focused on the place type and location. Whenever the user states a purpose, intended activity, audience, or preference that should change place ordering, put it in relevance_criteria even if related words could also be added to query. Example: query "cafes in Berlin" with relevance_criteria "Places suitable for working several hours on a laptop and taking a client call." Keep rating, open-now, price, and required a',
     "schema": {
       "type": "object",
       "properties": {
@@ -20698,7 +20698,7 @@ Note: The 'id' field is auto-generated if not provided - you don't need to inclu
               "relevance_criteria": {
                 "type": "string",
                 "maxLength": 1e3,
-                "description": "Optional natural-language goal used only to rank matching place candidates. Omit for ordinary provider ordering; structured place, rating, open-now, price, location, and amenity filters remain authoritative."
+                "description": 'Optional concise natural-language place-ranking goal, separate from the place and location query. Set it whenever the user states a purpose, intended activity, audience, or preference that should change ordering. Example: "Suitable for working several hours on a laptop and taking a client call." Omit only for a neutral search fully expressed by query and structured fields; never invent preferences.\n'
               },
               "languageCode": {
                 "type": "string",
@@ -21053,7 +21053,7 @@ Note: The 'id' field is auto-generated if not provided - you don't need to inclu
     "app_namespace_py": "news",
     "skill_method_py": "search",
     "description_key": "news.search.description",
-    "description": "Search for news articles, current events, headlines, and announcements. When the user states a material purpose or preference that should change which coverage is most useful, include a concise, faithful relevance_criteria value. Do not wait for the user to name the field, but omit it for a plain news search and never invent preferences.",
+    "description": 'Search for news articles, current events, headlines, and announcements. Keep query focused on the news topic. Whenever the user states a purpose, audience, decision need, impact of interest, or coverage preference that should change ordering, put it in relevance_criteria even if related terms could also be added to query. Example: query "EU AI regulation" with relevance_criteria "Changes most likely to affect small EU software startups." Omit relevance_criteria only for a neutral news search ful',
     "schema": {
       "type": "object",
       "properties": {
@@ -21083,7 +21083,7 @@ Note: The 'id' field is auto-generated if not provided - you don't need to inclu
               "relevance_criteria": {
                 "type": "string",
                 "maxLength": 1e3,
-                "description": "Optional concise natural-language purpose or preference for relevance ranking. Include it when the user states a material goal that should change ordering; omit it for a plain search and never invent preferences. When present, the skill ranks up to 40 candidates and still returns only count results.\n"
+                "description": 'Optional concise natural-language coverage-ranking goal, separate from the news query. Set it whenever the user states a purpose, audience, decision need, impact of interest, or coverage preference that should change ordering. Example: "Changes most likely to affect small EU software startups." Omit only for a neutral search fully expressed by query and structured fields; never invent preferences. When present, up to 40 candidates are ranked and only count are returned.\n'
               },
               "country": {
                 "type": "string",
@@ -21893,7 +21893,7 @@ Note: The 'id' field is auto-generated if not provided - you don't need to inclu
     "app_namespace_py": "shopping",
     "skill_method_py": "search_products",
     "description_key": "app_skills.shopping.search_products.description",
-    "description": "Search products on REWE, Amazon, or Stoffe.de with real-time prices. Use category to route groceries, marketplace products, fabrics, sewing supplies, and patterns to compatible providers. Invalid provider/category combinations are rejected. When the user states a material use case or preference that should change product ordering, include a concise, faithful relevance_criteria value. Keep provider, category, country, department, price, fulfilment, and sort constraints structured. A plain product",
+    "description": "Search products on REWE, Amazon, or Stoffe.de with real-time prices. Use category to route groceries, marketplace products, fabrics, sewing supplies, and patterns to compatible providers. Invalid provider/category combinations are rejected. Keep query focused on the product type. Whenever the user states an intended use, audience, compatibility need, desired quality, or preference that should change ordering, put it in relevance_criteria even if related words could also be added to query. Exampl",
     "schema": {
       "type": "object",
       "properties": {
@@ -21953,7 +21953,7 @@ Note: The 'id' field is auto-generated if not provided - you don't need to inclu
               "relevance_criteria": {
                 "type": "string",
                 "maxLength": 1e3,
-                "description": "Optional natural-language purchase goal used only to rank matching product candidates. Omit for ordinary provider ordering; structured provider, category, price, country, department, fulfilment, and sort fields remain authoritative."
+                "description": 'Optional concise natural-language product-ranking goal, separate from the product query. Set it whenever the user states an intended use, audience, compatibility need, desired quality, or preference that should change ordering. Example: "Good for travel, with explicit quiet-click, long-battery, and multi-device evidence." Omit only for a neutral search fully expressed by query and structured fields.\n'
               },
               "sort": {
                 "type": "string",
@@ -22647,7 +22647,7 @@ Note: The 'id' field is auto-generated if not provided - you don't need to inclu
     "app_namespace_py": "travel",
     "skill_method_py": "search_stays",
     "description_key": "app_skills.travel.search_stays.description",
-    "description": "Search hotels, hostels, and other stays for explicit dates and party size. When the user states a material stay purpose or preference that should change which valid properties rank first, include a concise, faithful relevance_criteria value. Keep dates, guests, currency, price, hotel class, rating, free cancellation, and sort constraints in their structured fields. A plain stay search may omit relevance_criteria; never invent budget, amenities, neighborhood, quietness, accessibility, workspace,",
+    "description": 'Search hotels, hostels, and other stays for explicit dates and party size. Keep query focused on destination or property. Whenever the user states a trip purpose, intended activity, traveler need, desired quality, or preference that should change ordering, put it in relevance_criteria even if related words could also be added to query. Example: "Prioritize explicit reliable-Wi-Fi and in-room workspace or desk evidence." Keep dates, guests, price, class, rating, cancellation, and sort structured.',
     "schema": {
       "type": "object",
       "properties": {
@@ -22703,13 +22703,15 @@ Note: The 'id' field is auto-generated if not provided - you don't need to inclu
               },
               "max_results": {
                 "type": "integer",
-                "description": "Maximum number of results to return.",
+                "description": "Maximum number of results to return (1-20, default 10).",
+                "minimum": 1,
+                "maximum": 20,
                 "default": 10
               },
               "relevance_criteria": {
                 "type": "string",
                 "maxLength": 1e3,
-                "description": "Optional natural-language stay goal used only to rank matching first-page properties. Omit for ordinary provider ordering; structured date, party-size, price, class, rating, cancellation, and sort filters remain authoritative."
+                "description": 'Optional concise natural-language stay-ranking goal, separate from the destination query. Set it whenever the user states a trip purpose, intended activity, traveler need, desired quality, or preference that should change ordering. Example: "Prioritize explicit reliable-Wi-Fi and workspace or desk evidence." Omit only for a neutral search fully expressed by query and structured fields; never invent preferences.\n'
               }
             },
             "required": [
@@ -22920,7 +22922,7 @@ Note: The 'id' field is auto-generated if not provided - you don't need to inclu
     "app_namespace_py": "videos",
     "skill_method_py": "search",
     "description_key": "videos.search.description",
-    "description": "Search for videos, documentaries, tutorials, and clips on the web. When the user states a material viewing purpose or preference that should change ordering, such as audience level, desired depth, format, duration, authority, or freshness, include a concise, faithful relevance_criteria value. Keep country, language, safe-search, freshness, and count constraints structured. A plain video search may omit relevance_criteria; never invent experience level, recency, duration, creator, popularity, or",
+    "description": 'Search for videos, documentaries, tutorials, and clips on the web. Keep query focused on the topic. Whenever the user states a viewing or learning purpose, audience level, desired depth, format, authority, or other preference that should change ordering, put it in relevance_criteria even if related words could also be added to query. Example: query "RAG tutorial" with relevance_criteria "Advanced, hands-on production guidance with deployment and evaluation details." Keep country, language, safe-',
     "schema": {
       "type": "object",
       "properties": {
@@ -22950,7 +22952,7 @@ Note: The 'id' field is auto-generated if not provided - you don't need to inclu
               "relevance_criteria": {
                 "type": "string",
                 "maxLength": 1e3,
-                "description": "Optional natural-language viewing or learning goal used only to rank matching video candidates. Omit for ordinary popularity ordering; structured country, language, safe-search, freshness, and count fields remain authoritative."
+                "description": 'Optional concise natural-language video-ranking goal, separate from the topic query. Set it whenever the user states a viewing or learning purpose, audience level, desired depth, format, authority, or preference that should change ordering. Example: "Advanced, hands-on production guidance with deployment and evaluation details." Omit only for a neutral search fully expressed by query and structured fields.\n'
               },
               "country": {
                 "type": "string",
@@ -23640,7 +23642,7 @@ Note: The 'id' field is auto-generated if not provided - you don't need to inclu
     "app_namespace_py": "web",
     "skill_method_py": "search",
     "description_key": "app_skills.web.search.description",
-    "description": "General web search for current information, prices, weather, facts, stocks, sports scores, etc. Use as a fallback when no specialized skill applies. When the user states a material purpose or preference that should change which results are most useful, include a concise, faithful relevance_criteria value (for example, research suitable for a purchase decision). Do not wait for the user to name the field, but omit it for a plain search and never invent preferences.",
+    "description": 'General web search for current information, prices, weather, facts, stocks, sports scores, etc. Use as a fallback when no specialized skill applies. Keep query focused on the subject being retrieved. Whenever the user states a purpose, intended use, audience, decision need, or preference that should change result ordering, put that goal in relevance_criteria even if related words could also be added to query. For example, query "laptop-friendly cafes Berlin" with relevance_criteria "Places suita',
     "schema": {
       "type": "object",
       "properties": {
@@ -23670,7 +23672,7 @@ Note: The 'id' field is auto-generated if not provided - you don't need to inclu
               "relevance_criteria": {
                 "type": "string",
                 "maxLength": 1e3,
-                "description": "Optional concise natural-language purpose or preference for relevance ranking. Include it when the user states a material goal that should change ordering; omit it for a plain search and never invent preferences. When present, the skill ranks up to 40 candidates and still returns only count results.\n"
+                "description": 'Optional concise natural-language ranking goal, separate from the retrieval query. Set it whenever the user states a purpose, intended use, audience, decision need, or preference that should change ordering, even if related terms also appear in query. Example: "Research useful for deciding which framework to adopt." Omit only for a neutral search fully expressed by query and structured fields; never invent preferences. When present, up to 40 candidates are ranked and only count are returned.\n'
               },
               "country": {
                 "type": "string",
@@ -24104,7 +24106,7 @@ var FitnessAppSkills = class {
     this.runSkill = runSkill;
   }
   /**
-   * Search available Urban Sports Club public fitness classes. Use this when the user asks for dated fitness classes, course availability, free spots, on-site classes, online classes, or plan-filtered Urban Sports classes. Omit plan unless the user explicitly asks for Essential, Classic, Premium, or Max. When the user states a material purpose or preference that should change class ordering, include a concise, faithful relevance_criteria value. Keep date, location, radius, plan, attendance mode, min
+   * Search available Urban Sports Club public fitness classes. Use this when the user asks for dated fitness classes, course availability, free spots, on-site classes, online classes, or plan-filtered Urban Sports classes. Omit plan unless the user explicitly asks for Essential, Classic, Premium, or Max. Keep query focused on the activity. Whenever the user states a fitness purpose, intended activity, audience level, desired quality, or preference that should change class ordering, put it in relevan
    * Description key: fitness.search_classes.description
    * Skill: fitness/search_classes
    */
@@ -24112,7 +24114,7 @@ var FitnessAppSkills = class {
     return this.runSkill("fitness", "search_classes", input, options);
   }
   /**
-   * Search Urban Sports Club public fitness locations. Use this when the user asks for gyms, studios, pools, or Urban Sports locations near a city, address, or radius. Do not use it for class availability; use fitness.search_classes for dated class searches. When the user states a material purpose or preference that should change venue ordering, include a concise, faithful relevance_criteria value. Keep city, radius, plan, and category constraints structured. A plain venue search may omit it; never
+   * Search Urban Sports Club public fitness locations. Use this when the user asks for gyms, studios, pools, or Urban Sports locations near a city, address, or radius. Do not use it for class availability; use fitness.search_classes for dated class searches. Keep query focused on the activity or venue type. Whenever the user states a fitness purpose, intended activity, accessibility need, desired quality, or preference that should change venue ordering, put it in relevance_criteria even if related w
    * Description key: fitness.search_locations.description
    * Skill: fitness/search_locations
    */
@@ -24148,7 +24150,7 @@ var HomeAppSkills = class {
     this.runSkill = runSkill;
   }
   /**
-   * Search for apartments, houses, and WG rooms in German cities. Searches ImmoScout24, Kleinanzeigen, and WG-Gesucht simultaneously. Returns listings with prices, sizes, rooms, addresses, and direct links. Costs 10 credits per search. Use when user asks about finding housing in Germany. When the user states a material preference not fully captured by the structured price, room, size, property-type, or sort fields, include a concise, faithful relevance_criteria value without waiting for the user to
+   * Search for apartments, houses, and WG rooms in German cities. Searches ImmoScout24, Kleinanzeigen, and WG-Gesucht simultaneously. Returns listings with prices, sizes, rooms, addresses, and direct links. Costs 10 credits per search. Use when user asks about finding housing in Germany. Keep query focused on the location. Whenever the user states an intended use, household need, desired quality, or preference not fully captured by price, room, size, property-type, or sort fields, put it in relevanc
    * Description key: app_skills.home.search.description
    * Skill: home/search
    */
@@ -24198,7 +24200,7 @@ var MapsAppSkills = class {
     this.runSkill = runSkill;
   }
   /**
-   * Search for places, businesses, restaurants, directions, and locations. When the user's request states a material purpose or preference that should change which matching places rank first, include a concise, faithful relevance_criteria value without waiting for the user to name the field. Keep location, place type, rating, open-now, price, and required amenity constraints in their structured fields. A plain place search may omit relevance_criteria; never invent quietness, ambience, accessibility,
+   * Search for places, businesses, restaurants, directions, and locations. Keep query focused on the place type and location. Whenever the user states a purpose, intended activity, audience, or preference that should change place ordering, put it in relevance_criteria even if related words could also be added to query. Example: query "cafes in Berlin" with relevance_criteria "Places suitable for working several hours on a laptop and taking a client call." Keep rating, open-now, price, and required a
    * Description key: maps.search.description
    * Skill: maps/search
    */
@@ -24254,7 +24256,7 @@ var NewsAppSkills = class {
     this.runSkill = runSkill;
   }
   /**
-   * Search for news articles, current events, headlines, and announcements. When the user states a material purpose or preference that should change which coverage is most useful, include a concise, faithful relevance_criteria value. Do not wait for the user to name the field, but omit it for a plain news search and never invent preferences.
+   * Search for news articles, current events, headlines, and announcements. Keep query focused on the news topic. Whenever the user states a purpose, audience, decision need, impact of interest, or coverage preference that should change ordering, put it in relevance_criteria even if related terms could also be added to query. Example: query "EU AI regulation" with relevance_criteria "Changes most likely to affect small EU software startups." Omit relevance_criteria only for a neutral news search ful
    * Description key: news.search.description
    * Skill: news/search
    */
@@ -24408,7 +24410,7 @@ var ShoppingAppSkills = class {
     this.runSkill = runSkill;
   }
   /**
-   * Search products on REWE, Amazon, or Stoffe.de with real-time prices. Use category to route groceries, marketplace products, fabrics, sewing supplies, and patterns to compatible providers. Invalid provider/category combinations are rejected. When the user states a material use case or preference that should change product ordering, include a concise, faithful relevance_criteria value. Keep provider, category, country, department, price, fulfilment, and sort constraints structured. A plain product
+   * Search products on REWE, Amazon, or Stoffe.de with real-time prices. Use category to route groceries, marketplace products, fabrics, sewing supplies, and patterns to compatible providers. Invalid provider/category combinations are rejected. Keep query focused on the product type. Whenever the user states an intended use, audience, compatibility need, desired quality, or preference that should change ordering, put it in relevance_criteria even if related words could also be added to query. Exampl
    * Description key: app_skills.shopping.search_products.description
    * Skill: shopping/search_products
    */
@@ -24482,7 +24484,7 @@ var TravelAppSkills = class {
     return this.runSkill("travel", "search_connections", input, options);
   }
   /**
-   * Search hotels, hostels, and other stays for explicit dates and party size. When the user states a material stay purpose or preference that should change which valid properties rank first, include a concise, faithful relevance_criteria value. Keep dates, guests, currency, price, hotel class, rating, free cancellation, and sort constraints in their structured fields. A plain stay search may omit relevance_criteria; never invent budget, amenities, neighborhood, quietness, accessibility, workspace,
+   * Search hotels, hostels, and other stays for explicit dates and party size. Keep query focused on destination or property. Whenever the user states a trip purpose, intended activity, traveler need, desired quality, or preference that should change ordering, put it in relevance_criteria even if related words could also be added to query. Example: "Prioritize explicit reliable-Wi-Fi and in-room workspace or desk evidence." Keep dates, guests, price, class, rating, cancellation, and sort structured.
    * Description key: app_skills.travel.search_stays.description
    * Skill: travel/search_stays
    */
@@ -24520,7 +24522,7 @@ var VideosAppSkills = class {
     return this.runSkill("videos", "get_transcript", input, options);
   }
   /**
-   * Search for videos, documentaries, tutorials, and clips on the web. When the user states a material viewing purpose or preference that should change ordering, such as audience level, desired depth, format, duration, authority, or freshness, include a concise, faithful relevance_criteria value. Keep country, language, safe-search, freshness, and count constraints structured. A plain video search may omit relevance_criteria; never invent experience level, recency, duration, creator, popularity, or
+   * Search for videos, documentaries, tutorials, and clips on the web. Keep query focused on the topic. Whenever the user states a viewing or learning purpose, audience level, desired depth, format, authority, or other preference that should change ordering, put it in relevance_criteria even if related words could also be added to query. Example: query "RAG tutorial" with relevance_criteria "Advanced, hands-on production guidance with deployment and evaluation details." Keep country, language, safe-
    * Description key: videos.search.description
    * Skill: videos/search
    */
@@ -24564,7 +24566,7 @@ var WebAppSkills = class {
     return this.runSkill("web", "read", input, options);
   }
   /**
-   * General web search for current information, prices, weather, facts, stocks, sports scores, etc. Use as a fallback when no specialized skill applies. When the user states a material purpose or preference that should change which results are most useful, include a concise, faithful relevance_criteria value (for example, research suitable for a purchase decision). Do not wait for the user to name the field, but omit it for a plain search and never invent preferences.
+   * General web search for current information, prices, weather, facts, stocks, sports scores, etc. Use as a fallback when no specialized skill applies. Keep query focused on the subject being retrieved. Whenever the user states a purpose, intended use, audience, decision need, or preference that should change result ordering, put that goal in relevance_criteria even if related words could also be added to query. For example, query "laptop-friendly cafes Berlin" with relevance_criteria "Places suita
    * Description key: app_skills.web.search.description
    * Skill: web/search
    */

package/dist/cli.js

@@ -19,7 +19,7 @@ import {
   serializeToYaml,
   shouldRequireTrustedAccountGuard,
   waitForWorkflowRun
-} from "./chunk-3PJYPJJQ.js";
+} from "./chunk-6FM33AJ3.js";
 import "./chunk-IWKP55ZB.js";
 import "./chunk-BBKJZ23O.js";
 export {

package/dist/index.d.ts

@@ -929,7 +929,7 @@ declare const APP_SKILL_METADATA: readonly [{
                         readonly relevance_criteria: {
                             readonly type: "string";
                             readonly maxLength: 1000;
-                            readonly description: "Optional concise natural-language event-selection purpose used for relevance ranking. Include it whenever the user states a material goal such as networking, promoting a product, finding potential users, or future speaking opportunities; omit it for a plain event search and never invent preferences. When present, the skill ranks a bounded pool of up to 40 candidates (or the larger requested count) and still returns only count events.\n";
+                            readonly description: "Optional concise natural-language event-ranking goal, separate from the event query. Set it whenever the user states a purpose, intended audience, networking goal, desired activity, or preference such as promoting a product or finding a future speaking opportunity. Omit only for a neutral event search fully expressed by query and structured fields; never invent preferences. When present, up to 40 candidates (or the larger requested count) are ranked and only count are returned.\n";
                         };
                         readonly provider: {
                             readonly type: "string";
@@ -1171,7 +1171,7 @@ declare const APP_SKILL_METADATA: readonly [{
     readonly app_namespace_py: "fitness";
     readonly skill_method_py: "search_locations";
     readonly description_key: "fitness.search_locations.description";
-    readonly description: "Search Urban Sports Club public fitness locations. Use this when the user asks for gyms, studios, pools, or Urban Sports locations near a city, address, or radius. Do not use it for class availability; use fitness.search_classes for dated class searches. When the user states a material purpose or preference that should change venue ordering, include a concise, faithful relevance_criteria value. Keep city, radius, plan, and category constraints structured. A plain venue search may omit it; never";
+    readonly description: "Search Urban Sports Club public fitness locations. Use this when the user asks for gyms, studios, pools, or Urban Sports locations near a city, address, or radius. Do not use it for class availability; use fitness.search_classes for dated class searches. Keep query focused on the activity or venue type. Whenever the user states a fitness purpose, intended activity, accessibility need, desired quality, or preference that should change venue ordering, put it in relevance_criteria even if related w";
     readonly schema: {
         readonly type: "object";
         readonly properties: {
@@ -1213,7 +1213,7 @@ declare const APP_SKILL_METADATA: readonly [{
                         readonly relevance_criteria: {
                             readonly type: "string";
                             readonly maxLength: 1000;
-                            readonly description: "Optional natural-language activity goal used only to rank matching fitness locations. Omit for distance-first provider ordering; structured city, radius, plan, and category filters remain authoritative.";
+                            readonly description: "Optional concise natural-language venue-ranking goal, separate from the activity query. Set it whenever the user states a fitness purpose, intended activity, accessibility need, desired quality, or preference that should change ordering. Example: \"Broad yoga variety with explicit central-Berlin evidence.\" Omit only for a neutral search fully expressed by query and structured fields.\n";
                         };
                     };
                 };
@@ -1229,7 +1229,7 @@ declare const APP_SKILL_METADATA: readonly [{
     readonly app_namespace_py: "fitness";
     readonly skill_method_py: "search_classes";
     readonly description_key: "fitness.search_classes.description";
-    readonly description: "Search available Urban Sports Club public fitness classes. Use this when the user asks for dated fitness classes, course availability, free spots, on-site classes, online classes, or plan-filtered Urban Sports classes. Omit plan unless the user explicitly asks for Essential, Classic, Premium, or Max. When the user states a material purpose or preference that should change class ordering, include a concise, faithful relevance_criteria value. Keep date, location, radius, plan, attendance mode, min";
+    readonly description: "Search available Urban Sports Club public fitness classes. Use this when the user asks for dated fitness classes, course availability, free spots, on-site classes, online classes, or plan-filtered Urban Sports classes. Omit plan unless the user explicitly asks for Essential, Classic, Premium, or Max. Keep query focused on the activity. Whenever the user states a fitness purpose, intended activity, audience level, desired quality, or preference that should change class ordering, put it in relevan";
     readonly schema: {
         readonly type: "object";
         readonly properties: {
@@ -1289,7 +1289,7 @@ declare const APP_SKILL_METADATA: readonly [{
                         readonly relevance_criteria: {
                             readonly type: "string";
                             readonly maxLength: 1000;
-                            readonly description: "Optional natural-language activity goal used only to rank matching fitness classes. Omit for chronological provider ordering; structured date, location, radius, plan, attendance, spots, category, and venue filters remain authoritative.";
+                            readonly description: "Optional concise natural-language class-ranking goal, separate from the activity query. Set it whenever the user states a fitness purpose, intended activity, audience level, desired quality, or preference that should change ordering. Example: \"Evening on-site yoga classes with explicit remaining spots.\" Omit only for a neutral search fully expressed by query and structured fields.\n";
                         };
                     };
                 };
@@ -1389,7 +1389,7 @@ declare const APP_SKILL_METADATA: readonly [{
     readonly app_namespace_py: "home";
     readonly skill_method_py: "search";
     readonly description_key: "app_skills.home.search.description";
-    readonly description: "Search for apartments, houses, and WG rooms in German cities. Searches ImmoScout24, Kleinanzeigen, and WG-Gesucht simultaneously. Returns listings with prices, sizes, rooms, addresses, and direct links. Costs 10 credits per search. Use when user asks about finding housing in Germany. When the user states a material preference not fully captured by the structured price, room, size, property-type, or sort fields, include a concise, faithful relevance_criteria value without waiting for the user to";
+    readonly description: "Search for apartments, houses, and WG rooms in German cities. Searches ImmoScout24, Kleinanzeigen, and WG-Gesucht simultaneously. Returns listings with prices, sizes, rooms, addresses, and direct links. Costs 10 credits per search. Use when user asks about finding housing in Germany. Keep query focused on the location. Whenever the user states an intended use, household need, desired quality, or preference not fully captured by price, room, size, property-type, or sort fields, put it in relevanc";
     readonly schema: {
         readonly type: "object";
         readonly properties: {
@@ -1447,7 +1447,7 @@ declare const APP_SKILL_METADATA: readonly [{
                         readonly relevance_criteria: {
                             readonly type: "string";
                             readonly maxLength: 1000;
-                            readonly description: "Optional concise natural-language housing preference for relevance ranking. Include it when the user states a material preference not fully represented by structured filters; omit it for a plain search. Rank only explicit listing facts and never infer unstated amenities, commute, lease, accessibility, or neighborhood qualities. The internal candidate pool is bounded and only max_results listings are returned.\n";
+                            readonly description: "Optional concise natural-language housing-ranking goal, separate from the location query. Set it whenever the user states an intended use, household need, desired quality, or preference not represented by structured filters. Example: \"Prioritize explicit balcony and quiet-setting evidence.\" Omit only for a neutral search fully expressed by query and structured fields. Rank only explicit listing facts and never infer unstated qualities. Only max_results listings are returned.\n";
                         };
                         readonly max_results: {
                             readonly type: "integer";
@@ -1830,7 +1830,7 @@ declare const APP_SKILL_METADATA: readonly [{
     readonly app_namespace_py: "maps";
     readonly skill_method_py: "search";
     readonly description_key: "maps.search.description";
-    readonly description: "Search for places, businesses, restaurants, directions, and locations. When the user's request states a material purpose or preference that should change which matching places rank first, include a concise, faithful relevance_criteria value without waiting for the user to name the field. Keep location, place type, rating, open-now, price, and required amenity constraints in their structured fields. A plain place search may omit relevance_criteria; never invent quietness, ambience, accessibility,";
+    readonly description: "Search for places, businesses, restaurants, directions, and locations. Keep query focused on the place type and location. Whenever the user states a purpose, intended activity, audience, or preference that should change place ordering, put it in relevance_criteria even if related words could also be added to query. Example: query \"cafes in Berlin\" with relevance_criteria \"Places suitable for working several hours on a laptop and taking a client call.\" Keep rating, open-now, price, and required a";
     readonly schema: {
         readonly type: "object";
         readonly properties: {
@@ -1854,7 +1854,7 @@ declare const APP_SKILL_METADATA: readonly [{
                         readonly relevance_criteria: {
                             readonly type: "string";
                             readonly maxLength: 1000;
-                            readonly description: "Optional natural-language goal used only to rank matching place candidates. Omit for ordinary provider ordering; structured place, rating, open-now, price, location, and amenity filters remain authoritative.";
+                            readonly description: "Optional concise natural-language place-ranking goal, separate from the place and location query. Set it whenever the user states a purpose, intended activity, audience, or preference that should change ordering. Example: \"Suitable for working several hours on a laptop and taking a client call.\" Omit only for a neutral search fully expressed by query and structured fields; never invent preferences.\n";
                         };
                         readonly languageCode: {
                             readonly type: "string";
@@ -2150,7 +2150,7 @@ declare const APP_SKILL_METADATA: readonly [{
     readonly app_namespace_py: "news";
     readonly skill_method_py: "search";
     readonly description_key: "news.search.description";
-    readonly description: "Search for news articles, current events, headlines, and announcements. When the user states a material purpose or preference that should change which coverage is most useful, include a concise, faithful relevance_criteria value. Do not wait for the user to name the field, but omit it for a plain news search and never invent preferences.";
+    readonly description: "Search for news articles, current events, headlines, and announcements. Keep query focused on the news topic. Whenever the user states a purpose, audience, decision need, impact of interest, or coverage preference that should change ordering, put it in relevance_criteria even if related terms could also be added to query. Example: query \"EU AI regulation\" with relevance_criteria \"Changes most likely to affect small EU software startups.\" Omit relevance_criteria only for a neutral news search ful";
     readonly schema: {
         readonly type: "object";
         readonly properties: {
@@ -2174,7 +2174,7 @@ declare const APP_SKILL_METADATA: readonly [{
                         readonly relevance_criteria: {
                             readonly type: "string";
                             readonly maxLength: 1000;
-                            readonly description: "Optional concise natural-language purpose or preference for relevance ranking. Include it when the user states a material goal that should change ordering; omit it for a plain search and never invent preferences. When present, the skill ranks up to 40 candidates and still returns only count results.\n";
+                            readonly description: "Optional concise natural-language coverage-ranking goal, separate from the news query. Set it whenever the user states a purpose, audience, decision need, impact of interest, or coverage preference that should change ordering. Example: \"Changes most likely to affect small EU software startups.\" Omit only for a neutral search fully expressed by query and structured fields; never invent preferences. When present, up to 40 candidates are ranked and only count are returned.\n";
                         };
                         readonly country: {
                             readonly type: "string";
@@ -2820,7 +2820,7 @@ declare const APP_SKILL_METADATA: readonly [{
     readonly app_namespace_py: "shopping";
     readonly skill_method_py: "search_products";
     readonly description_key: "app_skills.shopping.search_products.description";
-    readonly description: "Search products on REWE, Amazon, or Stoffe.de with real-time prices. Use category to route groceries, marketplace products, fabrics, sewing supplies, and patterns to compatible providers. Invalid provider/category combinations are rejected. When the user states a material use case or preference that should change product ordering, include a concise, faithful relevance_criteria value. Keep provider, category, country, department, price, fulfilment, and sort constraints structured. A plain product";
+    readonly description: "Search products on REWE, Amazon, or Stoffe.de with real-time prices. Use category to route groceries, marketplace products, fabrics, sewing supplies, and patterns to compatible providers. Invalid provider/category combinations are rejected. Keep query focused on the product type. Whenever the user states an intended use, audience, compatibility need, desired quality, or preference that should change ordering, put it in relevance_criteria even if related words could also be added to query. Exampl";
     readonly schema: {
         readonly type: "object";
         readonly properties: {
@@ -2854,7 +2854,7 @@ declare const APP_SKILL_METADATA: readonly [{
                         readonly relevance_criteria: {
                             readonly type: "string";
                             readonly maxLength: 1000;
-                            readonly description: "Optional natural-language purchase goal used only to rank matching product candidates. Omit for ordinary provider ordering; structured provider, category, price, country, department, fulfilment, and sort fields remain authoritative.";
+                            readonly description: "Optional concise natural-language product-ranking goal, separate from the product query. Set it whenever the user states an intended use, audience, compatibility need, desired quality, or preference that should change ordering. Example: \"Good for travel, with explicit quiet-click, long-battery, and multi-device evidence.\" Omit only for a neutral search fully expressed by query and structured fields.\n";
                         };
                         readonly sort: {
                             readonly type: "string";
@@ -3389,7 +3389,7 @@ declare const APP_SKILL_METADATA: readonly [{
     readonly app_namespace_py: "travel";
     readonly skill_method_py: "search_stays";
     readonly description_key: "app_skills.travel.search_stays.description";
-    readonly description: "Search hotels, hostels, and other stays for explicit dates and party size. When the user states a material stay purpose or preference that should change which valid properties rank first, include a concise, faithful relevance_criteria value. Keep dates, guests, currency, price, hotel class, rating, free cancellation, and sort constraints in their structured fields. A plain stay search may omit relevance_criteria; never invent budget, amenities, neighborhood, quietness, accessibility, workspace,";
+    readonly description: "Search hotels, hostels, and other stays for explicit dates and party size. Keep query focused on destination or property. Whenever the user states a trip purpose, intended activity, traveler need, desired quality, or preference that should change ordering, put it in relevance_criteria even if related words could also be added to query. Example: \"Prioritize explicit reliable-Wi-Fi and in-room workspace or desk evidence.\" Keep dates, guests, price, class, rating, cancellation, and sort structured.";
     readonly schema: {
         readonly type: "object";
         readonly properties: {
@@ -3445,13 +3445,15 @@ declare const APP_SKILL_METADATA: readonly [{
                         };
                         readonly max_results: {
                             readonly type: "integer";
-                            readonly description: "Maximum number of results to return.";
+                            readonly description: "Maximum number of results to return (1-20, default 10).";
+                            readonly minimum: 1;
+                            readonly maximum: 20;
                             readonly default: 10;
                         };
                         readonly relevance_criteria: {
                             readonly type: "string";
                             readonly maxLength: 1000;
-                            readonly description: "Optional natural-language stay goal used only to rank matching first-page properties. Omit for ordinary provider ordering; structured date, party-size, price, class, rating, cancellation, and sort filters remain authoritative.";
+                            readonly description: "Optional concise natural-language stay-ranking goal, separate from the destination query. Set it whenever the user states a trip purpose, intended activity, traveler need, desired quality, or preference that should change ordering. Example: \"Prioritize explicit reliable-Wi-Fi and workspace or desk evidence.\" Omit only for a neutral search fully expressed by query and structured fields; never invent preferences.\n";
                         };
                     };
                     readonly required: readonly ["query", "check_in_date", "check_out_date"];
@@ -3612,7 +3614,7 @@ declare const APP_SKILL_METADATA: readonly [{
     readonly app_namespace_py: "videos";
     readonly skill_method_py: "search";
     readonly description_key: "videos.search.description";
-    readonly description: "Search for videos, documentaries, tutorials, and clips on the web. When the user states a material viewing purpose or preference that should change ordering, such as audience level, desired depth, format, duration, authority, or freshness, include a concise, faithful relevance_criteria value. Keep country, language, safe-search, freshness, and count constraints structured. A plain video search may omit relevance_criteria; never invent experience level, recency, duration, creator, popularity, or";
+    readonly description: "Search for videos, documentaries, tutorials, and clips on the web. Keep query focused on the topic. Whenever the user states a viewing or learning purpose, audience level, desired depth, format, authority, or other preference that should change ordering, put it in relevance_criteria even if related words could also be added to query. Example: query \"RAG tutorial\" with relevance_criteria \"Advanced, hands-on production guidance with deployment and evaluation details.\" Keep country, language, safe-";
     readonly schema: {
         readonly type: "object";
         readonly properties: {
@@ -3636,7 +3638,7 @@ declare const APP_SKILL_METADATA: readonly [{
                         readonly relevance_criteria: {
                             readonly type: "string";
                             readonly maxLength: 1000;
-                            readonly description: "Optional natural-language viewing or learning goal used only to rank matching video candidates. Omit for ordinary popularity ordering; structured country, language, safe-search, freshness, and count fields remain authoritative.";
+                            readonly description: "Optional concise natural-language video-ranking goal, separate from the topic query. Set it whenever the user states a viewing or learning purpose, audience level, desired depth, format, authority, or preference that should change ordering. Example: \"Advanced, hands-on production guidance with deployment and evaluation details.\" Omit only for a neutral search fully expressed by query and structured fields.\n";
                         };
                         readonly country: {
                             readonly type: "string";
@@ -4135,7 +4137,7 @@ declare const APP_SKILL_METADATA: readonly [{
     readonly app_namespace_py: "web";
     readonly skill_method_py: "search";
     readonly description_key: "app_skills.web.search.description";
-    readonly description: "General web search for current information, prices, weather, facts, stocks, sports scores, etc. Use as a fallback when no specialized skill applies. When the user states a material purpose or preference that should change which results are most useful, include a concise, faithful relevance_criteria value (for example, research suitable for a purchase decision). Do not wait for the user to name the field, but omit it for a plain search and never invent preferences.";
+    readonly description: "General web search for current information, prices, weather, facts, stocks, sports scores, etc. Use as a fallback when no specialized skill applies. Keep query focused on the subject being retrieved. Whenever the user states a purpose, intended use, audience, decision need, or preference that should change result ordering, put that goal in relevance_criteria even if related words could also be added to query. For example, query \"laptop-friendly cafes Berlin\" with relevance_criteria \"Places suita";
     readonly schema: {
         readonly type: "object";
         readonly properties: {
@@ -4159,7 +4161,7 @@ declare const APP_SKILL_METADATA: readonly [{
                         readonly relevance_criteria: {
                             readonly type: "string";
                             readonly maxLength: 1000;
-                            readonly description: "Optional concise natural-language purpose or preference for relevance ranking. Include it when the user states a material goal that should change ordering; omit it for a plain search and never invent preferences. When present, the skill ranks up to 40 candidates and still returns only count results.\n";
+                            readonly description: "Optional concise natural-language ranking goal, separate from the retrieval query. Set it whenever the user states a purpose, intended use, audience, decision need, or preference that should change ordering, even if related terms also appear in query. Example: \"Research useful for deciding which framework to adopt.\" Omit only for a neutral search fully expressed by query and structured fields; never invent preferences. When present, up to 40 candidates are ranked and only count are returned.\n";
                         };
                         readonly country: {
                             readonly type: "string";
@@ -4439,13 +4441,13 @@ declare class FitnessAppSkills {
     private readonly runSkill;
     constructor(runSkill: AppSkillRunner);
     /**
-     * Search available Urban Sports Club public fitness classes. Use this when the user asks for dated fitness classes, course availability, free spots, on-site classes, online classes, or plan-filtered Urban Sports classes. Omit plan unless the user explicitly asks for Essential, Classic, Premium, or Max. When the user states a material purpose or preference that should change class ordering, include a concise, faithful relevance_criteria value. Keep date, location, radius, plan, attendance mode, min
+     * Search available Urban Sports Club public fitness classes. Use this when the user asks for dated fitness classes, course availability, free spots, on-site classes, online classes, or plan-filtered Urban Sports classes. Omit plan unless the user explicitly asks for Essential, Classic, Premium, or Max. Keep query focused on the activity. Whenever the user states a fitness purpose, intended activity, audience level, desired quality, or preference that should change class ordering, put it in relevan
      * Description key: fitness.search_classes.description
      * Skill: fitness/search_classes
      */
     searchClasses<T = unknown>(input: SkillInput, options?: AppSkillRunOptions): Promise<T>;
     /**
-     * Search Urban Sports Club public fitness locations. Use this when the user asks for gyms, studios, pools, or Urban Sports locations near a city, address, or radius. Do not use it for class availability; use fitness.search_classes for dated class searches. When the user states a material purpose or preference that should change venue ordering, include a concise, faithful relevance_criteria value. Keep city, radius, plan, and category constraints structured. A plain venue search may omit it; never
+     * Search Urban Sports Club public fitness locations. Use this when the user asks for gyms, studios, pools, or Urban Sports locations near a city, address, or radius. Do not use it for class availability; use fitness.search_classes for dated class searches. Keep query focused on the activity or venue type. Whenever the user states a fitness purpose, intended activity, accessibility need, desired quality, or preference that should change venue ordering, put it in relevance_criteria even if related w
      * Description key: fitness.search_locations.description
      * Skill: fitness/search_locations
      */
@@ -4471,7 +4473,7 @@ declare class HomeAppSkills {
     private readonly runSkill;
     constructor(runSkill: AppSkillRunner);
     /**
-     * Search for apartments, houses, and WG rooms in German cities. Searches ImmoScout24, Kleinanzeigen, and WG-Gesucht simultaneously. Returns listings with prices, sizes, rooms, addresses, and direct links. Costs 10 credits per search. Use when user asks about finding housing in Germany. When the user states a material preference not fully captured by the structured price, room, size, property-type, or sort fields, include a concise, faithful relevance_criteria value without waiting for the user to
+     * Search for apartments, houses, and WG rooms in German cities. Searches ImmoScout24, Kleinanzeigen, and WG-Gesucht simultaneously. Returns listings with prices, sizes, rooms, addresses, and direct links. Costs 10 credits per search. Use when user asks about finding housing in Germany. Keep query focused on the location. Whenever the user states an intended use, household need, desired quality, or preference not fully captured by price, room, size, property-type, or sort fields, put it in relevanc
      * Description key: app_skills.home.search.description
      * Skill: home/search
      */
@@ -4507,7 +4509,7 @@ declare class MapsAppSkills {
     private readonly runSkill;
     constructor(runSkill: AppSkillRunner);
     /**
-     * Search for places, businesses, restaurants, directions, and locations. When the user's request states a material purpose or preference that should change which matching places rank first, include a concise, faithful relevance_criteria value without waiting for the user to name the field. Keep location, place type, rating, open-now, price, and required amenity constraints in their structured fields. A plain place search may omit relevance_criteria; never invent quietness, ambience, accessibility,
+     * Search for places, businesses, restaurants, directions, and locations. Keep query focused on the place type and location. Whenever the user states a purpose, intended activity, audience, or preference that should change place ordering, put it in relevance_criteria even if related words could also be added to query. Example: query "cafes in Berlin" with relevance_criteria "Places suitable for working several hours on a laptop and taking a client call." Keep rating, open-now, price, and required a
      * Description key: maps.search.description
      * Skill: maps/search
      */
@@ -4547,7 +4549,7 @@ declare class NewsAppSkills {
     private readonly runSkill;
     constructor(runSkill: AppSkillRunner);
     /**
-     * Search for news articles, current events, headlines, and announcements. When the user states a material purpose or preference that should change which coverage is most useful, include a concise, faithful relevance_criteria value. Do not wait for the user to name the field, but omit it for a plain news search and never invent preferences.
+     * Search for news articles, current events, headlines, and announcements. Keep query focused on the news topic. Whenever the user states a purpose, audience, decision need, impact of interest, or coverage preference that should change ordering, put it in relevance_criteria even if related terms could also be added to query. Example: query "EU AI regulation" with relevance_criteria "Changes most likely to affect small EU software startups." Omit relevance_criteria only for a neutral news search ful
      * Description key: news.search.description
      * Skill: news/search
      */
@@ -4659,7 +4661,7 @@ declare class ShoppingAppSkills {
     private readonly runSkill;
     constructor(runSkill: AppSkillRunner);
     /**
-     * Search products on REWE, Amazon, or Stoffe.de with real-time prices. Use category to route groceries, marketplace products, fabrics, sewing supplies, and patterns to compatible providers. Invalid provider/category combinations are rejected. When the user states a material use case or preference that should change product ordering, include a concise, faithful relevance_criteria value. Keep provider, category, country, department, price, fulfilment, and sort constraints structured. A plain product
+     * Search products on REWE, Amazon, or Stoffe.de with real-time prices. Use category to route groceries, marketplace products, fabrics, sewing supplies, and patterns to compatible providers. Invalid provider/category combinations are rejected. Keep query focused on the product type. Whenever the user states an intended use, audience, compatibility need, desired quality, or preference that should change ordering, put it in relevance_criteria even if related words could also be added to query. Exampl
      * Description key: app_skills.shopping.search_products.description
      * Skill: shopping/search_products
      */
@@ -4713,7 +4715,7 @@ declare class TravelAppSkills {
      */
     searchConnections<T = unknown>(input: SkillInput, options?: AppSkillRunOptions): Promise<T>;
     /**
-     * Search hotels, hostels, and other stays for explicit dates and party size. When the user states a material stay purpose or preference that should change which valid properties rank first, include a concise, faithful relevance_criteria value. Keep dates, guests, currency, price, hotel class, rating, free cancellation, and sort constraints in their structured fields. A plain stay search may omit relevance_criteria; never invent budget, amenities, neighborhood, quietness, accessibility, workspace,
+     * Search hotels, hostels, and other stays for explicit dates and party size. Keep query focused on destination or property. Whenever the user states a trip purpose, intended activity, traveler need, desired quality, or preference that should change ordering, put it in relevance_criteria even if related words could also be added to query. Example: "Prioritize explicit reliable-Wi-Fi and in-room workspace or desk evidence." Keep dates, guests, price, class, rating, cancellation, and sort structured.
      * Description key: app_skills.travel.search_stays.description
      * Skill: travel/search_stays
      */
@@ -4741,7 +4743,7 @@ declare class VideosAppSkills {
      */
     getTranscript<T = unknown>(input: SkillInput, options?: AppSkillRunOptions): Promise<T>;
     /**
-     * Search for videos, documentaries, tutorials, and clips on the web. When the user states a material viewing purpose or preference that should change ordering, such as audience level, desired depth, format, duration, authority, or freshness, include a concise, faithful relevance_criteria value. Keep country, language, safe-search, freshness, and count constraints structured. A plain video search may omit relevance_criteria; never invent experience level, recency, duration, creator, popularity, or
+     * Search for videos, documentaries, tutorials, and clips on the web. Keep query focused on the topic. Whenever the user states a viewing or learning purpose, audience level, desired depth, format, authority, or other preference that should change ordering, put it in relevance_criteria even if related words could also be added to query. Example: query "RAG tutorial" with relevance_criteria "Advanced, hands-on production guidance with deployment and evaluation details." Keep country, language, safe-
      * Description key: videos.search.description
      * Skill: videos/search
      */
@@ -4773,7 +4775,7 @@ declare class WebAppSkills {
      */
     read<T = unknown>(input: SkillInput, options?: AppSkillRunOptions): Promise<T>;
     /**
-     * General web search for current information, prices, weather, facts, stocks, sports scores, etc. Use as a fallback when no specialized skill applies. When the user states a material purpose or preference that should change which results are most useful, include a concise, faithful relevance_criteria value (for example, research suitable for a purchase decision). Do not wait for the user to name the field, but omit it for a plain search and never invent preferences.
+     * General web search for current information, prices, weather, facts, stocks, sports scores, etc. Use as a fallback when no specialized skill applies. Keep query focused on the subject being retrieved. Whenever the user states a purpose, intended use, audience, decision need, or preference that should change result ordering, put that goal in relevance_criteria even if related words could also be added to query. For example, query "laptop-friendly cafes Berlin" with relevance_criteria "Places suita
      * Description key: app_skills.web.search.description
      * Skill: web/search
      */

package/dist/index.js

@@ -42,7 +42,7 @@ import {
   selectAssistantMessagesForSpeech,
   serializeToYaml,
   summarizeAssistantSpeech
-} from "./chunk-3PJYPJJQ.js";
+} from "./chunk-6FM33AJ3.js";
 import "./chunk-IWKP55ZB.js";
 import "./chunk-BBKJZ23O.js";
 export {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "openmates",
-  "version": "0.21.0-alpha.7",
+  "version": "0.21.0-alpha.9",
   "description": "OpenMates CLI and SDK",
   "type": "module",
   "main": "dist/index.js",