← 우리동네GSCONTENT HISTORY

Update to 우리동네GS

Snapshot Nov 9, 2026 · 12:07 UTC · version 1.0.2

Collection source: downloaded plugin package.

WHAT CHANGED

Instructions updated for gs-retail-product-discovery

Full description — Now says: promotion, or a natural-language phrase describing a situation, preference, or purpose. Use when a user wants to find products or promotions available...

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save 우리동네GS and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Full description

Before

Oct 24, 2026 · 13:39 UTC

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,

After

Nov 9, 2026 · 12:07 UTC

promotion, or a natural-language phrase describing a situation, preference, or purpose. Use when a user wants to find products or promotions available through the supported GS Retail service channels. Do not use to execute store-location...

Skill instructions

Before

Oct 24, 2026 · 13:39 UTC

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. - Do not ask ...

After

Nov 9, 2026 · 12:07 UTC

promotion, or a natural-language phrase describing a situation, preference, or purpose. Use when a user wants to find products or promotions available through the supported GS Retail service channels. Do not use to execute store-location...

Compare saved observations

Download comparison JSON

SKILL.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. 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, promotion, or a natural-language phrase describing a situation, preference, or purpose. Use when a user wants to find products or promotions available through the supported GS Retail service channels. Do not use to execute store-location lookup, product-detail lookup, orders, reservations, cart changes, or payments.
 ---
 
 # GS Retail Product Discovery
@@ -11,7 +11,6 @@
 
 - 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 `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:
 
@@ -24,8 +23,9 @@
 
 ## Prepare the query
 
-- Keep the product name, category, and promotion terms needed by the catalog search.
-- Remove conversational filler such as `찾아줘`, `보여줘`, `추천해줘`, `오늘`, and `지금` when it does not change the requested product intent.
+- Keep product names, categories, promotion terms, and meaningful natural-language phrases that describe the user's situation, preference, or purpose.
+- Preserve those semantic phrases instead of reducing them to guessed product names, categories, or keywords. For example, keep `운동 끝나고 먹기 좋은 것` as written rather than changing it to `단백질 음료`.
+- Remove only request expressions such as `찾아줘`, `보여줘`, and `추천해줘`, or time expressions such as `오늘` and `지금`, when they do not change the search meaning.
 - Preserve promotion expressions such as `1+1`, `2+1`, `3+1`, `덤증정`, `gspay`, `pop할인`, `다다익선`, `묶음할인`, and `콤보`.
 - Normalize `GS Pay`, `GS페이`, and case variants to `gspay`; normalize `POP 할인` and `팝할인` to `pop할인`.
 - Do not invent a service code or product constraint that the user did not request.
@@ -43,6 +43,7 @@
 - Do not claim that a product is in stock unless the tool explicitly returns stock information.
 - Do not promise product details because no product-detail tool is available.
 - Do not place orders, reserve products, add items to a cart, or initiate payment.
+- A product-discovery phrase may mention an intended ordering, delivery, pickup, or reservation context. Keep that context in the query when the user is asking which products suit it, but do not claim availability or perform the operation.
 - Do not use this workflow for store-location requests or unrelated general questions.
 - 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.
 - 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.
@@ -70,6 +71,21 @@
 ```
 
 ```text
+User: 운동 끝나고 먹기 좋은 것 추천해줘
+Tool: list_products({ "query": "운동 끝나고 먹기 좋은 것" })
+```
+
+```text
+User: 출근길에 미리 주문해두고 받을 수 있는 아침 추천해줘
+Tool: list_products({ "query": "출근길에 미리 주문해두고 받을 수 있는 아침" })
+```
+
+```text
+User: GS25에서 매운 거 좋아하는데 자극적이지 않은 라면 보여줘
+Tool: list_products({ "query": "매운 거 좋아하는데 자극적이지 않은 라면", "service": "GS25" })
+```
+
+```text
 User: 강남역 근처 GS25 찾아줘
 Action: Do not call the product-search tools because this is a store-location request.
 ```
