AI Agent Hub
Back to skills
📊

Complaint Quality Review Analysis

Data Analysis Updated 2026.08.29

Paste the following prompt into your AI chat to install this skill:

Please install @engicool/complaint-quality-analysis according to https://skillhub.cn/install/skillhub.md.

About this skill

Problem

Enterprise complaint ledgers often sit across worksheets with inconsistent field names, making manual review slow and prone to missed repeat issues. This skill targets after-sales quality review, turning Excel, CSV, or pasted complaint records into structured analysis. It first creates a macro data overview, then confirms key fields such as issue level and resolution status, reducing field-mapping errors. It fits annual reviews, single-customer complaint concentration analysis, and monthly top-issue reporting, but does not handle shop-floor defects, incoming supplier materials, SPC, or cost/process analysis.

How It Works

The workflow is confirm first, compute second, generate last. The skill parses all worksheets and identifies fields, types, and row counts. It then shows preliminary insights, including date range, complaint volume, major customers and product lines, plus data-quality flags such as missing fields or invalid dates. Next, it runs category statistics, customer/product distribution, and repeated-complaint detection, marking issues when the same keyword, customer, and time window appear at least three times. It finally outputs report.html and report.md; the HTML report embeds matplotlib charts, while Markdown is easy to paste into weekly reports or review documents. The report keeps a fixed structure: period overview, category statistics and high-frequency issues, and quality conclusions with internal-control recommendations.

Use Cases

  • Turn multiple worksheets in a half-year complaint ledger into issue, customer, and repeat-issue lists.
  • Analyze a large customer's annual complaint CSV and flag issues repeated at least three times for that customer.
  • Build a monthly quality review from all complaints, showing top issues, month-over-month shifts, and a summary.
  • Confirm field meanings before a quality weekly report, then generate an HTML report with charts for documentation.

Best For

  • Quality engineers: need to turn complaint ledgers into periodic quality review reports.
  • After-sales leads: need complaint distribution and repeat-issue views by customer or product.
  • Quality data analysts: need to parse Excel/CSV fields and produce HTML/Markdown briefings.
  • Project quality owners: need neutral monthly complaint summaries for management review.