manage-product-catalog

Implements product catalog CRUD with variant management, atomic inventory control, and multi-channel sync.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/vesviet/agent-skills --skill manage-product-catalog-vesviet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: manage-product-catalog
Source: https://github.com/vesviet/agent-skills/tree/main/core/skills/commerce/manage-product-catalog
Command: npx skills add https://github.com/vesviet/agent-skills --skill manage-product-catalog-vesviet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building an e-commerce catalog involves hard problems: duplicate SKUs, overselling under concurrent traffic, silently overwritten prices, and inventory leaks across marketplace channels. This Skill provides the data model, concurrency rules, and sync patterns to implement a catalog that stays consistent across storefronts and external marketplaces. ## Core Features & Use Cases - Product and Variant Modeling: Define Product and ProductVariant entities with database-enforced SKU uniqueness, versioned pricing with effective timestamps, and server-side stock computation. - Concurrency-Safe Inventory: Apply Two-Phase Atomic Inventory Holds (atomic SQL or Redis Lua with TTL), Optimistic Concurrency Control via version stamps, and channel safety buffers before publishing stock to marketplaces like Shopee, Lazada, or Amazon. - 2026 Architecture Patterns: Add semantic vector search with hybrid RRF fusion, event-sourced inventory via Kafka, knowledge graphs for recommendations, and human-review gates for AI-generated product content. - Use Case: When syncing a catalog to TikTok Shop, the Skill deducts a dynamic safety buffer (5% or minimum 3 units) before publishing quantities, preventing oversells from marketplace traffic surges. ## Quick Start Use the manage-product-catalog skill to design the product and variant data model with atomic inventory reservation for my e-commerce backend.

Frequently Asked Questions about manage-product-catalog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent overselling inventory across multiple sales channels?▼

Prevent overselling with a Two-Phase Atomic Inventory Hold using atomic conditional SQL or Redis Lua scripts with TTL, converting holds to commits on payment success. Additionally, deduct dynamic safety buffers (5% or minimum 3 units) before publishing stock to external marketplaces.

How should product variants and SKUs be modeled in a database?▼

Model a Product entity with shared fields (name, description, images, category) and a ProductVariant entity holding SKU, price, weight, stock, and attribute options like size and color. Enforce SKU uniqueness with a database constraint, never only at the application layer.

Should inventory be tracked per product or per variant?▼

Track quantity_on_hand per variant, never per product, since each sellable unit has its own stock. Expose is_in_stock as a computed server-side property (quantity_on_hand minus reserved_quantity) rather than raw counts.

Can AI-generated product descriptions be published automatically?▼

No, AI-generated product content requires a mandatory human-review gate before its status is set to published. Track generated_by, reviewed_by, generated_at, and generation_model, and treat unreviewed AI output as drafts.

Why does my marketplace sync create duplicate products on re-run?▼

Duplicates occur when the sync lacks idempotent upserts keyed by SKU. Implement upsert-by-SKU logic so re-running a sync from a POS, ERP, or supplier feed updates existing records instead of inserting new ones, and log created, updated, and failed counts per run.