Sample Input
Among 8 fictional reviews, 1 is an exact duplicate and 1 is a default positive comment; of the remaining 6 valid reviews, 5 contain issues: 3 mention shipping delays and 2 mention packaging damage.

LEARN BY DOING
Define deduplication, tag definitions, unique counts, denominators, and priorities clearly to avoid duplicate reviews, word frequency, and a few quotes being mistaken for all customer conclusions.
The following is a fictional teaching example, not a client testimonial. Templates, full samples, and verification steps are all included in the download pack.
Among 8 fictional reviews, 1 is an exact duplicate and 1 is a default positive comment; of the remaining 6 valid reviews, 5 contain issues: 3 mention shipping delays and 2 mention packaging damage.
The denominator for valid reviews is 6, so shipping issues account for 3 ÷ 6 = 50.0%; among the 5 issue reviews, they account for 3 ÷ 5 = 60.0%. Verify fulfillment time differences first; don't present correlation as root cause.
Keep stable record keys, exclusion reasons, and near-duplicate manual confirmation path; allow one comment to have multiple tags but count a topic once per comment; report both overall share and within-issue share, and use severity and confidence to form an interpretable ranking.

LEARN BY DOING
First validate results with the sample pack, then copy the blank template to process your own anonymized data.
SCOPE
Record source, time, SKU, language, rating, and exclusion rules; first count raw, duplicate, invalid, available, and issue comments.
DEDUPE
Prefer review IDs; when no stable ID exists, form candidate groups and confirm manually; keep follow-up comments and similar text by default.
LABEL
Write inclusion, exclusion, and example sentences for each topic; allow multiple tags, but count a topic once per comment, and distinguish facts, feelings, and inferences.
DENOMINATOR
Calculate overall share using unique available comments and within-issue share using unique issue comments; retain sample and channel bias limits.
PRIORITY
Sort by share, severity, and evidence confidence; escalate safety and major quality events separately, then design low-risk verification.
LEARN BY DOING
A document-type skill is not the same as deployed software. Models, tools, and real business systems require separate configuration; static review does not guarantee absolute safety of any future version or runtime environment.
You can download this reviewed version's resource package. If it includes SKILL.md, provide it and the related documentation to your AI tool; first read and check the materials and usage boundaries, and do not run anything automatically.
You can also select the text to copy directly; read it first before executing.
FORMWEFT independently authored Chinese methods, templates, and fictional samples; Feishu original package not redistributed. Current fixed version has completed file structure, static rules, and content review, no high-risk behavior found. Real data permissions and generated results still need user review.
d62c54fcba6b4f36fd16619db228f5f47058323510592d3fe8b0b00c76dccf9fMethods can be learned on your own; when you need cross-system, cross-role continuous operation, we can build it into an enterprise workbench together.
Return to the resource library to find the next template based on your business problem.
Browse resource libraryCustomer voice analysis, product quality feedback, and business operation insights workbench
Describe your business problem
Customer voice analysis, product quality feedback, and business operation insights workbench