Update to 우리동네GS
Snapshot Oct 24, 2026 · 13:39 UTC · version 1.0.1
Collection source: downloaded plugin package. These snapshots do not have a confirmed matching collection source. Differences in file lists alone do not establish changes to the package.
Instructions updated for gs-retail-product-discovery
Full description — Now says: promotion.
Observed in instructions or declared skills. Runtime behavior has not been tested.
Up to 3 plugins free · no card required.
All fields and original values.
Full description
Sep 30, 2026 · 23:12 UTC
promotion and guide users from service selection to product results.
Oct 24, 2026 · 13:39 UTC
promotion.
Skill instructions
Sep 30, 2026 · 23:12 UTC
promotion and guide users from service selection to product results. Use when a user wants to find products or promotions available through the supported GS Retail service channels. Do not use for store locations, product-detail lookup, ...
Oct 24, 2026 · 13:39 UTC
promotion. Use when a user wants to find products or promotions available through the supported GS Retail service channels. Do not use for store locations, product-detail lookup, orders, reservations, carts, or payments. - If the user wa...
Supporting files
Sep 30, 2026 · 23:12 UTC
[{"relative_path":"references/negative-examples.md","size_in_bytes":5793}]
Oct 24, 2026 · 13:39 UTC
[{"relative_path":"references/negative-examples.md","size_in_bytes":5773}]
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -1,6 +1,6 @@ --- name: gs-retail-product-discovery -description: Search the GS Retail product catalog by product name, category, or promotion and guide users from service selection to product results. Use when a user wants to find products or promotions available through the supported GS Retail service channels. Do not use for store locations, product-detail lookup, orders, reservations, carts, or payments. +description: Search the GS Retail product catalog by product name, category, or promotion. Use when a user wants to find products or promotions available through the supported GS Retail service channels. Do not use for store locations, product-detail lookup, orders, reservations, carts, or payments. --- # GS Retail Product Discovery @@ -10,9 +10,8 @@ ## Choose the tool - If the user names `GS25`, `GSTHEFRESH`, `WINE25`, or requests all services, call `list_products` with that service code. -- If the user wants a product or promotion but does not name a service channel, call `select_service` first. -- After the user selects a service, continue with `list_products` using the original product intent and the selected service code. -- Do not ask for a service in plain text when `select_service` can render the service-selection widget. +- If the user wants a product or promotion but does not name a service channel, call `list_products` without `service`; it defaults to all services. +- Do not ask the user to choose a service before searching. Map user-facing service names to the exact tool code when they clearly refer to a service channel: @@ -52,7 +51,7 @@ ```text User: 우유 찾아줘 -Tool: select_service({ "query": "우유" }) +Tool: list_products({ "query": "우유" }) ``` ```text
Full technical diff · 3 changed fields
changed /description
"Search the GS Retail product catalog by product name, category, or promotion and guide users from service selection to product results. Use when a user wants to find products or promotions available through the supported GS Retail service channels. Do not use for store locations, product-detail lookup, orders, reservations, carts, or payments."
"Search the GS Retail product catalog by product name, category, or promotion. Use when a user wants to find products or promotions available through the supported GS Retail service channels. Do not use for store locations, product-detail lookup, orders, reservations, carts, or payments."
changed /included_files
[
{
"relative_path": "references/negative-examples.md",
"size_in_bytes": 5793
}
][
{
"relative_path": "references/negative-examples.md",
"size_in_bytes": 5773
}
]changed /skill_md_contents
"---\nname: gs-retail-product-discovery\ndescription: Search the GS Retail product catalog by product name, category, or promotion and guide users from service selection to product results. Use when a user wants to find products or promotions available through the supported GS Retail service channels. Do not use for store locations, product-detail lookup, orders, reservations, carts, or payments.\n---\n\n# GS Retail Product Discovery\n\nUse the MCP tools to provide a short, widget-led product discovery flow.\n\n## Choose the tool\n\n- If the user names `GS25`, `GSTHEFRESH`, `WINE25`, or requests all services, call `list_products` with that service code.\n- If the user wants a product or promotion but does not name a service channel, call `select_service` first.\n- After the user selects a service, continue with `list_products` using the original product intent and the selected service code.\n- Do not ask for a service in plain text when `select_service` can render the service-selection widget.\n\nMap user-facing service names to the exact tool code when they clearly refer to a service channel:\n\n| User expression | Service code |\n| --- | --- |\n| `GS25`, `편의점` | `GS25` |\n| `GS더프레시`, `더프레시`, `슈퍼`, `수퍼` | `GSTHEFRESH` |\n| `와인25+`, `와인25플러스`, `WINE25` | `WINE25` |\n| `전체`, `모두`, `모든 서비스` | `ALL` |\n\n## Prepare the query\n\n- Keep the product name, category, and promotion terms needed by the catalog search.\n- Remove conversational filler such as `찾아줘`, `보여줘`, `추천해줘`, `오늘`, and `지금` when it does not change the requested product intent.\n- Preserve promotion expressions such as `1+1`, `2+1`, `3+1`, `덤증정`, `gspay`, `pop할인`, `다다익선`, `묶음할인`, and `콤보`.\n- Normalize `GS Pay`, `GS페이`, and case variants to `gspay`; normalize `POP 할인` and `팝할인` to `pop할인`.\n- Do not invent a service code or product constraint that the user did not request.\n\n## Present results\n\n- Prefer the message returned by the tool and keep any accompanying assistant text brief.\n- When a widget is rendered, do not repeat product counts, service counts, or the complete results as a plain-text table.\n- Do not refer to the widget with positional wording such as `아래`, `하단`, `above`, `below`, or `following`.\n- If `searchKeywordStatus` indicates that a replacement or fallback keyword was used, preserve the tool's disclosure that a different keyword was searched.\n- Treat an empty result and a temporary search failure differently; use the message returned by the tool for each case.\n\n## Boundaries\n\n- Do not claim that a product is in stock unless the tool explicitly returns stock information.\n- Do not promise product details because no product-detail tool is available.\n- Do not place orders, reserve products, add items to a cart, or initiate payment.\n- Do not use this workflow for store-location requests or unrelated general questions.\n- Do not call the product-search tools for account changes, payment data, delivery or pickup operations, inventory checks, medical claims, restricted-goods circumvention, competitor searches, internal company data, security bypasses, or requests involving another person's data.\n- When evaluating an ambiguous or negative request, use [negative examples](references/negative-examples.md) to identify unsupported intent. Do not treat the examples as capabilities.\n\n## Examples\n\n```text\nUser: 우유 찾아줘\nTool: select_service({ \"query\": \"우유\" })\n```\n\n```text\nUser: GS25 1+1 음료 보여줘\nTool: list_products({ \"query\": \"1+1 음료\", \"service\": \"GS25\" })\n```\n\n```text\nUser: 모든 서비스에서 과자 찾아줘\nTool: list_products({ \"query\": \"과자\", \"service\": \"ALL\" })\n```\n\n```text\nUser: GS더프레시에서 계란 찾아줘\nTool: list_products({ \"query\": \"계란\", \"service\": \"GSTHEFRESH\" })\n```\n\n```text\nUser: 강남역 근처 GS25 찾아줘\nAction: Do not call the product-search tools because this is a store-location request.\n```\n""---\nname: gs-retail-product-discovery\ndescription: Search the GS Retail product catalog by product name, category, or promotion. Use when a user wants to find products or promotions available through the supported GS Retail service channels. Do not use for store locations, product-detail lookup, orders, reservations, carts, or payments.\n---\n\n# GS Retail Product Discovery\n\nUse the MCP tools to provide a short, widget-led product discovery flow.\n\n## Choose the tool\n\n- If the user names `GS25`, `GSTHEFRESH`, `WINE25`, or requests all services, call `list_products` with that service code.\n- If the user wants a product or promotion but does not name a service channel, call `list_products` without `service`; it defaults to all services.\n- Do not ask the user to choose a service before searching.\n\nMap user-facing service names to the exact tool code when they clearly refer to a service channel:\n\n| User expression | Service code |\n| --- | --- |\n| `GS25`, `편의점` | `GS25` |\n| `GS더프레시`, `더프레시`, `슈퍼`, `수퍼` | `GSTHEFRESH` |\n| `와인25+`, `와인25플러스`, `WINE25` | `WINE25` |\n| `전체`, `모두`, `모든 서비스` | `ALL` |\n\n## Prepare the query\n\n- Keep the product name, category, and promotion terms needed by the catalog search.\n- Remove conversational filler such as `찾아줘`, `보여줘`, `추천해줘`, `오늘`, and `지금` when it does not change the requested product intent.\n- Preserve promotion expressions such as `1+1`, `2+1`, `3+1`, `덤증정`, `gspay`, `pop할인`, `다다익선`, `묶음할인`, and `콤보`.\n- Normalize `GS Pay`, `GS페이`, and case variants to `gspay`; normalize `POP 할인` and `팝할인` to `pop할인`.\n- Do not invent a service code or product constraint that the user did not request.\n\n## Present results\n\n- Prefer the message returned by the tool and keep any accompanying assistant text brief.\n- When a widget is rendered, do not repeat product counts, service counts, or the complete results as a plain-text table.\n- Do not refer to the widget with positional wording such as `아래`, `하단`, `above`, `below`, or `following`.\n- If `searchKeywordStatus` indicates that a replacement or fallback keyword was used, preserve the tool's disclosure that a different keyword was searched.\n- Treat an empty result and a temporary search failure differently; use the message returned by the tool for each case.\n\n## Boundaries\n\n- Do not claim that a product is in stock unless the tool explicitly returns stock information.\n- Do not promise product details because no product-detail tool is available.\n- Do not place orders, reserve products, add items to a cart, or initiate payment.\n- Do not use this workflow for store-location requests or unrelated general questions.\n- Do not call the product-search tools for account changes, payment data, delivery or pickup operations, inventory checks, medical claims, restricted-goods circumvention, competitor searches, internal company data, security bypasses, or requests involving another person's data.\n- When evaluating an ambiguous or negative request, use [negative examples](references/negative-examples.md) to identify unsupported intent. Do not treat the examples as capabilities.\n\n## Examples\n\n```text\nUser: 우유 찾아줘\nTool: list_products({ \"query\": \"우유\" })\n```\n\n```text\nUser: GS25 1+1 음료 보여줘\nTool: list_products({ \"query\": \"1+1 음료\", \"service\": \"GS25\" })\n```\n\n```text\nUser: 모든 서비스에서 과자 찾아줘\nTool: list_products({ \"query\": \"과자\", \"service\": \"ALL\" })\n```\n\n```text\nUser: GS더프레시에서 계란 찾아줘\nTool: list_products({ \"query\": \"계란\", \"service\": \"GSTHEFRESH\" })\n```\n\n```text\nUser: 강남역 근처 GS25 찾아줘\nAction: Do not call the product-search tools because this is a store-location request.\n```\n"Full snapshot data
{
"description": "Search the GS Retail product catalog by product name, category, or promotion. Use when a user wants to find products or promotions available through the supported GS Retail service channels. Do not use for store locations, product-detail lookup, orders, reservations, carts, or payments.",
"included_files": [
{
"relative_path": "references/negative-examples.md",
"size_in_bytes": 5773
}
],
"name": "gs-retail-product-discovery",
"skill_md_contents": "---\nname: gs-retail-product-discovery\ndescription: Search the GS Retail product catalog by product name, category, or promotion. Use when a user wants to find products or promotions available through the supported GS Retail service channels. Do not use for store locations, product-detail lookup, orders, reservations, carts, or payments.\n---\n\n# GS Retail Product Discovery\n\nUse the MCP tools to provide a short, widget-led product discovery flow.\n\n## Choose the tool\n\n- If the user names `GS25`, `GSTHEFRESH`, `WINE25`, or requests all services, call `list_products` with that service code.\n- If the user wants a product or promotion but does not name a service channel, call `list_products` without `service`; it defaults to all services.\n- Do not ask the user to choose a service before searching.\n\nMap user-facing service names to the exact tool code when they clearly refer to a service channel:\n\n| User expression | Service code |\n| --- | --- |\n| `GS25`, `편의점` | `GS25` |\n| `GS더프레시`, `더프레시`, `슈퍼`, `수퍼` | `GSTHEFRESH` |\n| `와인25+`, `와인25플러스`, `WINE25` | `WINE25` |\n| `전체`, `모두`, `모든 서비스` | `ALL` |\n\n## Prepare the query\n\n- Keep the product name, category, and promotion terms needed by the catalog search.\n- Remove conversational filler such as `찾아줘`, `보여줘`, `추천해줘`, `오늘`, and `지금` when it does not change the requested product intent.\n- Preserve promotion expressions such as `1+1`, `2+1`, `3+1`, `덤증정`, `gspay`, `pop할인`, `다다익선`, `묶음할인`, and `콤보`.\n- Normalize `GS Pay`, `GS페이`, and case variants to `gspay`; normalize `POP 할인` and `팝할인` to `pop할인`.\n- Do not invent a service code or product constraint that the user did not request.\n\n## Present results\n\n- Prefer the message returned by the tool and keep any accompanying assistant text brief.\n- When a widget is rendered, do not repeat product counts, service counts, or the complete results as a plain-text table.\n- Do not refer to the widget with positional wording such as `아래`, `하단`, `above`, `below`, or `following`.\n- If `searchKeywordStatus` indicates that a replacement or fallback keyword was used, preserve the tool's disclosure that a different keyword was searched.\n- Treat an empty result and a temporary search failure differently; use the message returned by the tool for each case.\n\n## Boundaries\n\n- Do not claim that a product is in stock unless the tool explicitly returns stock information.\n- Do not promise product details because no product-detail tool is available.\n- Do not place orders, reserve products, add items to a cart, or initiate payment.\n- Do not use this workflow for store-location requests or unrelated general questions.\n- Do not call the product-search tools for account changes, payment data, delivery or pickup operations, inventory checks, medical claims, restricted-goods circumvention, competitor searches, internal company data, security bypasses, or requests involving another person's data.\n- When evaluating an ambiguous or negative request, use [negative examples](references/negative-examples.md) to identify unsupported intent. Do not treat the examples as capabilities.\n\n## Examples\n\n```text\nUser: 우유 찾아줘\nTool: list_products({ \"query\": \"우유\" })\n```\n\n```text\nUser: GS25 1+1 음료 보여줘\nTool: list_products({ \"query\": \"1+1 음료\", \"service\": \"GS25\" })\n```\n\n```text\nUser: 모든 서비스에서 과자 찾아줘\nTool: list_products({ \"query\": \"과자\", \"service\": \"ALL\" })\n```\n\n```text\nUser: GS더프레시에서 계란 찾아줘\nTool: list_products({ \"query\": \"계란\", \"service\": \"GSTHEFRESH\" })\n```\n\n```text\nUser: 강남역 근처 GS25 찾아줘\nAction: Do not call the product-search tools because this is a store-location request.\n```\n"
}SHA-256 of public snapshot: bff4d3b7fc0b057dbbd5c45a128e4102d800119d7ab73b3d28646af464a3ea46