[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718DSD527W213JAAF98QV1P":3,"skill-same:01M718DSD527W213JAAF98QV1P":67},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M718DSD527W213JAAF98QV1P","commerce-merchant-operations",null,"The reference merchant agent, covering its flows, staged changes and host approval, metrics grounding, the analysis delegate, store memory, components, and marketplace rules. Load when building or reviewing an agent for the operators of a store, property, subscriber base, or venue.","anthropics\u002Fcommerce-agents","anthropics","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F76263028?v=4","01M697XGDPXJAVQ8391V2BCYTE","Anthropic","01M718D5FGWKEA8ZJF2GGGYZWB",3473,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fcommerce-agents\u002Fblob\u002Fmain\u002Fplugins\u002Fcommerce-builder\u002Fskills\u002Fcommerce-merchant-operations\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"commerce merchant operations","commerce","operations","merchant","base","marketplace","operators","changes","store","grounding","components","analysis","when","Rules","load","host","flows","delegate","for","memory","2026-11-10 10:12:30",false,"---\nname: commerce-merchant-operations\ndescription: The reference merchant agent, covering its flows, staged changes and host approval, metrics grounding, the analysis delegate, store memory, components, and marketplace rules. Load when building or reviewing an agent for the operators of a store, property, subscriber base, or venue.\n---\n\n# Merchant agent\n\nPaths are in the reference repo: `merchant_agent\u002F` is `merchant-agent\u002Fcore\u002Fmerchant_agent\u002F`, `merchant_agent_runtime\u002F`\nis `merchant-agent\u002Fruntime-messages-api\u002Fmerchant_agent_runtime\u002F`, `merchant_agent_sdk\u002F` is\n`merchant-agent\u002Fruntime-agent-sdk\u002Fmerchant_agent_sdk\u002F`, `commerce_common\u002F` is `commerce-common\u002Fcommerce_common\u002F`.\n\n## What it does\n\nThe merchant agent works with an operator inside their back office over one `MerchantBackend` (`merchant_agent\u002Fbackend.py`).\nIts five flows are the skills in `merchant-agent\u002Fskills\u002F`: performance-insights, catalog-listings, inventory-operations,\npricing-promotions, marketing-campaigns. The mechanisms in `commerce_common\u002F` are shared; the prompt, tools, gates, and\nexecutor are its own, and every tool result comes back inside `MERCHANT_FENCE` (`merchant_agent\u002Ffencing.py`).\n\n## The staged-change contract\n\n1. Every write is a `stage_*` tool (`stage_listing_update`, `stage_price_update`, `stage_inventory_action`, `stage_promotion`,\n   `stage_campaign`). Each returns the staged record and a note, emits a `change_update` event, and, with\n   `stage_shows_preview` on (the default, `merchant_agent\u002Fconfig.py`), emits the `change_preview` card through the runner\n   `present_change_preview` uses (`MerchantToolExecutor`, `merchant_agent\u002Fexecutor.py`). The MCP server turns it off\n   because its executor events do not reach the operator, so the hosted agent calls `present_change_preview`; that tool\n   also shows an earlier change again. Live state is untouched until `apply_change`, which performs the platform write.\n2. Staging accepts only listing and campaign ids that tools returned this session, and a content edit also needs a\n   `get_listing` read; `apply_change` and `discard_change` accept only change ids that staging or `get_pending_changes`\n   returned (`merchant_agent\u002Fgates.py`). Showing the preview card marks nothing approved.\n3. `check_guardrails` in `merchant_agent\u002Fchanges.py` runs when a change is staged (`ChangeLedger.stage`, or your backend's\n   equivalent) and again in `check_apply_change` (`merchant_agent\u002Fgates.py`) under the config in force at apply time.\n   The limits are `max_items_per_change`, `max_price_delta_pct`, `max_promotion_discount_pct`, `max_restock_quantity`,\n   `max_campaign_budget`, and `max_listing_field_chars` in `merchant_agent\u002Fconfig.py`; the defaults are demonstration values.\n4. `protected_fields` can never be staged, `price_bearing_fields` are the fields the price cap reads, and\n   `listing_update_blocked_fields` may not ride a free-form listing update. A domain that prices under another name\n   (a nightly rate, a monthly fee, a tier price) appends to these tuples and never replaces them.\n5. `require_host_approval` defaults to `True`: `apply_change` succeeds only for an id in `MerchantSessionState.approved_change_ids`,\n   which only host code writes. The three surfaces in the repo are the portal's `\u002Fchanges\u002F{change_id}\u002Fapply` route\n   (`examples\u002Fdemo_common\u002Fmerchant.py`), `MerchantToolset.host_approve` (`merchant_agent_sdk\u002Fmerchant_tools.py`, prompted\n   per change by `merchant-agent\u002Fruntime-agent-sdk\u002Fmain.py`), and `always_ask` on `apply_change` in the hosted manifest;\n   there the MCP server's config sets `require_host_approval=False` (its `default_config` does; a config you pass\n   must too, or every apply is held). An approval typed into the chat sets nothing.\n6. `require_host_approval` and `approval_surface` render into the static prompt and into refusals, so they are set per\n   deployment and a change to either is a redeploy (commerce-prompt-caching). Name the real surface in `approval_surface`.\n7. A change kind a system does not support raises `ChangeNotApplicable` (`merchant_agent\u002Fchanges.py`) and the executor\n   relays it; the tool stays registered. Applied and discarded changes stay queryable as the audit trail, each stamped\n   with the operator from `MerchantSessionContext.operator`, which a production host derives from its authentication.\n\n## Grounding and follow-through\n\n- A performance question forces `get_business_snapshot`, and a change request carrying an apply phrase with nothing\n  staged this session forces `get_pending_changes` (`GROUNDING_RULES` in `merchant_agent\u002Fgrounding.py`; lexicons and\n  flags in `merchant_agent\u002Fconfig.py`, appended to and never replaced).\n- A turn that matched `change_requested` and ended on bare text, with no `stage_*` attempt and no `present_suggestions`\n  close, gets `STAGING_FOLLOWTHROUGH_REMINDER` once, as a user message (`merchant_agent\u002Fgates.py`; applied in\n  `merchant_agent_runtime\u002Forchestrator.py` and `merchant_agent_sdk\u002Fagent.py`); the reminder text is excluded from memory extraction.\n- `present_metrics` joins each pick from the snapshot, a queried series, a campaign, or a recorded analysis and drops the\n  rest with a note (`resolve_metrics` in `merchant_agent\u002Fenrichment.py`), so a card never carries a model-authored figure.\n\n## The analysis delegate\n\n- `enable_analysis` (default off) registers `run_analysis`, a `DelegateExtension` built by `build_analysis_delegate` in\n  `merchant_agent_runtime\u002Fanalysis.py`. The delegate's tools are a submit tool, a progress tool, the `ANALYSIS_READ_TOOLS`\n  (`merchant_agent\u002Fanalysis.py`), and a query tool when the backend implements `MerchantBackend.execute_analysis_query`\n  (`analysis_sql_only` then leaves the per-series reads off). It holds no staging tool; its result is recorded in\n  `seen_analyses` and rendered as its own metrics card.\n- `check_analysis_sql` refuses anything other than one SELECT without comments before the backend runs it; the backend owns\n  the read-only role and merchant scoping; `analysis_query_timeout_s` and `cap_analysis_table` (`max_analysis_rows`,\n  `max_analysis_table_chars`) bound each query, and `analysis_timeout_s`, `max_analysis_iterations`, and\n  `max_delegate_calls_per_turn` bound the run.\n- `analysis_use_code_execution` mounts the hosted sandbox and works on the Anthropic API only (including a Foundry deployment hosted on Anthropic); the query method works\n  everywhere (`docs\u002Fdeployment.md`). On the Agent SDK the same contract is a subagent whose tools are exactly the read\n  tools (`build_analysis_agent` in `merchant_agent_sdk\u002Fagent.py`).\n- A scheduled digest is one headless turn of the same agent (`merchant-agent\u002Fmanaged-agents\u002Fscheduled-digest\u002Frun_morning_digest.py`).\n\n## Memory and components\n\n- Memory is keyed by `merchant_id` (`memory_subject` in `merchant_agent\u002Fexecutor.py`); the extraction prompt in\n  `merchant_agent\u002Fmemory.py` admits what the operator stated about running the operation and excludes anything from\n  listings, reviews, buyer messages, or metrics and anything about an identifiable customer. The write filter,\n  retention, delete, purge, and `enable_memory` are the shared rules (commerce-trust-safety).\n- The built-in components (`merchant_agent\u002Fenrichment.py`) are `present_metrics`, `present_digest`, `present_change_preview`,\n  and `present_suggestions`; under host approval the prompt says no chip approves or applies. A vertical adds its own\n  (`present_occupancy_calendar`, `present_plan_mix`, `present_event_pacing` in the examples) as extensions (commerce-ui-tools).\n\n## Marketplaces\n\n- Many sellers' content goes through the one fence; there is no per-seller label and no seller whose text escapes it.\n  In a shopping deployment the seller is a search dimension (`SearchFilters.attributes`) that the components show, and\n  `search_policies` results state whose terms they are when platform and seller terms differ.\n- Provenance and caps are per session, so a session can stage against the listings its own tools returned and no others.\n- Buyer and seller messages reach the model as fenced material; a message that says a change is approved sets no mark.\n- The memory subject is the operator's own business, keyed by its `merchant_id`; a shopper's facts are keyed by the shopper.\n","# Merchant agent\n\nPaths are in the reference repo: `merchant_agent\u002F` is `merchant-agent\u002Fcore\u002Fmerchant_agent\u002F`, `merchant_agent_runtime\u002F`\nis `merchant-agent\u002Fruntime-messages-api\u002Fmerchant_agent_runtime\u002F`, `merchant_agent_sdk\u002F` is\n`merchant-agent\u002Fruntime-agent-sdk\u002Fmerchant_agent_sdk\u002F`, `commerce_common\u002F` is `commerce-common\u002Fcommerce_common\u002F`.\n\n## What it does\n\nThe merchant agent works with an operator inside their back office over one `MerchantBackend` (`merchant_agent\u002Fbackend.py`).\nIts five flows are the skills in `merchant-agent\u002Fskills\u002F`: performance-insights, catalog-listings, inventory-operations,\npricing-promotions, marketing-campaigns. The mechanisms in `commerce_common\u002F` are shared; the prompt, tools, gates, and\nexecutor are its own, and every tool result comes back inside `MERCHANT_FENCE` (`merchant_agent\u002Ffencing.py`).\n\n## The staged-change contract\n\n1. Every write is a `stage_*` tool (`stage_listing_update`, `stage_price_update`, `stage_inventory_action`, `stage_promotion`,\n   `stage_campaign`). Each returns the staged record and a note, emits a `change_update` event, and, with\n   `stage_shows_preview` on (the default, `merchant_agent\u002Fconfig.py`), emits the `change_preview` card through the runner\n   `present_change_preview` uses (`MerchantToolExecutor`, `merchant_agent\u002Fexecutor.py`). The MCP server turns it off\n   because its executor events do not reach the operator, so the hosted agent calls `present_change_preview`; that tool\n   also shows an earlier change again. Live state is untouched until `apply_change`, which performs the platform write.\n2. Staging accepts only listing and campaign ids that tools returned this session, and a content edit also needs a\n   `get_listing` read; `apply_change` and `discard_change` accept only change ids that staging or `get_pending_changes`\n   returned (`merchant_agent\u002Fgates.py`). Showing the preview card marks nothing approved.\n3. `check_guardrails` in `merchant_agent\u002Fchanges.py` runs when a change is staged (`ChangeLedger.stage`, or your backend's\n   equivalent) and again in `check_apply_change` (`merchant_agent\u002Fgates.py`) under the config in force at apply time.\n   The limits are `max_items_per_change`, `max_price_delta_pct`, `max_promotion_discount_pct`, `max_restock_quantity`,\n   `max_campaign_budget`, and `max_listing_field_chars` in `merchant_agent\u002Fconfig.py`; the defaults are demonstration values.\n4. `protected_fields` can never be staged, `price_bearing_fields` are the fields the price cap reads, and\n   `listing_update_blocked_fields` may not ride a free-form listing update. A domain that prices under another name\n   (a nightly rate, a monthly fee, a tier price) appends to these tuples and never replaces them.\n5. `require_host_approval` defaults to `True`: `apply_change` succeeds only for an id in `MerchantSessionState.approved_change_ids`,\n   which only host code writes. The three surfaces in the repo are the portal's `\u002Fchanges\u002F{change_id}\u002Fapply` route\n   (`examples\u002Fdemo_common\u002Fmerchant.py`), `MerchantToolset.host_approve` (`merchant_agent_sdk\u002Fmerchant_tools.py`, prompted\n   per change by `merchant-agent\u002Fruntime-agent-sdk\u002Fmain.py`), and `always_ask` on `apply_change` in the hosted manifest;\n   there the MCP server's config sets `require_host_approval=False` (its `default_config` does; a config you pass\n   must too, or every apply is held). An approval typed into the chat sets nothing.\n6. `require_host_approval` and `approval_surface` render into the static prompt and into refusals, so they are set per\n   deployment and a change to either is a redeploy (commerce-prompt-caching). Name the real surface in `approval_surface`.\n7. A change kind a system does not support raises `ChangeNotApplicable` (`merchant_agent\u002Fchanges.py`) and the executor\n   relays it; the tool stays registered. Applied and discarded changes stay queryable as the audit trail, each stamped\n   with the operator from `MerchantSessionContext.operator`, which a production host derives from its authentication.\n\n## Grounding and follow-through\n\n- A performance question forces `get_business_snapshot`, and a change request carrying an apply phrase with nothing\n  staged this session forces `get_pending_changes` (`GROUNDING_RULES` in `merchant_agent\u002Fgrounding.py`; lexicons and\n  flags in `merchant_agent\u002Fconfig.py`, appended to and never replaced).\n- A turn that matched `change_requested` and ended on bare text, with no `stage_*` attempt and no `present_suggestions`\n  close, gets `STAGING_FOLLOWTHROUGH_REMINDER` once, as a user message (`merchant_agent\u002Fgates.py`; applied in\n  `merchant_agent_runtime\u002Forchestrator.py` and `merchant_agent_sdk\u002Fagent.py`); the reminder text is excluded from memory extraction.\n- `present_metrics` joins each pick from the snapshot, a queried series, a campaign, or a recorded analysis and drops the\n  rest with a note (`resolve_metrics` in `merchant_agent\u002Fenrichment.py`), so a card never carries a model-authored figure.\n\n## The analysis delegate\n\n- `enable_analysis` (default off) registers `run_analysis`, a `DelegateExtension` built by `build_analysis_delegate` in\n  `merchant_agent_runtime\u002Fanalysis.py`. The delegate's tools are a submit tool, a progress tool, the `ANALYSIS_READ_TOOLS`\n  (`merchant_agent\u002Fanalysis.py`), and a query tool when the backend implements `MerchantBackend.execute_analysis_query`\n  (`analysis_sql_only` then leaves the per-series reads off). It holds no staging tool; its result is recorded in\n  `seen_analyses` and rendered as its own metrics card.\n- `check_analysis_sql` refuses anything other than one SELECT without comments before the backend runs it; the backend owns\n  the read-only role and merchant scoping; `analysis_query_timeout_s` and `cap_analysis_table` (`max_analysis_rows`,\n  `max_analysis_table_chars`) bound each query, and `analysis_timeout_s`, `max_analysis_iterations`, and\n  `max_delegate_calls_per_turn` bound the run.\n- `analysis_use_code_execution` mounts the hosted sandbox and works on the Anthropic API only (including a Foundry deployment hosted on Anthropic); the query method works\n  everywhere (`docs\u002Fdeployment.md`). On the Agent SDK the same contract is a subagent whose tools are exactly the read\n  tools (`build_analysis_agent` in `merchant_agent_sdk\u002Fagent.py`).\n- A scheduled digest is one headless turn of the same agent (`merchant-agent\u002Fmanaged-agents\u002Fscheduled-digest\u002Frun_morning_digest.py`).\n\n## Memory and components\n\n- Memory is keyed by `merchant_id` (`memory_subject` in `merchant_agent\u002Fexecutor.py`); the extraction prompt in\n  `merchant_agent\u002Fmemory.py` admits what the operator stated about running the operation and excludes anything from\n  listings, reviews, buyer messages, or metrics and anything about an identifiable customer. The write filter,\n  retention, delete, purge, and `enable_memory` are the shared rules (commerce-trust-safety).\n- The built-in components (`merchant_agent\u002Fenrichment.py`) are `present_metrics`, `present_digest`, `present_change_preview`,\n  and `present_suggestions`; under host approval the prompt says no chip approves or applies. A vertical adds its own\n  (`present_occupancy_calendar`, `present_plan_mix`, `present_event_pacing` in the examples) as extensions (commerce-ui-tools).\n\n## Marketplaces\n\n- Many sellers' content goes through the one fence; there is no per-seller label and no seller whose text escapes it.\n  In a shopping deployment the seller is a search dimension (`SearchFilters.attributes`) that the components show, and\n  `search_policies` results state whose terms they are when platform and seller terms differ.\n- Provenance and caps are per session, so a session can stage against the listings its own tools returned and no others.\n- Buyer and seller messages reach the model as fenced material; a message that says a change is approved sets no mark.\n- The memory subject is the operator's own business, keyed by its `merchant_id`; a shopper's facts are keyed by the shopper.\n",{"name":5,"description":7},"main","fd4d59224ab96b43c6dc6888207c67b3bd5a24cf","plugins\u002Fcommerce-builder\u002Fskills\u002Fcommerce-merchant-operations",714,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fcommerce-agents","https:\u002F\u002Fclaude.com\u002Fsolutions\u002Fcommerce","https:\u002F\u002Fgithub.com\u002Fanthropics","https:\u002F\u002Fanthropic.com","2026-11-04 19:55:09",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add anthropics\u002Fcommerce-agents --skill commerce-merchant-operations",{"tool":59,"command":60},"bunx","bunx skills add anthropics\u002Fcommerce-agents --skill commerce-merchant-operations",{"tool":62,"command":63},"pnpm","pnpm dlx skills add anthropics\u002Fcommerce-agents --skill commerce-merchant-operations","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fcommerce-agents\u002Fblob\u002Fmain\u002Fplugins\u002Fcommerce-builder\u002Fskills\u002Fcommerce-merchant-operations\u002FSKILL.md",true,[],[68,91,115,135,157,175],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":39},"01M718ECZVF8TFQM4CVAT5HGQG","search-discovery","Turning a described need (several constraints, a gift, a choice between candidates already in view, a search that came back empty or sold out) into a shortlist and a pick. Not needed when one search for the thing the customer named answers the request, or when the customer wants to learn what matters in a category first (purchase-research).","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fcommerce-agents\u002Fblob\u002Fmain\u002Fshopping-agent\u002Fskills\u002Fsearch-discovery\u002FSKILL.md",[],[75,76,77,78,79,80,81,82,83,37,84,85,86,87,88,31,89,90],"discovery","search","search discovery","back","research","first","gift","view","customer","request","pick","purchase","choice","empty","learn","constraints",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":102,"publishedAt":39},"01M718EAXW7452GQ9336TFCEMH","purchase-research","Teaching a customer how to choose before any candidates appear, when they ask what matters in a category, how two approaches to it differ, or where to begin. Not needed once the customer has named the thing they want, however considered the purchase (that is search work), nor for outfitting a space or an event (planning-goals).","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fcommerce-agents\u002Fblob\u002Fmain\u002Fshopping-agent\u002Fskills\u002Fpurchase-research\u002FSKILL.md",[97],{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[79,103,86,104,105,106,83,107,37,108,109,76,110,111,31,112,113,114],"purchase research","work","goals","planning","how","event","choose","space","how to","ask","teaching","it",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":39},"01M718E8N33VV0XXCY2DA4Y548","planning-goals","Planning a coordinated set of items toward a goal, an event, a trip, or a project, where the request only comes together as several purchases with a structure between them, and later changes to a plan you have presented. Not needed when the customer wants a single item, however carefully chosen.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fcommerce-agents\u002Fblob\u002Fmain\u002Fshopping-agent\u002Fskills\u002Fplanning-goals\u002FSKILL.md",[],[122,105,106,123,124,125,126,127,26,128,83,129,130,108,84,131,132,31,133,134],"planning goals","SET","with","as","structure","plan","later","project","goal","single","only","you","trip",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":39},"01M718E5ES8CYDTZFZPB5XDTYP","memory-personalization","Requests about what is remembered, however short, from an ask to remember one thing to asks to say what is on file, correct it, or forget it; a bare save or an answer from the profile alone does not cover these. Also applying what the store already knows, recalling an older fact (a past recipient, a size, a recurring order) when it would change the pick, and deciding what should outlast the session. Not needed when the request carries no personal context to apply or keep.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fcommerce-agents\u002Fblob\u002Fmain\u002Fshopping-agent\u002Fskills\u002Fmemory-personalization\u002FSKILL.md",[],[38,142,143,144,145,146,147,148,149,150,85,31,151,112,152,153,27,154,155,156],"memory personalization","personalization","bare","remember","recurring","answer","session","correct","short","keep","apply","file","forget","say","change",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":163,"publishedAt":39},"01M718E3E3Y51D55XXTQ9979T9","customer-care","Help after a purchase or booking, covering the status of an order or delivery whether or not the customer names it, returns, refunds, exchanges, and cancellations, an item that arrived damaged, incomplete, or late, and questions about the store's terms or a membership. Not needed for finding, comparing, or choosing something new.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fcommerce-agents\u002Fblob\u002Fmain\u002Fshopping-agent\u002Fskills\u002Fcustomer-care\u002FSKILL.md",[],[83,164,27,37,165,166,167,168,169,86,170,171,172,114,173,174],"customer care","help","booking","questions","about","delivery","status","new","terms","refunds","returns",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":192,"publishedAt":39},"01M718E0X4VE056S16PA347Z3F","commerce-ui-tools","The reference presentation-tool contract, covering server-side enrichment, suggestion chips, the event stream, progressive rendering, both roles' built-in components, and adding a vertical component. Load when building or reviewing how a commerce agent's output reaches a frontend.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fcommerce-agents\u002Fblob\u002Fmain\u002Fplugins\u002Fcommerce-builder\u002Fskills\u002Fcommerce-ui-tools\u002FSKILL.md",[181,184,187],{"categoryNo":182,"categoryName":183,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":185,"categoryName":186,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":188,"categoryName":189,"taxonomyType":190,"taxonomyTypeDesc":191},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[193,194,195,20,196,197,198,199,107,108,200,201,202,203,204,205,206,207,33,31],"commerce ui tools","ui","Tools","roles","server","component","enrichment","server-side","tool","rendering","frontend","progressive","contract","stream","reference"]