Vertical Retail
Retail & e-commerce domain knowledge for SMB storefront products (storefront, inventory, pricing, cart-recovery). Codifies the vocabulary (SKU vs variant, reorder point, COGS/margin, ATS, AOV), the non-obvious rules (Shopify owns the storefront — don't fight it head-on; the wedge is multichannel inventory + reorder and cart recovery), the must-model entities (Product→Variants matrix, channel-aware InventoryLevel, ReorderRule, PricingRule, AbandonedCart), and what a naive build gets wrong (no variant model, single-channel inventory, reorder without lead-time/safety-stock). Applied by architect/
Install
npx skills add jeremybrasher/grokbot-skills --skill vertical-retailgit clone --depth 1 https://github.com/jeremybrasher/grokbot-skills.git /tmp/grokbot-skills
mkdir -p ~/.claude/skills
cp -r /tmp/grokbot-skills/collections/great-cto/skills/vertical-retail ~/.claude/skills/vertical-retailPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Retail & e-commerce — spec it like someone who's run a store The SMB retail buyer already pays Shopify ($39–399/mo + 2.9%), BigCommerce, Wix, Ecwid, or WooCommerce. They are not naive — so the spec can't be either. A storefront that "has products and a cart" is table stakes; the value is in the parts those platforms do badly. Read this before writing the catalog/inventory/pricing/cart sections of any retail ARCH or PLAN doc. ## 1. Domain vocabulary (use these exact words) - **SKU vs variant** — a **variant** is one buyable configuration (Red / Large); its **SKU** is the unique code that variant ships and is counted under. A "product" is the parent; you stock, price, and sell *variants*, not products. - **Multichannel / omnichannel** — selling across several channels (own storefront, Amazon, eBay, in-store POS, Instagram). *Omnichannel* additionally means one inventory pool behind all of them. Channel-awareness is the whole game for SMB inventory. - **Reorder point** — stock level that triggers a purchase order = (avg daily demand × **lead time** in days) + **safety stock**. **Lead time** = supplier days from order to receipt. **Safety stock** = buffer for demand/lead-time variance. Reordering without all three is wrong. - **COGS** (cost of goods sold) and **margin** = (price − COGS) / price. **Landed cost** = unit cost + freight + duties + handling; margin must use landed cost, not invoice cost.
Details
- Skill name
vertical-retail- Repository
- jeremybrasher/grokbot-skills
- Path
collections/great-cto/skills/vertical-retail/SKILL.md- Repo updated
- 15 September 2026
FAQ
What does the Vertical Retail skill do?
Retail & e-commerce domain knowledge for SMB storefront products (storefront, inventory, pricing, cart-recovery). Codifies the vocabulary (SKU vs variant, reorder point, COGS/margin, ATS, AOV), the non-obvious rules (Shopify owns the storefront — don't fight it head-on; the wedge is multichannel inventory + reorder and cart recovery), the must-model entities (Product→Variants matrix, channel-aware InventoryLevel, ReorderRule, PricingRule, AbandonedCart), and what a naive build gets wrong (no variant model, single-channel inventory, reorder without lead-time/safety-stock). Applied by architect/
How do I install the Vertical Retail skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add jeremybrasher/grokbot-skills --skill vertical-retail. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Vertical Retail popular?
It lives in jeremybrasher/grokbot-skills, which has 38 GitHub stars and 11 forks.
Related skills
Anti Patterns
38jeremybrasher/grokbot-skills
Catalogue of known SDLC anti-patterns that great_cto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
Anydesign
38jeremybrasher/grokbot-skills
Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes. Use this skill whenever the user wants to understand, document, replicate, or audit the design of something visual: a screenshot, a URL, a Figma link, a Pinterest reference, a mockup, a competitor's site, a component, a dashboard, a landing page. Also when they ask 'extract the design system from X', 'document the style of Y', 'analyze this visually', 'convert this image into tokens', 'help me replicate this design', 'what palette does t
Archetype Review Base
38jeremybrasher/grokbot-skills
Shared review framework that every domain reviewer (pci, oracle, gov, edtech, healthcare, mlops, etc.) MUST follow. Defines the output artifact (TM-{slug}.md), mandatory sections, severity scale, verdict format, the workflow scaffold (when-invoked, Step-0 read-inputs, HANDOFF), and the "domain heuristic vs generic check" boundary. Eliminates duplication across the ~30 reviewer prompts.
Abm Strategy
39lionelsimai/claude-skills-collection
Design account-based marketing strategies with targeting. TRIGGERS - Use when user needs help with abm-strategy related tasks.
Vertical Real Estate
38jeremybrasher/grokbot-skills
Residential-proptech domain knowledge so architect / pm aren't naive when speccing real-estate products (listings, lead-crm, transaction-coordination, property-mgmt). Codifies MLS/IDX reality, listing status lifecycle + syndication canonical-source, long-cycle lead nurture, transaction-coordination as the high-pain wedge, and the must-model entities. Applied during spec authoring so the architecture reflects how real estate actually works — not a generic CRUD assumption.
Actuarial Analysis
39lionelsimai/claude-skills-collection
Guide actuarial analysis for insurance pricing. TRIGGERS - Use when user needs help with actuarial-analysis related tasks.
Browse the most popular Claude skills, all marketing, sales & business skills, or write your own with the skills generator.