Full technical diff · 2 changed fields

changed /description

BEFORE
"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."
AFTER
"Search the GS Retail product catalog by product name, category, promotion, or a natural-language phrase describing a situation, preference, or purpose. Use when a user wants to find products or promotions available through the supported GS Retail service channels. Do not use to execute store-location lookup, product-detail lookup, orders, reservations, cart changes, or payments."

changed /skill_md_contents

BEFORE
"---\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"
AFTER
"---\nname: gs-retail-product-discovery\ndescription: Search the GS Retail product catalog by product name, category, promotion, or a natural-language phrase describing a situation, preference, or purpose. Use when a user wants to find products or promotions available through the supported GS Retail service channels. Do not use to execute store-location lookup, product-detail lookup, orders, reservations, cart changes, 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\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 product names, categories, promotion terms, and meaningful natural-language phrases that describe the user's situation, preference, or purpose.\n- Preserve those semantic phrases instead of reducing them to guessed product names, categories, or keywords. For example, keep `운동 끝나고 먹기 좋은 것` as written rather than changing it to `단백질 음료`.\n- Remove only request expressions such as `찾아줘`, `보여줘`, and `추천해줘`, or time expressions such as `오늘` and `지금`, when they do not change the search meaning.\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- A product-discovery phrase may mention an intended ordering, delivery, pickup, or reservation context. Keep that context in the query when the user is asking which products suit it, but do not claim availability or perform the operation.\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: 운동 끝나고 먹기 좋은 것 추천해줘\nTool: list_products({ \"query\": \"운동 끝나고 먹기 좋은 것\" })\n```\n\n```text\nUser: 출근길에 미리 주문해두고 받을 수 있는 아침 추천해줘\nTool: list_products({ \"query\": \"출근길에 미리 주문해두고 받을 수 있는 아침\" })\n```\n\n```text\nUser: GS25에서 매운 거 좋아하는데 자극적이지 않은 라면 보여줘\nTool: list_products({ \"query\": \"매운 거 좋아하는데 자극적이지 않은 라면\", \"service\": \"GS25\" })\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, promotion, or a natural-language phrase describing a situation, preference, or purpose. Use when a user wants to find products or promotions available through the supported GS Retail service channels. Do not use to execute store-location lookup, product-detail lookup, orders, reservations, cart changes, 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, promotion, or a natural-language phrase describing a situation, preference, or purpose. Use when a user wants to find products or promotions available through the supported GS Retail service channels. Do not use to execute store-location lookup, product-detail lookup, orders, reservations, cart changes, 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\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 product names, categories, promotion terms, and meaningful natural-language phrases that describe the user's situation, preference, or purpose.\n- Preserve those semantic phrases instead of reducing them to guessed product names, categories, or keywords. For example, keep `운동 끝나고 먹기 좋은 것` as written rather than changing it to `단백질 음료`.\n- Remove only request expressions such as `찾아줘`, `보여줘`, and `추천해줘`, or time expressions such as `오늘` and `지금`, when they do not change the search meaning.\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- A product-discovery phrase may mention an intended ordering, delivery, pickup, or reservation context. Keep that context in the query when the user is asking which products suit it, but do not claim availability or perform the operation.\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: 운동 끝나고 먹기 좋은 것 추천해줘\nTool: list_products({ \"query\": \"운동 끝나고 먹기 좋은 것\" })\n```\n\n```text\nUser: 출근길에 미리 주문해두고 받을 수 있는 아침 추천해줘\nTool: list_products({ \"query\": \"출근길에 미리 주문해두고 받을 수 있는 아침\" })\n```\n\n```text\nUser: GS25에서 매운 거 좋아하는데 자극적이지 않은 라면 보여줘\nTool: list_products({ \"query\": \"매운 거 좋아하는데 자극적이지 않은 라면\", \"service\": \"GS25\" })\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: f3f39ae9b7be9f6fba116087632a53760e19de5403bb669758760121e4fe4919