Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add BanibrataChatterjee/AwesomeSalesforceSkills --skill commerce-catalog-strategygit clone --depth 1 https://github.com/BanibrataChatterjee/AwesomeSalesforceSkillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/commerce-catalog-strategy)<a href="https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/commerce-catalog-strategy"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/commerce-catalog-strategy/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/commerce-catalog-strategy"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/commerce-catalog-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00095 | $0.03073 |
| Opus 5 | $0.00048 | $0.01537 |
| Sonnet 5 | $0.00019 | $0.00615 |
| Haiku 4.5 | $0.00010 | $0.00307 |
Grade A, and why
commerce-catalog-strategy scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commerce Catalog Strategy
This skill activates when a practitioner needs to design — not configure — a product catalog for Salesforce B2B or B2C/D2C Commerce. It covers taxonomy design, attribute planning, search index strategy, storefront navigation structure, and merchandising hierarchy. For hands-on configuration tasks (creating WebStoreCatalog records, assigning products to categories, configuring entitlement policies), use the companion skill admin/commerce-product-catalog.
Before Starting
Gather this context before working on anything in this domain:
- Store type: B2B and B2C/D2C stores use the same underlying product catalog data model but have different storefront catalog structures, search behaviors, and attribute visibility rules. Confirm which platform is in scope.
- Most common wrong assumption: Practitioners conflate the product catalog (the system-of-record for all products, not site-assigned, shared across orgs) with the storefront catalog (the navigation structure visible to buyers, one per site). These are separate objects with different design concerns.
- 50 searchable field limit: D2C and B2C stores support a maximum of 50 searchable fields per product. Exceeding this limit silently breaks the next search index rebuild. This constraint must be resolved at taxonomy design time, not after catalog migration.
- Full-token search only: Commerce search uses full-token matching. There is no prefix search or infix (substring) search. This constrains attribute naming conventions and significantly impacts how buyers can locate products by partial term.
Core Concepts
Understanding these four concepts is mandatory before making any taxonomy or attribute recommendation.
Product Catalog vs. Storefront Catalog
Salesforce Commerce uses two distinct catalog constructs that serve different purposes:
- The product catalog (
ProductCatalogobject) is the system-of-record repository for all products and their attributes. It is not assigned to a storefront. Products exist in the product catalog independent of any store. This is where taxonomy (category hierarchy), product variants, and attribute definitions live as data. - The storefront catalog is the navigation structure used by a specific B2B or B2C site. It determines which categories buyers see, in what order, and which products appear in which category pages. A store has exactly one active storefront catalog.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 197 lines · 95 tokens per session scan A 4a1be5387d22
commerce-catalog-strategy is a skill published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (3 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 95 tokens to every session and 3,073 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
commerce-catalog-strategy
Use this skill when designing a product catalog taxonomy, planning attribute strategy, or determining search and navigation structure for a B2B or B2C/D2C Commerce store. Triggers on: taxonomy design questions, attribute planning, search index strategy, category navigation structure, or merchandising hierarchy…
b2b-vs-b2c-requirements
Use this skill to determine whether a Salesforce Commerce project should use B2B Commerce (account-gated, BuyerGroup-based, contract pricing) or D2C Commerce (consumer storefront, guest checkout, individual-based). Trigger keywords: B2B vs B2C, commerce platform selection, buyer journey, account-based purchasing…
commerce-pricing-and-promotions
Configure pricebooks, tiered pricing, promotions, coupon codes, and cart discounts for B2B or D2C Commerce stores. Trigger keywords: WebStorePricebook, BuyerGroupPricebook, PriceAdjustmentSchedule, PromotionsCartCalculator, commerce coupon, cart-level discount, tiered price, Commerce promotion. NOT for Sales Cloud…
commerce-product-catalog
Use when configuring or troubleshooting the B2B/B2C Commerce product catalog — ProductCatalog, ProductCategory, ProductCategoryProduct, WebStoreCatalog, CommerceEntitlementPolicy, product attributes, and product variants. Trigger keywords: product catalog, product category, commerce catalog, entitlement policy…
commerce-checkout-configuration
Use this skill when configuring Salesforce B2B or D2C Commerce checkout: payment methods, shipping/tax integration, guest checkout, order summary setup, and CartCheckoutSession state orchestration. Trigger keywords: checkout flow, payment adapter, shipping tax integration, guest checkout, order summary…
commerce-checkout-flow-design
Use this skill when designing the checkout experience for a Salesforce B2B or D2C Commerce storefront — covering runtime model selection (LWR Managed Checkout vs Aura Flow Builder), cart and line-item requirements, payment option scoping, shipping rule definition, and guest vs. registered buyer experience design.…