Don't send the full table to the model. Only send the header and a sample so it writes a cleaning and analysis script, and run the data locally.
Disclaimer: The content shown on this page is generated by an AI model and is for reference only. It does not constitute any guarantee of effectiveness. Actual output and Credits consumption are subject to "Usage Details" in the console.
qwen3.7-plus (writes the cleaning and analysis script) · a dirty order table exported from a business system (3,695 rows / 11 columns, messy dates, amounts with ¥, duplicates and blanks) · three stages: (1) send only the header + a 20-row sample to the model so it writes a ready-to-run script → (2) the script runs locally, the full data never uploads → (3) read its conclusions.
One-sentence output: The Douyin channel has a 16.15% refund rate, the only outlier among five channels; customer C2077 placed 38 orders in a single day, suspected of brushing—expand for the diagnostic numbers, the channel table, and 4 pitfalls you must double-check.
Steps: Have it write a script instead of giving it the data
Send only the header and the first 20 rows of sample data, and have qwen3.7-plus write a script that runs directly:
View measured output · analysis script stdout as-is
View measured output · analysis script stdout as-is
Notes
- Consumption: This playbook involves text generation (
qwen3.7-plus). The input is only a 20-row sample rather than the full table; when data is large, do not feed the whole table (it tends to time out). Have it write a script and run it locally for stability. - Data stays local: The model only sees the 20-row sample used to write the script. The full order table (including customer IDs and amounts) always runs on your own machine and is never uploaded.
- Double-check key numbers yourself: The script's conclusions are readable as-is, but numbers involving amount definitions or anomaly judgments should be verified against the script (the script is plain text; tweak a few lines as needed).