[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-anthropic-catalog-listings":3,"mdc-63oqkc-key":37,"related-org-anthropic-catalog-listings":229,"related-repo-anthropic-catalog-listings":417},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":12,"stars":26,"repoUrl":27,"updatedAt":28,"license":29,"forks":30,"topics":31,"repo":32,"sourceUrl":35,"mdContent":36},"catalog-listings","create and improve e-commerce listing content","Creating and improving listing content, covering titles, descriptions, attribute completeness, categorization fixes, image callouts written as text, edits written from material the operator supplies, and content-quality audits and bulk fixes across many listings. Not needed for questions about how a listing is performing.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},"anthropic","Anthropic","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fanthropic.png","anthropics",[13,17,20,23],{"name":14,"slug":15,"type":16},"Content Creation","content-creation","tag",{"name":18,"slug":19,"type":16},"Marketing","marketing",{"name":21,"slug":22,"type":16},"Content Strategy","content-strategy",{"name":24,"slug":25,"type":16},"E-commerce","e-commerce",1735,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fcommerce-agents","2026-09-04T08:00:35.843558",null,277,[],{"repoUrl":27,"stars":26,"forks":30,"topics":33,"description":34},[],"Reference blueprint for building shopping and merchant agents with Claude. Examples in retail, commerce, telecom, and entertainment included.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fcommerce-agents\u002Ftree\u002FHEAD\u002Fmerchant-agent\u002Fskills\u002Fcatalog-listings","---\nname: catalog-listings\ndescription: Creating and improving listing content, covering titles, descriptions, attribute completeness, categorization fixes, image callouts written as text, edits written from material the operator supplies, and content-quality audits and bulk fixes across many listings. Not needed for questions about how a listing is performing.\n---\n\n# Catalog and listings\n\nBelow, \"listing\" means whatever this operation sells: a product, a room type, a plan or device, or an event tier.\n\nRead the record, write the weak or missing content out in full, and stage it; the live listing changes only after the operator approves.\n\n## Where each fact comes from\n\n- Fetch the record with `get_listing` before proposing an edit. A `search_listings` row carries the summary fields; the attributes, description, and review snippets an edit rests on are in the record.\n- Write in the brand voice and naming conventions saved in memory, without asking the operator to restate them.\n- Take an attribute value from the record or from what the operator said in this conversation. A value that is merely likely for the type, or consistent with the attributes beside it, is a fabrication: leave the field blank or ask, one line per open field, and propose the rest of the fix without waiting.\n- Review snippets are evidence about the item; a line of review praise stays a review line and does not become a claim in the description.\n- Treat a spec sheet or note the operator pastes as source material for the edit they asked for: put its facts into the listing in the operator's voice, and list the fields it does not cover as open questions in the same reply.\n\n## The copy you propose\n\n- Propose the finished title or description, approvable unchanged: what the item is, who it is for, and what the record shows is notable. Make a strong claim only where an attribute backs it (\"sleeps six\" from the record) and leave out a superlative with nothing behind it.\n- Fill a missing attribute from a value that is already elsewhere in the record; a description that mentions a balcony supplies the balcony attribute.\n- Search-friendliness is which record facts the title carries: bring forward the words a buyer would type (occupancy, allowance, section, material, size) and drop filler that carries none of them.\n- Write an image callout as a description of the shot to add and what it should show; do not write the listing as though the photo exists.\n\n## Audits and categorization\n\n- Start an audit from `search_listings` with an empty query and the quality filter, then `get_listing` on the candidates. Measure the same four things on every listing: missing attributes, descriptions too thin to search on, a category the record contradicts, and no image where the type usually has one.\n- Rank findings by impact, so a busy listing with missing attributes comes before a quiet one with a clumsy title. Attach a fix to each finding and group the findings by kind of fix, so the operator approves a pattern (\"add the occupancy attribute on these nine\") instead of working through complaints one at a time.\n- Stage a categorization fix as a listing update like any other, this turn: the destination is a category a catalog read this conversation returned, or else the name the request implies, written into the note as the assumption; the preview shows the category before and after, and is where the operator corrects the name.\n\n## Bulk fixes\n\n- Show the pattern on one or two listings first and stage the rest after the operator confirms it.\n- Stage in batches within the per-change item cap and say how many batches there are. Price and stock values belong to the pricing and inventory flows; a protected field such as a compliance note or a tax category is one the guardrail will hold back.\n- A bulk change contains the edits the operator asked for; offer anything you notice on the way through as a separate proposal.\n\n## Stage and preview\n\n- Stage each edit with `stage_listing_update`; the preview carries the diff, and the staging note says why the change is right.\n",{"data":38,"body":39},{"name":4,"description":6},{"type":40,"children":41},"root",[42,51,57,62,69,116,122,145,151,183,189,207,213],{"type":43,"tag":44,"props":45,"children":47},"element","h1",{"id":46},"catalog-and-listings",[48],{"type":49,"value":50},"text","Catalog and listings",{"type":43,"tag":52,"props":53,"children":54},"p",{},[55],{"type":49,"value":56},"Below, \"listing\" means whatever this operation sells: a product, a room type, a plan or device, or an event tier.",{"type":43,"tag":52,"props":58,"children":59},{},[60],{"type":49,"value":61},"Read the record, write the weak or missing content out in full, and stage it; the live listing changes only after the operator approves.",{"type":43,"tag":63,"props":64,"children":66},"h2",{"id":65},"where-each-fact-comes-from",[67],{"type":49,"value":68},"Where each fact comes from",{"type":43,"tag":70,"props":71,"children":72},"ul",{},[73,96,101,106,111],{"type":43,"tag":74,"props":75,"children":76},"li",{},[77,79,86,88,94],{"type":49,"value":78},"Fetch the record with ",{"type":43,"tag":80,"props":81,"children":83},"code",{"className":82},[],[84],{"type":49,"value":85},"get_listing",{"type":49,"value":87}," before proposing an edit. A ",{"type":43,"tag":80,"props":89,"children":91},{"className":90},[],[92],{"type":49,"value":93},"search_listings",{"type":49,"value":95}," row carries the summary fields; the attributes, description, and review snippets an edit rests on are in the record.",{"type":43,"tag":74,"props":97,"children":98},{},[99],{"type":49,"value":100},"Write in the brand voice and naming conventions saved in memory, without asking the operator to restate them.",{"type":43,"tag":74,"props":102,"children":103},{},[104],{"type":49,"value":105},"Take an attribute value from the record or from what the operator said in this conversation. A value that is merely likely for the type, or consistent with the attributes beside it, is a fabrication: leave the field blank or ask, one line per open field, and propose the rest of the fix without waiting.",{"type":43,"tag":74,"props":107,"children":108},{},[109],{"type":49,"value":110},"Review snippets are evidence about the item; a line of review praise stays a review line and does not become a claim in the description.",{"type":43,"tag":74,"props":112,"children":113},{},[114],{"type":49,"value":115},"Treat a spec sheet or note the operator pastes as source material for the edit they asked for: put its facts into the listing in the operator's voice, and list the fields it does not cover as open questions in the same reply.",{"type":43,"tag":63,"props":117,"children":119},{"id":118},"the-copy-you-propose",[120],{"type":49,"value":121},"The copy you propose",{"type":43,"tag":70,"props":123,"children":124},{},[125,130,135,140],{"type":43,"tag":74,"props":126,"children":127},{},[128],{"type":49,"value":129},"Propose the finished title or description, approvable unchanged: what the item is, who it is for, and what the record shows is notable. Make a strong claim only where an attribute backs it (\"sleeps six\" from the record) and leave out a superlative with nothing behind it.",{"type":43,"tag":74,"props":131,"children":132},{},[133],{"type":49,"value":134},"Fill a missing attribute from a value that is already elsewhere in the record; a description that mentions a balcony supplies the balcony attribute.",{"type":43,"tag":74,"props":136,"children":137},{},[138],{"type":49,"value":139},"Search-friendliness is which record facts the title carries: bring forward the words a buyer would type (occupancy, allowance, section, material, size) and drop filler that carries none of them.",{"type":43,"tag":74,"props":141,"children":142},{},[143],{"type":49,"value":144},"Write an image callout as a description of the shot to add and what it should show; do not write the listing as though the photo exists.",{"type":43,"tag":63,"props":146,"children":148},{"id":147},"audits-and-categorization",[149],{"type":49,"value":150},"Audits and categorization",{"type":43,"tag":70,"props":152,"children":153},{},[154,173,178],{"type":43,"tag":74,"props":155,"children":156},{},[157,159,164,166,171],{"type":49,"value":158},"Start an audit from ",{"type":43,"tag":80,"props":160,"children":162},{"className":161},[],[163],{"type":49,"value":93},{"type":49,"value":165}," with an empty query and the quality filter, then ",{"type":43,"tag":80,"props":167,"children":169},{"className":168},[],[170],{"type":49,"value":85},{"type":49,"value":172}," on the candidates. Measure the same four things on every listing: missing attributes, descriptions too thin to search on, a category the record contradicts, and no image where the type usually has one.",{"type":43,"tag":74,"props":174,"children":175},{},[176],{"type":49,"value":177},"Rank findings by impact, so a busy listing with missing attributes comes before a quiet one with a clumsy title. Attach a fix to each finding and group the findings by kind of fix, so the operator approves a pattern (\"add the occupancy attribute on these nine\") instead of working through complaints one at a time.",{"type":43,"tag":74,"props":179,"children":180},{},[181],{"type":49,"value":182},"Stage a categorization fix as a listing update like any other, this turn: the destination is a category a catalog read this conversation returned, or else the name the request implies, written into the note as the assumption; the preview shows the category before and after, and is where the operator corrects the name.",{"type":43,"tag":63,"props":184,"children":186},{"id":185},"bulk-fixes",[187],{"type":49,"value":188},"Bulk fixes",{"type":43,"tag":70,"props":190,"children":191},{},[192,197,202],{"type":43,"tag":74,"props":193,"children":194},{},[195],{"type":49,"value":196},"Show the pattern on one or two listings first and stage the rest after the operator confirms it.",{"type":43,"tag":74,"props":198,"children":199},{},[200],{"type":49,"value":201},"Stage in batches within the per-change item cap and say how many batches there are. Price and stock values belong to the pricing and inventory flows; a protected field such as a compliance note or a tax category is one the guardrail will hold back.",{"type":43,"tag":74,"props":203,"children":204},{},[205],{"type":49,"value":206},"A bulk change contains the edits the operator asked for; offer anything you notice on the way through as a separate proposal.",{"type":43,"tag":63,"props":208,"children":210},{"id":209},"stage-and-preview",[211],{"type":49,"value":212},"Stage and preview",{"type":43,"tag":70,"props":214,"children":215},{},[216],{"type":43,"tag":74,"props":217,"children":218},{},[219,221,227],{"type":49,"value":220},"Stage each edit with ",{"type":43,"tag":80,"props":222,"children":224},{"className":223},[],[225],{"type":49,"value":226},"stage_listing_update",{"type":49,"value":228},"; the preview carries the diff, and the staging note says why the change is right.",{"items":230,"total":416},[231,247,266,280,292,311,327,338,359,379,393,408],{"slug":232,"name":232,"fn":233,"description":234,"org":235,"tags":236,"stars":244,"repoUrl":245,"updatedAt":246},"academy-guide","recommend Claude Academy resources","Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: \"how do I\", \"how can I\", \"getting started with\", \"what can Claude do\", \"teach me\", \"learn to use\"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[237,238,241],{"name":9,"slug":8,"type":16},{"name":239,"slug":240,"type":16},"Documentation","documentation",{"name":242,"slug":243,"type":16},"Education","education",161831,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fskills","2026-08-19T03:59:01.021254",{"slug":248,"name":248,"fn":249,"description":250,"org":251,"tags":252,"stars":244,"repoUrl":245,"updatedAt":265},"algorithmic-art","create algorithmic art with p5.js","Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[253,256,259,262],{"name":254,"slug":255,"type":16},"Creative","creative",{"name":257,"slug":258,"type":16},"Design","design",{"name":260,"slug":261,"type":16},"Generative Art","generative-art",{"name":263,"slug":264,"type":16},"JavaScript","javascript","2026-04-06T17:56:15.455818",{"slug":267,"name":267,"fn":268,"description":269,"org":270,"tags":271,"stars":244,"repoUrl":245,"updatedAt":279},"brand-guidelines","apply Anthropic brand colors and typography","Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[272,275,276],{"name":273,"slug":274,"type":16},"Branding","branding",{"name":257,"slug":258,"type":16},{"name":277,"slug":278,"type":16},"Typography","typography","2026-04-06T17:56:05.042852",{"slug":281,"name":281,"fn":282,"description":283,"org":284,"tags":285,"stars":244,"repoUrl":245,"updatedAt":291},"canvas-design","create posters and visual art as PNG or PDF","Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[286,287,288],{"name":254,"slug":255,"type":16},{"name":257,"slug":258,"type":16},{"name":289,"slug":290,"type":16},"PDF","pdf","2026-04-06T17:56:03.794732",{"slug":293,"name":293,"fn":294,"description":295,"org":296,"tags":297,"stars":244,"repoUrl":245,"updatedAt":310},"claude-api","build apps with the Claude API","Reference for the Claude API \u002F Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration.\nTRIGGER — read BEFORE opening the target file; don't skip because it \"looks like a one-liner\" — whenever: the prompt names Claude\u002FAnthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing\u002Fmodel choice\u002Flimits\u002Fcaching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent\u002FMCP\u002Ftool-definition\u002Fmulti-agent\u002FRAG\u002FLLM-judge\u002Fcomputer-use; generate\u002Fsummarize\u002Fextract\u002Fclassify\u002Frewrite\u002Fconverse over NL; debugging refusals\u002Fcutoffs\u002Fstreaming\u002Ftool-calls\u002Ftokens).\nSKIP only when another provider is being worked on (overrides all triggers): OpenAI\u002FGPT\u002FGemini\u002FLlama\u002FMistral\u002FCohere\u002FOllama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[298,301,302,305,307],{"name":299,"slug":300,"type":16},"Agents","agents",{"name":9,"slug":8,"type":16},{"name":303,"slug":304,"type":16},"Anthropic SDK","anthropic-sdk",{"name":306,"slug":293,"type":16},"Claude API",{"name":308,"slug":309,"type":16},"LLM","llm","2026-09-04T07:28:24.898544",{"slug":312,"name":312,"fn":313,"description":314,"org":315,"tags":316,"stars":244,"repoUrl":245,"updatedAt":326},"discernment-nudge","provide discernment nudges for user decisions","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[317,320,323],{"name":318,"slug":319,"type":16},"Coaching","coaching",{"name":321,"slug":322,"type":16},"Productivity","productivity",{"name":324,"slug":325,"type":16},"Strategy","strategy","2026-08-19T03:59:01.539281",{"slug":328,"name":328,"fn":329,"description":330,"org":331,"tags":332,"stars":244,"repoUrl":245,"updatedAt":337},"doc-coauthoring","co-author documentation and technical specs","Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[333,334],{"name":239,"slug":240,"type":16},{"name":335,"slug":336,"type":16},"Technical Writing","technical-writing","2026-04-06T17:56:14.18897",{"slug":339,"name":339,"fn":340,"description":341,"org":342,"tags":343,"stars":244,"repoUrl":245,"updatedAt":358},"docx","create and edit Word documents","Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[344,347,349,352,355],{"name":345,"slug":346,"type":16},"Documents","documents",{"name":348,"slug":339,"type":16},"DOCX",{"name":350,"slug":351,"type":16},"Office","office",{"name":353,"slug":354,"type":16},"Templates","templates",{"name":356,"slug":357,"type":16},"Word","word","2026-07-18T05:16:23.136271",{"slug":360,"name":360,"fn":361,"description":362,"org":363,"tags":364,"stars":244,"repoUrl":245,"updatedAt":378},"frontend-design","design production-grade frontend interfaces","Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[365,366,369,372,375],{"name":257,"slug":258,"type":16},{"name":367,"slug":368,"type":16},"Frontend","frontend",{"name":370,"slug":371,"type":16},"React","react",{"name":373,"slug":374,"type":16},"Tailwind CSS","tailwind-css",{"name":376,"slug":377,"type":16},"UI Components","ui-components","2026-09-04T07:28:23.795756",{"slug":380,"name":380,"fn":381,"description":382,"org":383,"tags":384,"stars":244,"repoUrl":245,"updatedAt":392},"internal-comms","write internal company communications","A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[385,388,389],{"name":386,"slug":387,"type":16},"Communications","communications",{"name":353,"slug":354,"type":16},{"name":390,"slug":391,"type":16},"Writing","writing","2026-04-06T17:56:20.695522",{"slug":394,"name":394,"fn":395,"description":396,"org":397,"tags":398,"stars":244,"repoUrl":245,"updatedAt":407},"mcp-builder","build MCP servers","Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node\u002FTypeScript (MCP SDK).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[399,400,403,404],{"name":299,"slug":300,"type":16},{"name":401,"slug":402,"type":16},"API Development","api-development",{"name":308,"slug":309,"type":16},{"name":405,"slug":406,"type":16},"MCP","mcp","2026-04-06T17:56:10.357665",{"slug":290,"name":290,"fn":409,"description":410,"org":411,"tags":412,"stars":244,"repoUrl":245,"updatedAt":415},"read edit and manipulate PDF files","Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text\u002Ftables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting\u002Fdecrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[413,414],{"name":345,"slug":346,"type":16},{"name":289,"slug":290,"type":16},"2026-04-06T17:56:02.483316",521,{"items":418,"total":514},[419,426,441,456,471,486,503],{"slug":4,"name":4,"fn":5,"description":6,"org":420,"tags":421,"stars":26,"repoUrl":27,"updatedAt":28},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[422,423,424,425],{"name":14,"slug":15,"type":16},{"name":21,"slug":22,"type":16},{"name":24,"slug":25,"type":16},{"name":18,"slug":19,"type":16},{"slug":427,"name":427,"fn":428,"description":429,"org":430,"tags":431,"stars":26,"repoUrl":27,"updatedAt":440},"commerce-architecture","design and review commerce agent architecture","How the reference commerce agents of either role are structured, covering the loop, where each rule lives, skills, the backend interface, delegates, and model fields. Load when designing or reviewing the structure of a shopping or merchant agent.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[432,433,436,437],{"name":299,"slug":300,"type":16},{"name":434,"slug":435,"type":16},"Architecture","architecture",{"name":24,"slug":25,"type":16},{"name":438,"slug":439,"type":16},"Engineering","engineering","2026-09-04T08:00:39.152322",{"slug":442,"name":442,"fn":443,"description":444,"org":445,"tags":446,"stars":26,"repoUrl":27,"updatedAt":455},"commerce-evals","run behavioral evals for commerce agents","Authoring and running behavioral evals for a shopping or merchant agent, covering the case shape, authoring rules, code graders and judges, the run pattern, and poisoned fixtures. Load when writing eval cases or rubrics or deciding how a suite runs.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[447,448,449,452],{"name":299,"slug":300,"type":16},{"name":24,"slug":25,"type":16},{"name":450,"slug":451,"type":16},"Evals","evals",{"name":453,"slug":454,"type":16},"Testing","testing","2026-09-04T08:00:36.204114",{"slug":457,"name":457,"fn":458,"description":459,"org":460,"tags":461,"stars":26,"repoUrl":27,"updatedAt":470},"commerce-merchant-operations","manage merchant operations and store rules","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.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[462,463,464,467],{"name":299,"slug":300,"type":16},{"name":24,"slug":25,"type":16},{"name":465,"slug":466,"type":16},"Management","management",{"name":468,"slug":469,"type":16},"Operations","operations","2026-09-04T08:00:35.464555",{"slug":472,"name":472,"fn":473,"description":474,"org":475,"tags":476,"stars":26,"repoUrl":27,"updatedAt":485},"commerce-prompt-caching","configure commerce agent prompt caching","The reference agents' cache-stable request assembly, covering the static system and per-request context split, the fixed tool list, the rolling conversation breakpoint, which config fields are prompt bytes, and verification. Load when writing or reviewing a commerce agent's prompt assembly, when cache reads are zero, or when a turn's latency or cost is the question.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[477,478,479,482],{"name":299,"slug":300,"type":16},{"name":24,"slug":25,"type":16},{"name":480,"slug":481,"type":16},"Performance","performance",{"name":483,"slug":484,"type":16},"Prompt Engineering","prompt-engineering","2026-09-04T08:00:39.50364",{"slug":487,"name":487,"fn":488,"description":489,"org":490,"tags":491,"stars":26,"repoUrl":27,"updatedAt":502},"commerce-trust-safety","enforce trust and safety rules","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.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[492,493,496,499],{"name":299,"slug":300,"type":16},{"name":494,"slug":495,"type":16},"Compliance","compliance",{"name":497,"slug":498,"type":16},"Memory","memory",{"name":500,"slug":501,"type":16},"Security","security","2026-09-04T08:00:42.609563",{"slug":504,"name":504,"fn":505,"description":506,"org":507,"tags":508,"stars":26,"repoUrl":27,"updatedAt":513},"commerce-ui-tools","implement commerce agent UI components","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.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[509,510,511,512],{"name":257,"slug":258,"type":16},{"name":24,"slug":25,"type":16},{"name":367,"slug":368,"type":16},{"name":376,"slug":377,"type":16},"2026-09-04T08:00:38.801247",16]