AaronShine-X/ecommerce-inventory-ops-assistant

Xiaohongshu

Xiaohongshu is the master entry point for Xiaohongshu e-commerce inventory, production, and cost table workflows. Tencent Docs workbook, sheet names, and sheet IDs must be read from private local configuration and should not be written in the public skill file.

Core Rules

• Always use live Tencent Docs data for inventory, production, receipt, shipment, return-to-inventory, and cost-table writes.
• Use memory and prior chat only for boundaries, mappings, or warnings; do not reuse old figures without live verification.
• Preview before writing any Tencent Docs table. Write only after the user clearly approves.
• Exception: when the user sends an image and the accompanying text says 修正数量 / 修正一下数量 / 修正做货数量, treat it as explicit approval to correct existing production quantities. Follow references/production-table.md correction workflow directly: parse the image, let text corrections override OCR, re-read target rows and date columns, write only existing 做货数量 detail cells, then read back details, G, and the summary row.
• After writing, re-read target cells/ranges and report exact cells plus readback values.
• Never overwrite summary/formula rows.
• In the configured production/receipt sheet, the unreceived-quantity column is formula-owned and read-only. Preserve existing formulas; never set, clear, overwrite, or manually fill it. If formulas look wrong or do not update, report it and ask before any repair.
• If a value, row, mapping, quantity, or target category is unclear, mark 需确认.
• Preserve the latest user correction over older notes.
• For 做货建议/配码, distinguish verified demand from user hypotheses and explicit cutting instructions; use references/production-advice.md to combine demand, current stock, timely in-transit, and cutting constraints. Do not turn a hypothetical ratio into a confirmed sales pattern.
• Do not create new cost categories or table meanings unless the user explicitly asks.
• When using Tencent Docs, prefer the tencent-docs skill/tooling. If MCP tools are not visible, use the target environment's configured Tencent Docs connector or credential store.

Reference Routing

Read only the reference file(s) needed for the current task.

Task	Read
Cost table, fabric cost, processing cost, shrinkage, accessories, miscellaneous fees, buttons, washing fee, factory shipment quantity write	references/cost-table.md
Production, receipt, fill tables, production plan, scheduling, not yet received, reverse sync inventory	references/production-table.md
Xiaohongshu orders, SKU statistics, inventory analysis, replenishment suggestions, past 7 days consumption, inventory alerts, return rate	references/inventory-orders.md
Production suggestions, size ratio, fabric allocation per piece, integer/round to tens, size-out-of-stock replenishment	references/production-advice.md (also read inventory-orders; when checking production schedule or writing, also read production-table)
Supply to others, breakeven, return risk, contract cycle pricing, closing inventory, capital cost, order volume fluctuation, target profit	references/supply-project-profit.md
Style number mapping, handwriting/OCR error-prone points, user latest corrections, error library	references/mappings-errors.md

For mixed tasks, read all relevant references. For example, "Fill cost table based on payment image" requires cost-table.md and often mappings-errors.md.

Private Tencent Docs Config

Public repositories should keep only config/tencent-docs.example.json.

For a real deployment, read private Tencent Docs routing from config/tencent-docs.local.json in the installed skill directory, or from the target environment's private configuration. Do not commit the local config.

Expected roles:

Config key	Meaning
workbook	Tencent Docs workbook metadata
sheets.inventory	Inventory sheet
sheets.production_receipt	Default production/receipt sheet
sheets.legacy_production	Optional legacy production sheet
sheets.cost	Cost table

If private config is missing, ask the user to configure the workbook and sheet IDs before reading or writing Tencent Docs.

Default Output Style

• Use concise tables for SKU, style, quantity, cost, and write previews.
• Separate confirmed facts from 需确认 items.
• State totals and reconciliation differences clearly.
• For reminders or chasing messages, provide a short WeChat version and a structured Feishu version when requested.

Required Cost-Table Preview Shape

When writing extracted costs to the cost table, preview at least:

Style / Item	Store attribution	Fill location	Item row	Proposed amount

Also mention target file, target sheet, target date column, current target-cell values, and source-total reconciliation.

Required Write Completion Report

After a write, report:

• Target file and sheet.
• Exact cells written.
• Values read back from Tencent Docs.
• Summary/formula rows checked.
• Any unresolved 需确认 items.

Cross-skill routing

• Jushuitan exception-order handling, review submission, and supplier-amount monitoring belong to the separate jushuitan-order-monitor skill; do not execute them inside this Xiaohongshu workflow.