store-order-query

What This Skill Does

The store-order-query skill acts as a robust analytical interface between your MySQL database and OpenClaw. It is designed to bridge the gap between raw transaction data and actionable business insights. By connecting directly to your database, the skill executes structured queries against your 'Order' and 'OrderItems' tables. It handles the complete lifecycle of data processing: from checking your configuration, fetching specific date-ranged records, analyzing order metrics, payment methods, and product performance, to finally rendering a comprehensive Markdown summary for the user. It effectively turns your technical database layer into a conversational business intelligence dashboard.

Installation

To integrate this skill, navigate to your OpenClaw workspace root and execute the following command in your terminal: clawhub install openclaw/skills/skills/bondli/store-order-query

Ensure you have run pnpm install in the root directory to set up all necessary dependencies. Upon first run, the skill will check for a configuration file located at ~/openclaw-skill-data/store-order-query/config.json. If it is missing, follow the interactive prompts to input your MySQL credentials (host, port, database name, user, and password). Once configured, the skill will automatically handle data extraction and report generation.

Use Cases

• Daily Business Monitoring: Keep track of current sales performance by querying 'today' to view incoming order volumes and revenue.
• Sales Analysis: Perform deep dives into order history to identify best-selling products based on SKU and quantity metrics.
• Financial Auditing: Quickly filter order statuses and payment methods to reconcile transaction records.
• Trend Reporting: Utilize the time-range parameters to compare sales performance across the last 7 or 30 days, helping you spot growth trends.

Example Prompts

• "给我看下今天的店铺经营情况，订单量怎么样？"
• "查询一下最近30天的订单支付方式分布情况。"
• "分析一下昨天卖得最好的商品有哪些？"

Tips & Limitations

• Data Security: Since the configuration file stores sensitive credentials, ensure the file permissions on config.json are restricted (e.g., chmod 600) and never commit this file to any public version control system.
• Permissions: Verify that the database user provided in the config has at least SELECT permissions on both the Order and OrderItems tables.
• Data Mapping: If your database schema differs from the provided documentation, you must update the field mappings in the config.json file to match your specific table column names.
• Performance: Very large date ranges may lead to high query latency. If querying data over several years, consider applying database indexing on the createdAt column to optimize search speeds.