[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718ECZVF8TFQM4CVAT5HGQG":3,"skill-same:01M718ECZVF8TFQM4CVAT5HGQG":65},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":47,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M718ECZVF8TFQM4CVAT5HGQG","search-discovery",null,"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).","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\u002Fshopping-agent\u002Fskills\u002Fsearch-discovery\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"search","search discovery","discovery","constraints","learn","when","empty","choice","purchase","pick","request","for","customer","view","gift","first","research","back","2026-11-10 10:12:30",false,"---\nname: search-discovery\ndescription: 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).\n---\n\n# Search and discovery\n\nBelow, \"item\" means whatever this catalog sells: a product, a stay, a plan, or a seat.\n\nTurn the need the customer described into a few options and a recommendation, in as few turns as the request allows.\n\n## Read the request and phrase the search\n\n- Take the budget, the recipient, dates, sizes, intended use, and dealbreakers out of the message and apply them; let the results show that you did instead of reading them back.\n- Search by default; a budget, a size, or a recipient you were not given narrows the shortlist and is asked about beside the results. Ask first only when the search cannot be run without the missing fact (a stay with no dates), and then ask that one question, with the likely answers as chips.\n- Apply what the profile you were given already holds (household, saved limits, what they own) without asking about it again.\n- Word the query in the catalog's vocabulary and leave the customer's phrasing behind.\n- Run one search per distinct thing the request names, all in the same round. Put a constraint the customer stated in a filter; put a guess about what they might also want in the query wording.\n\n## Shortlist and recommendation\n\n- Show three to six options in `present_products` with the one you recommend first. Each pick's `reason` is one clause naming the customer's own constraint it meets. When the options differ in a way that matters, name that trade-off in the text.\n- When the customer has narrowed to two to four finalists, use `present_comparison` on the dimensions they raised instead of another row of cards.\n- Answer a question the results do not cover with `get_product_details`, or with `web_search` where one is registered; when neither settles it, say it is unknown.\n- Before saying that several options fit under a figure, add up their prices. When the sum is over, give the sum, and offer no chip for a bundle the sum rules out.\n- Show an item the store cannot supply right now as unavailable, and introduce whatever you offer in its place as a stand-in.\n- Keep the text before the component to one to three sentences of guidance.\n\n## When the item is for someone else\n\n- Take the recipient's age, interests, and the budget from the request, the profile you were given, or a recall result about this recipient; a fact saved about a different person does not transfer. When none of the three says who the recipient is, ask the one question, or show a varied set and say their tastes are unknown.\n- Where a spread helps, include one dependable pick, one meant to delight, and one that costs less.\n- Surface the practicalities the attributes carry (sizing, batteries, noise, the age marking) where they matter for this recipient. Read an age marking against the recipient's age: leave a mismatched item off, or show it with the mismatch stated.\n","# Search and discovery\n\nBelow, \"item\" means whatever this catalog sells: a product, a stay, a plan, or a seat.\n\nTurn the need the customer described into a few options and a recommendation, in as few turns as the request allows.\n\n## Read the request and phrase the search\n\n- Take the budget, the recipient, dates, sizes, intended use, and dealbreakers out of the message and apply them; let the results show that you did instead of reading them back.\n- Search by default; a budget, a size, or a recipient you were not given narrows the shortlist and is asked about beside the results. Ask first only when the search cannot be run without the missing fact (a stay with no dates), and then ask that one question, with the likely answers as chips.\n- Apply what the profile you were given already holds (household, saved limits, what they own) without asking about it again.\n- Word the query in the catalog's vocabulary and leave the customer's phrasing behind.\n- Run one search per distinct thing the request names, all in the same round. Put a constraint the customer stated in a filter; put a guess about what they might also want in the query wording.\n\n## Shortlist and recommendation\n\n- Show three to six options in `present_products` with the one you recommend first. Each pick's `reason` is one clause naming the customer's own constraint it meets. When the options differ in a way that matters, name that trade-off in the text.\n- When the customer has narrowed to two to four finalists, use `present_comparison` on the dimensions they raised instead of another row of cards.\n- Answer a question the results do not cover with `get_product_details`, or with `web_search` where one is registered; when neither settles it, say it is unknown.\n- Before saying that several options fit under a figure, add up their prices. When the sum is over, give the sum, and offer no chip for a bundle the sum rules out.\n- Show an item the store cannot supply right now as unavailable, and introduce whatever you offer in its place as a stand-in.\n- Keep the text before the component to one to three sentences of guidance.\n\n## When the item is for someone else\n\n- Take the recipient's age, interests, and the budget from the request, the profile you were given, or a recall result about this recipient; a fact saved about a different person does not transfer. When none of the three says who the recipient is, ask the one question, or show a varied set and say their tastes are unknown.\n- Where a spread helps, include one dependable pick, one meant to delight, and one that costs less.\n- Surface the practicalities the attributes carry (sizing, batteries, noise, the age marking) where they matter for this recipient. Read an age marking against the recipient's age: leave a mismatched item off, or show it with the mismatch stated.\n",{"name":5,"description":7},"main","fd4d59224ab96b43c6dc6888207c67b3bd5a24cf","shopping-agent\u002Fskills\u002Fsearch-discovery",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":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add anthropics\u002Fcommerce-agents --skill search-discovery",{"tool":57,"command":58},"bunx","bunx skills add anthropics\u002Fcommerce-agents --skill search-discovery",{"tool":60,"command":61},"pnpm","pnpm dlx skills add anthropics\u002Fcommerce-agents --skill search-discovery","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fcommerce-agents\u002Fblob\u002Fmain\u002Fshopping-agent\u002Fskills\u002Fsearch-discovery\u002FSKILL.md",true,[],[66,90,111,135,153,188],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":77,"publishedAt":37},"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",[72],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[35,78,27,79,80,81,31,82,30,83,84,19,85,86,24,87,88,89],"purchase research","work","goals","planning","how","event","choose","space","how to","ask","teaching","it",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":37},"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",[],[97,80,81,98,99,100,101,102,103,104,31,105,106,83,29,107,108,24,109,110],"planning goals","SET","with","as","structure","plan","changes","later","project","goal","single","only","you","trip",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":37},"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",[],[118,119,120,121,122,123,124,125,126,127,28,24,128,87,129,130,131,132,133,134],"memory","memory personalization","personalization","bare","remember","recurring","answer","session","correct","short","keep","apply","file","store","forget","say","change",{"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":37},"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",[],[31,142,131,30,143,144,145,146,147,27,148,149,150,89,151,152],"customer care","help","booking","questions","about","delivery","status","new","terms","refunds","returns",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":170,"publishedAt":37},"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",[159,162,165],{"categoryNo":160,"categoryName":161,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":163,"categoryName":164,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":166,"categoryName":167,"taxonomyType":168,"taxonomyTypeDesc":169},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[171,172,173,174,175,176,177,178,82,83,179,180,181,182,183,184,185,186,187,24],"commerce ui tools","ui","Tools","commerce","roles","server","component","enrichment","server-side","tool","rendering","frontend","progressive","contract","stream","reference","load",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":194,"publishedAt":37},"01M718DYMDGKG57WYYVCT8V31R","commerce-trust-safety","The rules the reference agents enforce in code for third-party content, writes, grounding, identity, and memory, each with its module, plus two adversarial-eval rules. Load when handling untrusted tool results, guarding a write tool, or scoping what an agent remembers.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fcommerce-agents\u002Fblob\u002Fmain\u002Fplugins\u002Fcommerce-builder\u002Fskills\u002Fcommerce-trust-safety\u002FSKILL.md",[],[195,196,174,197,118,30,198,180,199,200,187,201,24,202,203,99,204,205,206,207],"trust","commerce trust safety","Safety","enforce","eval","module","Rules","code","grounding","adversarial","results","write","party"]